MQSeries.net :: View topic

praveenmq

Hello All,

We run message broker V6.1.0.5 in AIX TL8 server. There is a message flow which will interact with LDAP DB to fetch records.
When the message flow is idle for sometimes the result is not as expected and we receive the below error in the stderr file of the EG.

javax.naming.ServiceUnavailableException: 10.1.109.105:389; socket closed; remaining name 'ou=users,o=egov'
at com.sun.jndi.ldap.Connection.readReply(Connection.java:439)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:626)
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:549)
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1959)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1821)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1746)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:383)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:353)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:336)
at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:259)
at igov.gov.qa.service.MF_PROFILEMANAGER_JavaCompute.evaluate(MF_PROFILEMANAGER_JavaCompute.java:201)
at com.ibm.broker.javacompute.MbRuntimeJavaComputeNode.evaluate(MbRuntimeJavaComputeNode.java:179)
at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1476)
at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:103)
at com.ibm.broker.IAM3.Log4jNode.evaluate(Log4jNode.java:139)
at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1476)
at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:103)
at com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:178)
at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1476)

After few successive calls the message flow becomes active and the connection is successful.

Whenever the above error is seen broker and at the same time if i do a netstat in the LDAP machine the status of the connection is shown as TIME_WAIT. After 2 to 3 attempts i can see the status as ESTABLISHED.

Is there any way can we close the sockets from Message Broker ?
Do anyone faced similiar type of problems has it been resolved in your environment. Please share if you do have any input.

Any Fine tuning can be made in broker to make the connections to LDAP server always active?
_________________
Jack