java app running as demon can't access EJB bean over RMI (under AIX)

[Dzmitry_...@epam.com]

One part of our application is java app running as demon. Second part is web app deployed under WebSphere 5.1.1.7. Demon should access EJB beans of web app through RMI port of WebSphere. But after DST start (March 11) it fails and throws exception:

2007.03.13 13:52:32 DEBUG FundsController com.serviceware.prudential.agent.impl.ControllerManager Exception
javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:localhost:2809/NameServiceServerRoot". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. Root exception is
org.omg.CORBA.TRANSIENT: java.net.BindException: The socket name is not available on this system.:host=aixhost,port=2809 vmcid: IBM minor code: E02 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:450)
at com.ibm.rmi.transport.TCPTransport.getConnection(TCPTransport.java:180)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:81)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:175)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:306)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:377)
at com.ibm.rmi.corba.ORB.objectURLToObject(ORB.java:3937)
at com.ibm.CORBA.iiop.ORB.objectURLToObject(ORB.java:3405)
at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3823)
at com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInitCtxFactory.java:1255)
at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1106)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:678)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:606)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:481)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:102)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:408)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:131)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.serviceware.prudential.delegate.ejb.EJBBaseDelegate.getEjbHome(EJBBaseDelegate.java:60)
at com.serviceware.prudential.delegate.ejb.FundServiceDelegateRemote.getEjbService(FundServiceDelegateRemote.java:180)
at com.serviceware.prudential.delegate.ejb.FundServiceDelegateRemote.validateFund(FundServiceDelegateRemote.java:151)
at com.serviceware.prudential.agent.impl.controllers.FundsController.processFund(FundsController.java:147)
at com.serviceware.prudential.agent.impl.controllers.FundsController.doImport(FundsController.java:118)
at com.serviceware.prudential.agent.impl.ControllerManager.doImport(ControllerManager.java:160)
at com.serviceware.prudential.agent.ImportAgent.doImport(ImportAgent.java:185)
at com.serviceware.prudential.agent.WatchDog.doCheck(WatchDog.java:163)
at com.serviceware.prudential.agent.WatchDog.run(WatchDog.java:132)
Caused by: java.net.BindException: The socket name is not available on this system.
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:362)
at java.net.Socket.bind(Socket.java:524)
at com.ibm.rmi.transport.TCPTransportConnection.createSocket(TCPTransportConnection.java:165)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:376)
... 26 more
com.serviceware.prudential.api.exception.ServiceException: Failed to retrieve FundServiceHome interface
at com.serviceware.prudential.delegate.ejb.FundServiceDelegateRemote.getEjbService(FundServiceDelegateRemote.java:183)
at com.serviceware.prudential.delegate.ejb.FundServiceDelegateRemote.validateFund(FundServiceDelegateRemote.java:151)
at com.serviceware.prudential.agent.impl.controllers.FundsController.processFund(FundsController.java:147)
at com.serviceware.prudential.agent.impl.controllers.FundsController.doImport(FundsController.java:118)
at com.serviceware.prudential.agent.impl.ControllerManager.doImport(ControllerManager.java:160)
at com.serviceware.prudential.agent.ImportAgent.doImport(ImportAgent.java:185)
at com.serviceware.prudential.agent.WatchDog.doCheck(WatchDog.java:163)
at com.serviceware.prudential.agent.WatchDog.run(WatchDog.java:132)
Caused by: javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:localhost:2809/NameServiceServerRoot". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.BindException: The socket name is not available on this system.:host=aixhost,port=2809 vmcid: IBM minor code: E02 completed: No]
at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:1863)
at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1130)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:678)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:606)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:481)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:102)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:408)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:131)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.serviceware.prudential.delegate.ejb.EJBBaseDelegate.getEjbHome(EJBBaseDelegate.java:60)
at com.serviceware.prudential.delegate.ejb.FundServiceDelegateRemote.getEjbService(FundServiceDelegateRemote.java:180)
... 7 more

We know that JVM was updated to SR5.

Any ideas on cause of this problem? There were no changes in environment.