BAMAdapter Issue : java.rmi.ConnectException: Destination unreachable;

Hi,
I have installed SOA server and BAM server on same localhost but while calling BAM adapter from the BPEL process it's throwing below error.
*<Jun 24, 2011 6:56:51 PM BST> <Error> <oracle.soa.bpel.engine.ws> <BEA-000000>*
*<got FabricInvocationException java.rmi.ConnectException: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination*
Here are my JNDI configuration :: eis/bam/rmi
HostName     java.lang.String     localhost
InstanceName     java.lang.String     ADCServer1
Password     java.lang.String     *******
PortNumber     java.lang.String     9001
UserName     java.lang.String     weblogic
I have also tried with the eis/bam/soap but it is giving me
javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused
Do i need to modify any configuration file in server?
Please suggest.
Thanks,
Sagar

Similar Messages

Help !!!!! java.rmi.ConnectException

          I have realized a Cluster on WLS 6.1 sp4 but failover doesn't works fine. After
          the fail of the first node , the application goes on the secondary and works fine
          .. when the second node fails the http session goes on the third node but my
          application crash with this stack trace : <7-mar-03 19.30.03 CET> <Info> <Cluster>
          <Removing 5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,-1]:192.1
          68.12 0.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:nodo1 to the
          cluster> <7-mar-03 19.30.14 CET> <Info> <HTTP> <[WebAppServletContext(4776087,portale,/portale)]
          Localita: init> [PrimarySecondaryReplicaHandler] : weblogic.rmi.internal.LeasedRemoteRef@159
          - jvmid: '5110730417871414485S:192.168.120.35:[7009,700 9,7010,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.
          168.120.223:mydomain:nodo1', oid: '345' java.rmi.ConnectException: Could not establish
          a connection with 5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,
          -1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:n odo1,
          java.rmi.ConnectException: Destination unreachable ; nested exception is: java.net.ConnectException:
          Connection refused; No available router to destination at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:275)
          at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:408) at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
          97) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :255) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :230) at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35) at $Proxy165.getFunzioneCorrente(Unknown
          Source) at dbr.servlet.FunzioneServlet.doGetOrPost(FunzioneServlet.java:126) at
          dbr.servlet.FunzioneServlet.doPost(FunzioneServlet.java:49) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :262) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :198) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          ntext.java:2637) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          :2359) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          <7-mar-03 19.30.15 CET> <Debug> <DBR-TIM> <Could not establish a connection with
          5110730417871414485S:192.168.120.35:[7009,7009,7010 ,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.12
          0.223:mydomain:nodo1, java.rmi.ConnectException: Destina tion unreachable; nested
          exception is: java.net.ConnectException: Connection refused; No available router
          to destination>
          it looks like the secondary don't trasform himself in a primary , looking for
          ejb stub on the node died. Thanks for any help.


          Nobody has used Stateful ejb on a 3/4 node cluster?
          "Emanuele Alfieri" <[email protected]> wrote:
          >
          >I have realized a Cluster on WLS 6.1 sp4 but failover doesn't works fine.
          >After
          >the fail of the first node , the application goes on the secondary and
          >works fine
          >... when the second node fails the http session goes on the third node
          >but my
          >application crash with this stack trace : <7-mar-03 19.30.03 CET> <Info>
          ><Cluster>
          ><Removing 5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,-1]:192.1
          >68.12 0.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:nodo1
          >to the
          >cluster> <7-mar-03 19.30.14 CET> <Info> <HTTP> <[WebAppServletContext(4776087,portale,/portale)]
          >Localita: init> [PrimarySecondaryReplicaHandler] : weblogic.rmi.internal.LeasedRemoteRef@159
          >- jvmid: '5110730417871414485S:192.168.120.35:[7009,700 9,7010,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.
          >168.120.223:mydomain:nodo1', oid: '345' java.rmi.ConnectException: Could
          >not establish
          >a connection with 5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,
          >-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:n
          >odo1,
          >java.rmi.ConnectException: Destination unreachable ; nested exception
          >is: java.net.ConnectException:
          >Connection refused; No available router to destination at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:275)
          >at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:408) at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
          >97) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          >:255) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          >:230) at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35) at
          >$Proxy165.getFunzioneCorrente(Unknown
          >Source) at dbr.servlet.FunzioneServlet.doGetOrPost(FunzioneServlet.java:126)
          >at
          >dbr.servlet.FunzioneServlet.doPost(FunzioneServlet.java:49) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          >at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >:262) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >:198) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          >ntext.java:2637) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          >:2359) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          >at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          ><7-mar-03 19.30.15 CET> <Debug> <DBR-TIM> <Could not establish a connection
          >with
          >5110730417871414485S:192.168.120.35:[7009,7009,7010 ,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.12
          >0.223:mydomain:nodo1, java.rmi.ConnectException: Destina tion unreachable;
          >nested
          >exception is: java.net.ConnectException: Connection refused; No available
          >router
          >to destination>
          >
          >it looks like the secondary don't trasform himself in a primary , looking
          >for
          >ejb stub on the node died. Thanks for any help.
          >

Java.rmi.ConnectException: Could not ...

          I have realized a Cluster on WLS 6.1 sp4 but failover doesn't works fine. After
          the fail of the first node , the application goes on the secondary and works fine
          .. when the second node fails the http session goes on the third node but my
          application crash with this stack trace : <7-mar-03 19.30.03 CET> <Info> <Cluster>
          <Removing 5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,-1]:192.1
          68.12 0.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:nodo1 to the
          cluster> <7-mar-03 19.30.14 CET> <Info> <HTTP> <[WebAppServletContext(4776087,portale,/portale)]
          Localita: init> [PrimarySecondaryReplicaHandler] : weblogic.rmi.internal.LeasedRemoteRef@159
          - jvmid: '5110730417871414485S:192.168.120.35:[7009,700 9,7010,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.
          168.120.223:mydomain:nodo1', oid: '345' java.rmi.ConnectException: Could not establish
          a connection with 5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,
          -1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:n odo1,
          java.rmi.ConnectException: Destination unreachable ; nested exception is: java.net.ConnectException:
          Connection refused; No available router to destination at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:275)
          at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:408) at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
          97) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :255) at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :230) at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35) at $Proxy165.getFunzioneCorrente(Unknown
          Source) at dbr.servlet.FunzioneServlet.doGetOrPost(FunzioneServlet.java:126) at
          dbr.servlet.FunzioneServlet.doPost(FunzioneServlet.java:49) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :262) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :198) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          ntext.java:2637) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          :2359) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          <7-mar-03 19.30.15 CET> <Debug> <DBR-TIM> <Could not establish a connection with
          5110730417871414485S:192.168.120.35:[7009,7009,7010 ,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.12
          0.223:mydomain:nodo1, java.rmi.ConnectException: Destina tion unreachable; nested
          exception is: java.net.ConnectException: Connection refused; No available router
          to destination>
          it looks like the secondary don't trasform himself in a primary , looking for
          ejb stub on the node died. Thanks for any help.


          For respect reason to Bea , I think it's better to send my prototipe in private
          with e-mail ...
          Support has seen it and they accord to me about the existence of this crazy behavior...
          If you want test it and suggest some solution please give me your e-mail or send
          a mail to this address [email protected] , I'll reply really shortly with the
          prototipe in attach.
          Please help me , my team is under attack for this problem.
          Bye Bye
          Emanuele
          [email protected]
          "Sree Bodapati" <[email protected]> wrote:
          >Do you have replication groups setup? If not try
          >http://e-docs.bea.com/wls/docs61/cluster/servlet.html#1011791
          >
          >Can you duplicate this problem with a simple test case? If so post it
          >here
          >and I will take a look at it.
          >
          >/
          >sree
          >
          >"Emanuele Alfieri" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> I have realized a Cluster on WLS 6.1 sp4 but failover doesn't works
          >fine.
          >After
          >> the fail of the first node , the application goes on the secondary
          >and
          >works fine
          >> .. when the second node fails the http session goes on the third node
          >but
          >my
          >> application crash with this stack trace : <7-mar-03 19.30.03 CET> <Info>
          ><Cluster>
          >> <Removing
          >5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,-1]:192.1
          >> 68.12 0.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:nodo1
          >to the
          >> cluster> <7-mar-03 19.30.14 CET> <Info> <HTTP>
          ><[WebAppServletContext(4776087,portale,/portale)]
          >> Localita: init> [PrimarySecondaryReplicaHandler] :
          >weblogic.rmi.internal.LeasedRemoteRef@159
          >> - jvmid: '5110730417871414485S:192.168.120.35:[7009,700
          >9,7010,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.
          >> 168.120.223:mydomain:nodo1', oid: '345' java.rmi.ConnectException:
          >Could
          >not establish
          >> a connection with
          >5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,
          >> -1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain
          >:n odo1,
          >> java.rmi.ConnectException: Destination unreachable ; nested exception
          >is:
          >java.net.ConnectException:
          >> Connection refused; No available router to destination at
          >weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:275)
          >> at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:408) at
          >weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
          >> 97) at
          >weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          >> :255) at
          >weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          >> :230) at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >at
          >$Proxy165.getFunzioneCorrente(Unknown
          >> Source) at
          >dbr.servlet.FunzioneServlet.doGetOrPost(FunzioneServlet.java:126) at
          >> dbr.servlet.FunzioneServlet.doPost(FunzioneServlet.java:49) at
          >javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
          >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >> :262) at
          >weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          >> :198) at
          >weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          >> ntext.java:2637) at
          >weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          >> :2359) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          >at
          >weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >> <7-mar-03 19.30.15 CET> <Debug> <DBR-TIM> <Could not establish a
          >connection with
          >> 5110730417871414485S:192.168.120.35:[7009,7009,7010
          >,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.12
          >> 0.223:mydomain:nodo1, java.rmi.ConnectException: Destina tion unreachable;
          >nested
          >> exception is: java.net.ConnectException: Connection refused; No available
          >router
          >> to destination>
          >>
          >> it looks like the secondary don't trasform himself in a primary , looking
          >for
          >> ejb stub on the node died. Thanks for any help.
          >>
          >
          >

Java.rmi.ConnectException: Could not establish...

          I have realized a Cluster on WLS 6.1 sp4 but failover doesn't works fine.
          After the fail of the first node , the application goes on the secondary and works
          fine ... when the second node fails the http session goes on the third node but
          my application crash with this stack trace : <7-mar-03 19.30.03 CET> <Info> <Cluster>
          <Removing
          5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,-1]:192.1
          68.12
          0.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:nodo1 to the
          cluster>
          <7-mar-03 19.30.14 CET> <Info> <HTTP>
          <[WebAppServletContext(4776087,portale,/portale)] Localita: init>
          [PrimarySecondaryReplicaHandler] :
          weblogic.rmi.internal.LeasedRemoteRef@159 - jvmid:
          '5110730417871414485S:192.168.120.35:[7009,700
          9,7010,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.
          168.120.223:mydomain:nodo1', oid: '345'
          java.rmi.ConnectException: Could not establish a connection with
          5110730417871414485S:192.168.120.35:[7009,7009,7010,7010,7009,7010,
          -1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.120.223:mydomain:n
          odo1, java.rmi.ConnectException: Destination unreachable
          ; nested exception is:
          java.net.ConnectException: Connection refused; No available router
          to destination
          at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:275)
          at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:408)
          at
          weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
          97)
          at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :255)
          at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
          :230)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy165.getFunzioneCorrente(Unknown Source)
          at dbr.servlet.FunzioneServlet.doGetOrPost(FunzioneServlet.java:126)
          at dbr.servlet.FunzioneServlet.doPost(FunzioneServlet.java:49)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :262)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :198)
          at
          weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          ntext.java:2637)
          at
          weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          :2359)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          <7-mar-03 19.30.15 CET> <Debug> <DBR-TIM> <Could not establish a connection
          with 5110730417871414485S:192.168.120.35:[7009,7009,7010
          ,7010,7009,7010,-1]:192.168.120.35,192.168.120.39,192.168.120.222,192.168.12
          0.223:mydomain:nodo1, java.rmi.ConnectException: Destina
          tion unreachable; nested exception is:
          java.net.ConnectException: Connection refused; No available router
          to destination>
          it looks like the secondary don't trasform himself in a primary , looking for
          ejb stub on the node died.
          Thanks for any help.


Hi, I got the solution. Now it is working. Need to set the 'Listen Address:' environment parameter of the weblogic Admin server with the IP address of the machine on which the EJBs' are deployed. The path to this parameter on the console is - 'base_domain/Environment/Servers/'. Under this select your server and under configuration tab and General sub tab.

What does java.rmi.ConnectException: Connection refused to host mean? ¶

Several users have run into a java.rmi.ConnectException message during deployment, and need some information on how to troubleshoot this. We'll be adding this to our documentation, but thought it might be useful now.
In NoSQL DB R2.0, the show plan -id <id> command displays plan status and any errors that may have occurred. If you see this exception listed in the error section, it means that the Admin service was unable to reach one of the NoSQL DB components while the system was trying to execute an administrative command.
The first step is check on the overall status of the store. One way to do that is to use the show topology command, followed by the verify command. The show topology command will display the layout of the store, while verify will check the status of each component. A component that can't be reached will display a status of UNREACHABLE.
In general, NoSQL DB attempts to make any troubleshooting information you need available through the Admin CLI, through commands like show plan, show events, show faults. A ConnectException message means that a communication channel either was not established, or failed, and in those cases, troubleshooting information may not have been conveyed to the Admin service. This is particularly true if there was a communication failure during initial deployment of a component.
The next step would be to look in the NoSQL log files for more detailed error information. Look first in the aggregated storewide log, which can be found in the node that is hosting the master admin service, under the KVROOT/<storename>/logs/<storename>*.log. You can locate the master Admin through the "verify" command. This log file contains information from all the different components in the store.
Suppose Replication Node rg1-rn3, on Storage Node sn3, is not responsive. Look through the <storename>.log for entries made by those components. Each log entry is prefixed with the name of the component that issued the log message. Sometimes the aggregated storewide log has too much information, or sometimes information from a component was not transmitted to the Admin, and therefore isn't included in the aggregated log. In that case, it can be more helpful to look at the Replication Node or Storage Node logs directly, which can be found on their host, in the <KVROOT>/<storename>/logs directory.
If the problem occurs during an initial deployment, it can be particularly helpful to review the Storage Node logs to make sure that the Storage Node Agent on that node was created correctly, and that the process came up as expected, according to the installation directions, and the Replication Node logs. Some of the common reasons why a Replication Node might not come up are that here is inadequate heap and memory on the node, or that a initial configuration parameter is misspelled or has an invalid value, or that the time skew between components is greater than NoSQL's acceptable limit.

Several users have run into a java.rmi.ConnectException message during deployment, and need some information on how to troubleshoot this. We'll be adding this to our documentation, but thought it might be useful now.
In NoSQL DB R2.0, the show plan -id <id> command displays plan status and any errors that may have occurred. If you see this exception listed in the error section, it means that the Admin service was unable to reach one of the NoSQL DB components while the system was trying to execute an administrative command.
The first step is check on the overall status of the store. One way to do that is to use the show topology command, followed by the verify command. The show topology command will display the layout of the store, while verify will check the status of each component. A component that can't be reached will display a status of UNREACHABLE.
In general, NoSQL DB attempts to make any troubleshooting information you need available through the Admin CLI, through commands like show plan, show events, show faults. A ConnectException message means that a communication channel either was not established, or failed, and in those cases, troubleshooting information may not have been conveyed to the Admin service. This is particularly true if there was a communication failure during initial deployment of a component.
The next step would be to look in the NoSQL log files for more detailed error information. Look first in the aggregated storewide log, which can be found in the node that is hosting the master admin service, under the KVROOT/<storename>/logs/<storename>*.log. You can locate the master Admin through the "verify" command. This log file contains information from all the different components in the store.
Suppose Replication Node rg1-rn3, on Storage Node sn3, is not responsive. Look through the <storename>.log for entries made by those components. Each log entry is prefixed with the name of the component that issued the log message. Sometimes the aggregated storewide log has too much information, or sometimes information from a component was not transmitted to the Admin, and therefore isn't included in the aggregated log. In that case, it can be more helpful to look at the Replication Node or Storage Node logs directly, which can be found on their host, in the <KVROOT>/<storename>/logs directory.
If the problem occurs during an initial deployment, it can be particularly helpful to review the Storage Node logs to make sure that the Storage Node Agent on that node was created correctly, and that the process came up as expected, according to the installation directions, and the Replication Node logs. Some of the common reasons why a Replication Node might not come up are that here is inadequate heap and memory on the node, or that a initial configuration parameter is misspelled or has an invalid value, or that the time skew between components is greater than NoSQL's acceptable limit.

Exception in the main client program: java.rmi.ConnectException: Connection

Hi
I have written a program in Java using RMI and it runs perfectly fine on my pc(localhost). But when I run it on the LAN in my office, the client program stucks and I get an exception
***Exception in the main client program: java.rmi.ConnectException: Connection refused to host***
***java.net.ConnectException: Connection timed out: connect***
Do we need to make some settings in the RMI server...or some firewall issue is there...By default port is 1099 as used by RMI registry server
Please help me TIA
vnx_in

Hi, i am having the same java.rmi.ConnectException, but the problem is that i can't even run it on localhost. I simply can't start my server, and i am getting a problem on Naming.rebind, however i think it could be because i am using an static ip to connect to internet in the LAN of my town. Does it matter in this case. I would be so thankful, because i am not able to solve it after many efforts.
Thanks in Advance :)

Java.rmi.ConnectException using webstart Swing client with WL 8.1 SP2 in a

Hi all,
I'm receiving the following exception when invoking a remote method on
a cached remote stub. This only happens if there are at least two
nodes running in a cluster. It happens more often the more nodes are
running.
It seems that the exception occurs if for a call to a remote method a
cached stub is used, and if that call is referred to a different node
in the cluster by the load balancer than the one that the stub
originally came from. But I'm not completely sure about that...
Client side config:
Webstart
JDK 1.4.2_05
weblogic.jar (we're experiencing other problems already discussed in
this group when using wlclient.jar)
Server side config:
Weblogic 8.1 SP2
cluster on Sun Solaris machines (two nodes, one manager)
Here is the exception stacktrace:
java.rmi.ConnectException: Could not establish a connection with
2198062098923170717S:shebea219:[7001,7001,-1,-1,7001,-1,-1,0,0]:SHEBEA219,SHEBEA334:DaGama:DaGamaNode1,
java.security.AccessControlException: access denied
(java.net.SocketPermission shebea219 resolve)
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:316)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:488)
at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:584)
at
weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:91)
at
weblogic.rmi.internal.activation.ActivatableRemoteRef.invoke(ActivatableRemoteRef.java:69)
at
de.conet.dagama.interesengine.nativesession.SBNativeSession_8da95c_EOImpl_812_WLStub.isConnected(Unknown
Source)
at
de.conet.dagama.agent.flight.nativ.FlightNativeListener.doExitNativeSession(FlightNativeListener.java:244)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
de.objektpark.framework.command.CommandInvoker.invoke(CommandInvoker.java:132)
at
de.objektpark.framework.command.CommandProcessor.doService(CommandProcessor.java:169)
at
de.objektpark.framework.command.CommandProcessor.service(CommandProcessor.java:131)
at
de.objektpark.framework.command.CommandProcessor.execute(CommandProcessor.java:71)
at
de.conet.webactiv.swing.command.GUICommandProcessor.execute(GUICommandProcessor.java:87)
at
de.conet.webactiv.swing.controller.GUICommandController.execute(GUICommandController.java:98)
at
de.conet.webactiv.swing.controller.GUICommandController.execute(GUICommandController.java:124)
at
de.conet.dagama.agent.flight.nativ.FlightFreeNativeView.this_windowClosing(FlightFreeNativeView.java:84)
at
de.conet.dagama.agent.flight.nativ.FlightFreeNativeView$1.windowClosing(FlightFreeNativeView.java:73)
at java.awt.AWTEventMulticaster.windowClosing(Unknown Source)
at java.awt.Window.processWindowEvent(Unknown Source)
at javax.swing.JFrame.processWindowEvent(Unknown Source)
at java.awt.Window.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
Has anyone ever come across the same problem and possibly found a
solution?
Any help would be greatly appreciated.
Thanks in advance
Rolf

Hi all,
I'm receiving the following exception when invoking a remote method on
a cached remote stub. This only happens if there are at least two
nodes running in a cluster. It happens more often the more nodes are
running.
It seems that the exception occurs if for a call to a remote method a
cached stub is used, and if that call is referred to a different node
in the cluster by the load balancer than the one that the stub
originally came from. But I'm not completely sure about that...
Client side config:
Webstart
JDK 1.4.2_05
weblogic.jar (we're experiencing other problems already discussed in
this group when using wlclient.jar)
Server side config:
Weblogic 8.1 SP2
cluster on Sun Solaris machines (two nodes, one manager)
Here is the exception stacktrace:
java.rmi.ConnectException: Could not establish a connection with
2198062098923170717S:shebea219:[7001,7001,-1,-1,7001,-1,-1,0,0]:SHEBEA219,SHEBEA334:DaGama:DaGamaNode1,
java.security.AccessControlException: access denied
(java.net.SocketPermission shebea219 resolve)
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:316)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:488)
at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:584)
at
weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:91)
at
weblogic.rmi.internal.activation.ActivatableRemoteRef.invoke(ActivatableRemoteRef.java:69)
at
de.conet.dagama.interesengine.nativesession.SBNativeSession_8da95c_EOImpl_812_WLStub.isConnected(Unknown
Source)
at
de.conet.dagama.agent.flight.nativ.FlightNativeListener.doExitNativeSession(FlightNativeListener.java:244)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
de.objektpark.framework.command.CommandInvoker.invoke(CommandInvoker.java:132)
at
de.objektpark.framework.command.CommandProcessor.doService(CommandProcessor.java:169)
at
de.objektpark.framework.command.CommandProcessor.service(CommandProcessor.java:131)
at
de.objektpark.framework.command.CommandProcessor.execute(CommandProcessor.java:71)
at
de.conet.webactiv.swing.command.GUICommandProcessor.execute(GUICommandProcessor.java:87)
at
de.conet.webactiv.swing.controller.GUICommandController.execute(GUICommandController.java:98)
at
de.conet.webactiv.swing.controller.GUICommandController.execute(GUICommandController.java:124)
at
de.conet.dagama.agent.flight.nativ.FlightFreeNativeView.this_windowClosing(FlightFreeNativeView.java:84)
at
de.conet.dagama.agent.flight.nativ.FlightFreeNativeView$1.windowClosing(FlightFreeNativeView.java:73)
at java.awt.AWTEventMulticaster.windowClosing(Unknown Source)
at java.awt.Window.processWindowEvent(Unknown Source)
at javax.swing.JFrame.processWindowEvent(Unknown Source)
at java.awt.Window.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown
Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
Has anyone ever come across the same problem and possibly found a
solution?
Any help would be greatly appreciated.
Thanks in advance
Rolf

Java.rmi.ConnectException on calling callback method

I have an interface exposed as a remote service with a simple method to register the callback object on wich the server calls a method to notify an event.
public void registerForNotification (ExitCodeCallback callback) throws RemoteException;
public interface ExitCodeCallback extends Remote
   * @param event
   * @throws RemoteException
public void notifyExitCode (ExitCodeEvent event) throws RemoteException;
public class ExitCodeEvent implements Serializable
   * Comment for <code>serialVersionUID</code>
private static final long serialVersionUID = -8542839971016423057L;
private Integer code;
private String sourceName;
   * @param source
   * @param exitCode
public ExitCodeEvent (String source, Integer exitCode)
    exitCode = code;
    sourceName = source;
   * @return Object
public Object asString ()
    return sourceName + " exited with code " + code;
}When the server try to call this method causes an exception to be thrown
java.rmi.ConnectException: Connection refused to host: 26.2.242.76; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
     at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:179)
     at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
     at $Proxy2.notifyExitCode(Unknown Source)
     at it.sogei.jscheduler.rmi.server.SchedulerServicesServerSide$InnerServerExitCodeCallback.notifyExitCode(SchedulerServicesServerSide.java:156)
     at it.sogei.jscheduler.rmi.server.ApplicationTask.notifyExitCode(ApplicationTask.java:129)
     at it.sogei.jscheduler.rmi.server.WaiterThread.run(WaiterThread.java:47)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:516)
     at java.net.Socket.connect(Socket.java:466)
     at java.net.Socket.<init>(Socket.java:366)
     at java.net.Socket.<init>(Socket.java:179)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
     ... 10 morebut, surprisingly, the client receives the event even if the ExitCodeEvent.asString() called on that object print the following line
null exited with code null.
I wonder how this could be happened?

- It happens every single time the callback method is invoked, I see the event been deserialized client-side with the fields initialized with null values and server-side there is the java.rmi.ConnectException.
- The client can't unexport the callback object, that's because I didn't think to do it.
this is the method where I start to notify to all the registered client the event
for (ExitCodeCallback callbackElement : callback)
        try
          callbackElement.notifyExitCode(event);
        catch (RemoteException ex)
          logger.debug("Unable to notify.", ex);
      }where
List<ExitCodeCallback> callback;and implementation of the callback interface is
public class ClientExitCodeCallback implements ExitCodeCallback
transient Logger logger = Logger.getLogger(ClientExitCodeCallback.class);
   * @see it.sogei.jscheduler.ExitCodeCallback#notifyExitCode()
public void notifyExitCode (ExitCodeEvent event) throws RemoteException
    logger.warn(event.asString());
}

Java.rmi.ConnectException

hi I am trying to connect to a remote server from my client as follows
$ java TestRcf -Djava.security.policy=policy
and my policy file is as follows....
grant {
permission java.net.SocketPermission "*:1024-65535", "connect";
I get the following error when i try to connect it...
Do i have to include anything else in the policy file or what is that i am missing?
the error is as follows......
lookup host: //10.1.129.3/RCFSearch10.1.129.3
java.rmi.ConnectException: Connection refused to host: 10.1.129.3; nested exception is:
java.net.ConnectException: Connection timed out
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at java.rmi.Naming.lookup(Naming.java:84)
at com.lt.rcf.RemoteRCF.<init>(RemoteRCF.java:48)
at com.lt.rcf.RCFMediator.init(RCFMediator.java:405)
at com.lt.rcf.RCFMediator.<init>(RCFMediator.java:60)
at com.lt.rcf.RCFClient.<init>(RCFClient.java:59)
at com.lt.rcf.RCFAppBuilder.create(RCFAppBuilder.java:50)
at TestRcf.test0(TestRcf.java:55)
at TestRcf.main(TestRcf.java:88)
Caused by: java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:178)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 12 more
com.lt.rcf.RCFException: RCF Server connection not available: Connection refused to host: 10.1.129.3; nested exception is:
java.net.ConnectException: Connection timed out

first of all, which OS are you working on? This
question might sound wierd, but I have noticed a
lotta people working on Linux boxes havecomplained
about this. There is another mail thread about it:
>
http://forum.java.sun.com/thread.jspa?threadID=570065&
tstart=0
is your client able to look up the reference tothe
server ? If so, can you print that reference andfind
out which port the remote server is listening on ?
here did u mean Naming.LookUp("rmi://10.1.129.3") in the client.thats where i get connection refused while doing naming.lookup.
Then use the netstat command to see if the serveris
indeed listenign on that port when the connectionis
refused !
netstat -anp - p | grep <port_of_server>
let me know how it goes.
when i did netstat -anp - p | grep <port_of_server> on my client this is what i get ...
Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:1099 0.0.0.0:* LISTEN
6435/rmiregistry
tcp 0 0 10.1.129.3:51983 10.1.129.3:1099 ESTABLISHED
6492/java
tcp 0 0 10.1.129.3:1099 10.1.129.3:51983 ESTABLISHED
6435/rmiregistry

Java.rmi.ConnectException: Connection refuse

Hi all,
I have built a simple RMI client server application.I can run client & server fine locally.
However if I test this appplication over the internet, I get this exception on the client:
java.rmi.ConnectException: Connection refused to host: 169.254.157.53; nested exception is:
java.net.ConnectException: Connection timed out: connectConnection refused to host:169.254.157.53
The RMI server is running on my PC and the client on a friend's remote PC.Both PCs are connected to Internet.
I don't have any firewall running on my PC (including windows XP firewall). The server RMI lookup on the client happens correctly,
the exception is raised when the client tries to call the remote method on the server.
Here is an extract of my RMI server code (it works locally):
public static void main(String[] args) throws Exception {
          try {
          // args[0] contains the database server name given as command line argument, arg[1] contains binary path that contains weather jpeg files
          CPrimaryWeatherServer test = new CPrimaryWeatherServer(args[0], args[1]);
          Naming.rebind("rmi://localhost:1099/WeatherPrimaryService", test);
          System.out.println("Serveur m�t�o principal d�marr�");
          } catch (Exception e){ System.out.println(e.getMessage());}
Here is an extract of my RMI client code (it works locally):
try{
                    rec=1;
                    leftClik=1;
                    System.out.println("Before RMI lookup");
                    IPrimaryWeatherServerService serveur =(IPrimaryWeatherServerService)Naming.lookup("rmi://"+primWS+":1099/WeatherPrimaryService");
                    System.out.println("After RMI lookup");
                    System.out.println("Before server method call");
                    z=serveur.getFullWeatherData(); --> exception is raised here
                    System.out.println("After RMI server method call");
I am directly connected to Internet using an ethernet card connected to an ADSL modem.169.254.157.53 is the automatic IP of my network card different from the IP given by my ISP. By the way, the client tries to contact me using my DNS name that resolves correctly to my ISP IP adress.
Thanks a lot for help,

because I am guessing that a local IP address is being embedded into the stub so the clien't can't find the remote server. I am guessing because you didn't provide the exception or its text. Anyway the suggestion will cause the correct public IP address/hostname to be embedded into the stub.

Exception occured: java.rmi.ConnectException:

hi
i got an exception while running rmi client jar file....
i want to invoke a method in the server..i have created two jar files one for server and another for client..
i have added the policy file also..i tried by using server and client in the same system
when i run the client jar i got an exception like given below..and i'm using netbeans 6...
Exception occured: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect
can any one help me to solve this problem?
thanx in advance...

hi thanx for the reply..
i'm using windows XP, netbeans6, jdk6, sql server2000.
when i started the rmiregistry this exception is over, but another exception comes
Exception occured: java.rmi.NotBoundException: myebillRMIImpl
my code is given below..please help me....a similar code worked properly without using netbeans..
import java.sql.*;
public interface ebillRMIInterface extends java.rmi.Remote
public void insert(String str) throws java.rmi.RemoteException;
     public ResultSet select(String str1) throws java.rmi.RemoteException;
import java.rmi.*;
import java.rmi.server.UnicastRemoteObject;
import java.sql.*;
public class ebillRMIImpl extends UnicastRemoteObject implements ebillRMIInterface
public ebillRMIImpl(String name) throws RemoteException
super();
try
Naming.rebind(name, this);
catch(Exception e)
System.out.println("Exception occurred: " + e);
                    Statement stmt=null;
                    Connection con=null;
                    ResultSet res=null;
public void insert(String str)
try
               Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
               con = DriverManager.getConnection("jdbc:odbc:rmidsn", "sa", "");
               stmt = con.createStatement();
               stmt.executeUpdate(str);
               con.close();
          catch (Exception e)
               System.out.println(e);
          public ResultSet select(String str)
               try
               Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
               con = DriverManager.getConnection("jdbc:odbc:rmidsn", "sa", "");
               stmt = con.createStatement();
               res=stmt.executeQuery(str);
               con.close();
          catch (Exception e)
               System.out.println(e);
          return res;
import java.rmi.*;
import java.rmi.registry.LocateRegistry;
import java.rmi.registry.Registry;
import java.rmi.server.UnicastRemoteObject;
public class ebillRMIServer
public static void main(String[] argv)
System.setSecurityManager(new RMISecurityManager());
try
//Registry registry =LocateRegistry.getRegistry();
ebillRMIImpl implementation = new ebillRMIImpl("myebillRMIImpl");
catch (Exception e)
System.out.println("Exception occurred: " + e);
Client function is
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
System.setSecurityManager(new RMISecurityManager());
int itemid;
String serverName ="";
serverName = "localhost";
                    ResultSet res=null;
String itid=jTextField1.getText();
itemid=Integer.parseInt(itid);
try
//bind server object to object in client//rmi://host:<port>/correlator
ebillRMIInterface ebillserver = (ebillRMIInterface) Naming.lookup("rmi://"+serverName+"/myebillRMIImpl");
//invoke method on server object
System.out.println("Date on server is " + d);*/
                              String str="select * from Stock where itemid="+itemid;
                              res=ebillserver.select(str);
while(res.next())
jTextField2.setText(res.getString(2));
Float price=res.getFloat(4);
String pr=String.valueOf(price);
jTextField3.setText(pr);
catch(Exception e)
System.out.println("Exception occured: " + e);
System.exit(0);
System.out.println("RMI connection successful");
}

Invocation time Exception (java.rmi.ConnectException: Connection refused to

Hi folks,
SERVER = LINUX
CLIENT = WINDOWS 200
JAVA VERSION : 1.4.2
Object obj = Naming.lookup("rmi://x.x.x.x:5578/MyServer");
System.out.println("Object ="+obj); // Works fine and return stub as shown in o/p
MyServer_Stub server = (MyServer_Stub)obj;
server.validate(); // throws following Connection refused exception
-----OUTPUT-----
Object =com.MyServer_Stub[RemoteStub [ref: [endpoint:[x.x.x.x:42360](remote),objID:[a981ca:10722cb9411:-8000, 0]]]]
java.rmi.ConnectException: Connection refused to host: x.x.x.x.x; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)[
     at com.MyServer_Stub.validate(Unknown Source)/b]
     at tescasees.testbyexample.rmi.MyServerChangesTestApplication.main
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:452)
     at java.net.Socket.connect(Socket.java:402)
     at java.net.Socket.<init>(Socket.java:309)
     at java.net.Socket.<init>(Socket.java:124)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
     ... 5 more
Exception in thread "main"
[b] Why does java system throws exception at invoke time not connection time at lookup time</b]
Any suggestion...
Regards,
Manoj

> Are you getting this from a lookup()? If so it means the Registry you are looking for at rmi://x.x.x.x:5578 is not present.
I am getting it at the time when I invoke the method validate on the object returned from lookup.
--Manoj

Java.rmi.ConnectException: Connection refused to host: 10.41.8.140; nested exception is:

Agile:9.2.2.1
linux-x86_64

What is the Port in which you are ruinning the RMI?
You need to mention the port.
Simply chek if you have proper connectivity to the Server and the RMI Service as the speicifed port, try the debugging commands from command prompt like:
D:>telnet <Server IP Address> <Port Number>
If this command clears the windows into a blank window as if waiting for you input then it means that you have access to the Server and the RMI service is running on the machine.
If not, it is either NOT accessible or RMI Service is not working.
Thanks and regards,
Pazhanikanthan. P

JMS Module, Foreign Server: Destination unreachable

Hi,
In our OSB setup we have 2 weblogic domains (on RHEL5), one for hosting the OSB services and one that is used solely for the purpose of JMS messsaging.
Therefore we have configured a Foreign Server in our JMS Module on the OSB Domain with following config:
* JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
* JNDI Connection URL: t3://fsb-jms1-dev:7901,fsb-jms2-dev:7901
After deploying an EJB that makes use of this module we see following error in our log files every time when starting a Managed Server:
####<Jun 8, 2011 11:36:48 AM CEST> <Warning> <EJB> <esddev148> <osbms1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <11d1def534ea1be0:-27013fcb:1306e9a12ac:-8000-0000000000000016> <13075
25808959> <BEA-010061> <The Message-Driven EJB: MessageLogWriter is unable to connect to the JMS destination: fsb.jms.MessageLoggingQueue. The Error was:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java
.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:64)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java.rmi.ConnectException: Destination unreachab
le; nested exception is:
java.io.IOException: Empty server reply; No available router to destination; nested exception is:
java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:352)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:612)
at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:563)
at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:789)
at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:341)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:194)
... 4 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.io.IOException: Empty server reply; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:402)
at weblogic.rjvm.RJVMImpl.ensureConnectionEstablished(RJVMImpl.java:306)
at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:350)
at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:613)
... 30 more
>
I've allready ensured that the managed servers of the jms cluster are reachable by issuing a connect command from WLST (although making the connection can be time consuming)
wls:/offline> connect('weblogic','******','t3://fsb-jms1-dev:7901')
Connecting to t3://fsb-jms1-dev:7901 with userid weblogic ...
Successfully connected to managed Server 'jmsms1' that belongs to domain 'jmsdevdomain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/jmsdevdomain/serverConfig> disconnect()
Disconnected from weblogic server: jmsms1
wls:/offline> connect('weblogic','******','t3://fsb-jms2-dev:7901')
Connecting to t3://fsb-jms2-dev:7901 with userid weblogic ...
Successfully connected to managed Server 'jmsms2' that belongs to domain 'jmsdevdomain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
In my search for a solution I've also read that this could be caused by a bad configured DNS server. Therefore I configured my /etc/nsswitch.conf file to contain only the property files under the parameter hosts.
Following is an extraction of my /etc/hosts file:
10.16.85.50 fsb-jms1-dev.localdomain fsb-jms1-dev
10.16.85.51 fsb-jms2-dev.localdomain fsb-jms2-dev
10.16.85.52 fsb-osb1-dev.localdomain fsb-osb1-dev
10.16.85.53 fsb-osb2-dev.localdomain fsb-osb2-dev
Does anybody have an idea how I can further debug this problem?
Kind Regards,
Davy

Maybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html

T3://127.0.0.1:7101: Destination unreachable; -- On jDeveloper 11gR1

I am new to weblogic, and have just installed Oracle Express, WLS, jDeveloper.
After running through the tutorial on 'Building a Web Application with JDeveloper 11g Using EJB, JAP, and JavaServerFaces', following all steps to the letter, I am able to make the DB connections alright, start the integrated server, but once I try running the HRFacadeBean in step 18, but it errors out.
It seems to me that the issue with recognizing the t3 protocol.
I have checked that 127.0.0.1:7101 is up and running as I get the welcome screen when I go to it and there are no errors listed on the server console screen in jDeveloper, but I get this trace in the log:
[EclipseLink/JPA Client] Adding Java options: -javaagent:C:\Oracle\Middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-0.jar
C:\Oracle\Middleware\jdk160_18\bin\javaw.exe -client -classpath C:\Oracle\Middleware\jdeveloper\myWork\.adf;C:\Oracle\Middleware\jdeveloper\myWork\EJBModel\classes;C:\Oracle\Middleware\modules\com.oracle.toplink_1.0.0.0_11-1-1-3-0.jar;C:\Oracle\Middleware\modules\org.eclipse.persistence_1.0.0.0_2-0.jar;C:\Oracle\Middleware\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.toplink_11.1.1\javax.persistence_2.0_preview.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\Oracle\Middleware\modules\javax.jsf_1.0.0.0_1-2.jar;C:\Oracle\Middleware\modules\javax.ejb_3.0.1.jar;C:\Oracle\Middleware\modules\javax.enterprise.deploy_1.2.jar;C:\Oracle\Middleware\modules\javax.interceptor_1.0.jar;C:\Oracle\Middleware\modules\javax.jms_1.1.1.jar;C:\Oracle\Middleware\modules\javax.jsp_1.1.0.0_2-1.jar;C:\Oracle\Middleware\modules\javax.jws_2.0.jar;C:\Oracle\Middleware\modules\javax.activation_1.1.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.mail_1.1.0.0_1-4-1.jar;C:\Oracle\Middleware\modules\javax.xml.soap_1.3.1.0.jar;C:\Oracle\Middleware\modules\javax.xml.rpc_1.2.1.jar;C:\Oracle\Middleware\modules\javax.xml.ws_2.1.1.jar;C:\Oracle\Middleware\modules\javax.management.j2ee_1.0.jar;C:\Oracle\Middleware\modules\javax.resource_1.5.1.jar;C:\Oracle\Middleware\modules\javax.servlet_1.0.0.0_2-5.jar;C:\Oracle\Middleware\modules\javax.transaction_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.stream_1.1.1.0.jar;C:\Oracle\Middleware\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\Oracle\Middleware\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\Oracle\Middleware\modules\javax.persistence_1.0.0.0_1-0-2.jar;C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -javaagent:C:\Oracle\Middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-0.jar -Dhttp.proxyHost=proxy.ulalaunch.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts= -Dhttps.proxyHost=proxy.ulalaunch.com -Dhttps.proxyPort=80 -Dhttps.nonProxyHosts= oracle.HRFacadeClient
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at oracle.HRFacadeClient.getInitialContext(HRFacadeClient.java:58)
     at oracle.HRFacadeClient.main(HRFacadeClient.java:13)
Caused by: java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
     ... 9 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     java.io.IOException: Empty server reply; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     ... 12 more
Process exited with exit code 0.

Hi,
I guess the problem is with below information but I do not know from where they came!? maybe in the jdeveloper you have set the proxy or maybe your localhost is not bind to 127.0.0.1 and you must use your computer name.
Dhttp.proxyHost=proxy.ulalaunch.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts= -Dhttps.proxyHost=proxy.ulalaunch.com -Dhttps.proxyPort=80 -Dhttps.nonProxyHosts= oracle.HRFacadeClient

BAMAdapter Issue : java.rmi.ConnectException: Destination unreachable;

Similar Messages

Maybe you are looking for