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.

Similar Messages

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 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

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.
          >

Help : Cluster Fail over Test - Could not establish a connection

Hi All
          I'm trying to do Cluster fail over test with two Weblogic 8.1 sp2 instances in cluster.
          During that testing, I'm restarting the one of the instance which is handing my request, to make sure the session is replicated smoothly to the other instance,so that can continue accessing my application without any interuption. But when I restart the instance, I'm getting following exception
          Error 500--Internal Server Error
          java.rmi.ConnectException: Could not establish a connection with 8909815174098071019S:dappsn03:[8201,8201,-1,-1,8201,-1,-1,0,0]:dappsn03-04:TNL:tnl1_81dappsn03, 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: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 com.sns.pfk.ejb.PfkSessionBean_mz6mqm_EOImpl_812_WLStub.getPortalRecord(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.getInfofromSB(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doActionDisplay(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doGet(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doPost(Unknown Source)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:607)
               at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:400)
               at com.sns.ana.ui.servlet.AuthorisationBaseServlet.service(AuthorisationBaseServlet.java:109)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Buddies, anyone hit this issue before, pls show up some light to escape this hickup.
          With Regs
          -SHAN

Hi,
          Thanx for ones, spend time on reading this thread.This problem was due to some missing entries in weblogic-ejb.xml. This got fixed as we got support from BEA.
          With Regs
          -SHAN

Java.sql.SQLException: IO Error: The Network Adapter could not establish...

Hi,
I know that there are a lot of threads with this error, but I don't know how to solve my situation yet.
I'm trying to access to the database via JDBC, and the driver return the following error:
java.sql.SQLException: IO Error: The Network Adapter could not establish the connection
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:419)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
at net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133)
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.execute(OpenConnectionCommand.java:97)
at net.sourceforge.squirrel_sql.client.mainframe.action.ConnectToAliasCommand$SheetHandler.run(ConnectToAliasCommand.java:281)
- My oracle database is up and I can access to it with locally with TOAD
- I can do TELNET localhost 1521 in the server that has the DB installed
- I can do a successful ping from the client computer to the oracle server
- There aren't any firewalls between the client and the server.
- When I try to do TELNET <IP Address> 1521 from the client computer to the oracle DB Server, the connection could not be opened
- I tryed to do a TELNET to another port where I have another service, and the result has been successful. So the problem is related with the port 1521...
I don't have any knowledge about database administration, so I don't know what to do to solve this.
Can you help me please?

java.sql.SQLException: IO Error: The Network Adapter could not establish the connectionThis preposterous error message is Oracle's way of saying either 'Connection refused' or 'Connection timeout' or 'no route to host' or 'unknown host'. However because of the stupidity of making up their own message instead of giving the original exception, it is impossible to say which. The pretentious wording is also stupid: network adapters don't create connections. TCP/IP stacks do that.
As to your problem, either there is no such host, no route to the host, nothing listening at the IP:port you specified, or there is a firewall in the way. And that includes a possible Windows firewall on the server host itself.

Could Not Establish Connection to AS Java with Available Profiles

Hi All,
I am installing AS Java on SAP Netweaver 7.4 SR2.
OS: Windows Server 2008r2 and DB: MSSQLSever 2012
During the installation I got the below error on 28th Phase out of 29th.
"Deploy Java Components"
Below is the Error Log as extracted from SAPINST Log File
[ Error ] Could not establish connection to AS Java on [WIN-9OD90N7C:50204]. Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.. Check if the host and port specified are correct and AS Java is up and running.
[ LOG EXCEPTION ] :: Could not establish connection to AS Java on [WIN-9OD90N7C:50204]. Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.. Check if the host and port specified are correct and AS Java is up and running.
javax.naming.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:386)
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 com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.performOperation(DeployCommand.java:208)
at com.sap.engine.services.dc.api.cmd.deploy.DeployCommand.executeCommand(DeployCommand.java:540)
at com.sap.engine.services.dc.api.cmd.AbstractCommand.execute(AbstractCommand.java:197)
at com.sap.engine.services.dc.api.cmd.Runner.execute(Runner.java:37)
at com.sap.engine.services.dc.api.cmd.Runner.main(Runner.java:61)
Caused by: com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available profiles:
url=WIN-9OD90N7C:50204 protocol=p4 (None); Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 192.168.245.130 and port: 50204
Check if server is started, access point for the protocol is available, and IP/Host name is accessible on network.
at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:64)
at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:39)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:298)
... 14 more
Thanks and Regards
Anurag

Hi Anurag
Could you refer the SAP Notes for your issue
1571274 - Cannot connect to server using message server ms://
1925352 - How to check the access points (or ports) being used by a live SAP J2EE server
BR
SS

Java.sql.SQLException: Io exception: The Network Adapter could not establish the conn

Hello all!
First of all, I want to say I read all the answers to this problem that were posted in the past in this forum.
I try to connect from the intranet to an Oracle database, named bc01. The string I use is "jdbc:oracle:thin:@192.168.199.11:1521:bc01". On the 192.168.199.11 machine the listener and oracleservice services are started. The bc01 is correctly added to tnsnames.ora. If I issue a tnsping80 192.168.199.11 from the console it works. However, if I issue the same command from my workstation, it doesn't work (says No listener). So what am I missing here?
Any help is much appreciated !
Thank you very much!

Faizan,
Normally this error is reported when the database is either not available or the URL is invalid. Please check the URL whether you have a valid DB connection there.
Also I see the getConnection missing e,g.
Connection conn = ds.getConnection();
regards
Debu
I am trying to setup DataSource for my application and I am using oracle 8.1.6.3 database. I have following entry in the data-sources.xml file
<data-source
               class="oracle.jdbc.pool.OracleDataSource"
               name="jdbc/pool/OracleDS"
               location="jdbc/ConnectionDS"
               pooled-location="jdbc/pool/OracleDS"
               url="jdbc:oracle:thin:@machine:1521:development"
               username="user"
               password="password"
               min-connections="3"
               max-connections="50"
               wait-timeout="10"
               inactivity-timeout="30"
     />
In my JSP code I am doing following to access the database
ResultSet sqlResultSet = null;
PreparedStatement stm = null;
InitialContext ic = new InitialContext();
DataSource ds = (DataSource)ic.lookup("jdbc/OracleDS");
stm = conn.prepareStatement(updtUser);
I got following exception when I ran teh code
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
Thanks for help
Faizan

[java.sql.SQLException: Io exception: The Network Adapter could not establish the connection]

Hello,
I have recently installed Weblogic6.1Sp1 server with Weblogic Intergration 2.1
on solaris 7 and im getting this error when connecting to the database (oracle816.3);
I have changed Oracle drivers and tried many different configurations, with no
luck, Could someone give me some guidance or has anyone encounted this error before.
Thanks
Bobby
java.sql.SQLException: Io exception: The Network Adapter could not establish the
connection]
java.sql.SQLException: Io exception: The Network Adapter could not establish the
connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:323)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:260)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at com.bea.wlpi.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:187)
at com.bea.wlpi.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1177)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:104)
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getUser(RDBMSRealm.java:145)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:806)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:670)
at weblogic.security.acl.internal.FileRealm.getPrincipalFromAnyRealm(FileRealm.java:1008)
at weblogic.security.acl.internal.FileRealm.ensureRequiredObjectsExist(FileRealm.java:957)
at weblogic.security.acl.internal.FileRealm.loadMembers(FileRealm.java:1202)
at weblogic.security.SecurityService.initializeRealm(SecurityService.java:274)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)

Hi. This is definitely an oracle-only problem, so you should simplify the problem
down to a small standalone program using the oracle thin driver to make a connection.
Once you get this to work, weblogic will also be able to do it. Make sure that
when you try to have weblogic succeed after you can do it with oracle code only,
that the driver you used to succeed with, is ahead of any weblogic jars in
the server classpath. Note that we ship a classes12.zip in our packaging, but
Oracle has since released a newer one (with the same name!) that has some bugs
fixed. Make sure the later one is the one the JVM will pick up.
Joe
Bobby wrote:
>
Hello,
I have recently installed Weblogic6.1Sp1 server with Weblogic Intergration 2.1
on solaris 7 and im getting this error when connecting to the database (oracle816.3);
I have changed Oracle drivers and tried many different configurations, with no
luck, Could someone give me some guidance or has anyone encounted this error before.
Thanks
Bobby
java.sql.SQLException: Io exception: The Network Adapter could not establish the
connection]
java.sql.SQLException: Io exception: The Network Adapter could not establish the
connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:323)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:260)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at com.bea.wlpi.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:187)
at com.bea.wlpi.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1177)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:104)
at com.bea.wlpi.rdbmsrealm.RDBMSRealm.getUser(RDBMSRealm.java:145)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:806)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:670)
at weblogic.security.acl.internal.FileRealm.getPrincipalFromAnyRealm(FileRealm.java:1008)
at weblogic.security.acl.internal.FileRealm.ensureRequiredObjectsExist(FileRealm.java:957)
at weblogic.security.acl.internal.FileRealm.loadMembers(FileRealm.java:1202)
at weblogic.security.SecurityService.initializeRealm(SecurityService.java:274)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)

Java.sql.SQLException: Io exception: The Network Adapter could not establish the

Dear all,
I have been trying to connect to Oracle 8 from Java but without success.
I am using the following driver: oracle.jdbc.driver.OracleDriver
and the thin protocol as follows:
jdbc:oracle:thin:userid/password@databasename:1512:sid
I am getting the error message:
java.sql.SQLException: Io exception: The Network Adapter could not establish th
connection
I am using jdk1.3 with classes12.zip added to the classpath settings.
Can anybody help please.
Regards,
[email protected] or [email protected]
null

Dear colleague,
I am using a stand alone database running on my windows 98 laptop.
I connect successfully via sql plus using the user id: scott and password tiger.
Below is the entry of my tnsname.ora:
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
I am finding difficult to specify a host, but I have tried the following combinations:
DriverManager.getConnection ("jdbc:oracle:thin:@koudry:1521:PLSExtProc","scott", "tiger");
where the machine name is koudry and PLSExtProc the sid.
DriverManager.getConnection ("jdbc:oracle:thin:@localhost:1521:PLSExtProc","scott", "tiger");
and also 127.0.0.1 which is the ip address of the localhost. All these give me the following error:
Exception in thread "main" java.sql.SQLException: Io exception: The Network Adap
ter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:323)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:263)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
va:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at web.main(web.java:10)
When I use the oci protocol like:
DriverManager.getConnection ("jdbc:oracle:oci8:@127.0.0.1:1521:PLSExtProc","scott", "tiger");
I get the following error:
Exception in thread "main" java.lang.UnsatisfiedLinkError: make_c_state
at oracle.jdbc.oci8.OCIDBAccess.make_c_state(Native Method)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:233)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:249)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
va:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at web.main(web.java:10)
Below is the entry for autoexec.bat:
set classpath=.;c:\oracle\ora81\jdbc\lib\classes12.zip;
mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys
SET Path=c:\Oracle\Ora81\lib;c:\Oracle\Ora81\bin;"C:\PROGRAM FILES\ORACLE\JRE\1.1.7\BIN";C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\JDK1.3\BIN;C:\MSSQL7\BINN;C:\JDK1.3\SRC;
Can anyone see what I am doing wrong.
Thanks,
Richard Koudry
null

Java.sql.SQLException: Io exception: The Network Adapter could not establish the co

I am using Oracle 9i Server just the
Weblogic 5.1 and also using Oracle 8.1.6 client for weblogic. When I start the weblogic application I am getting the following error message
"java.sql.SQLException: Io exception: The Network Adapter could not establish the co
nnection

On 10 Feb 2003 09:51:52 -0800, Shankar Viswanathan
<[email protected]> wrote:
I am using Oracle 9i Server just the
Weblogic 5.1 and also using Oracle 8.1.6 client for weblogic. When I start the weblogic application I am getting the following error message
"java.sql.SQLException: Io exception: The Network Adapter could not establish the co
nnection
"You're not providing a lot of information here, but I'll assume a few
things and say...
Ensure the URL param is set properly in the pool def. Check hostname,
port and database/TNS entry. Also, try dbpinging the database with the
following:
java utils.dbping ORACLE <user> <password> <dbname>
substitute the appropriate values where necessary. For example, I have
a TNS def called 'jforum.world' for a particular oracle instance. User
is 'auser' and the password is 'apass'. The following command will
test the connection:
java utils.dbping ORACLE auser apass jforum.world
Alternatively, you can try tnsping, an oracle util, to test the
connectability.
If either of these utils work, then it's probably a typo somewhere in
the pool properties.
Bon

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

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 :)

Connection Pooling : Network Adapter could not establish the connection

Hi,
We have a client-server application wherein the server has a pooled connection to an Oracle 10i database. The application is developed in Java and we are using Oracle OracleConnectionCacheImpl API to manage the connection pooling( DYNAMIC pooling with a pool size of 5 and we are using ojdbc14.jar)
On certain occasions when activity is extremely high, the server attemtps to retrieve around 2 million datasets/records. The connection pool runs out of connections and we get the following error :
com.indigo.utils.DBEngineException: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at com.indigo.zclasses.DBTradingSource.getConnection(DBTradingSource.java:136)
at com.indigo.zclasses.DBTradingSource.getTicketMessages(DBTradingSource.java:8033)
at sun.reflect.GeneratedMethodAccessor749.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.indigo.basketserver.ServerSideUtil.ConfigUtil(ServerSideUtil.java:88)
at com.indigo.basketserver.RemoteServerImpl.ConfigUtil(RemoteServerImpl.java:543)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:418)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:521)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:325)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:171)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:149)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:95)
at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:63)
at oracle.jdbc.pool.OracleConnectionCacheImpl.getNewPoolOrXAConnection(OracleConnectionCacheImpl.java:547)
at oracle.jdbc.pool.OracleConnectionCacheImpl.getPooledConnection(OracleConnectionCacheImpl.java:404)
at oracle.jdbc.pool.OracleConnectionCacheImpl.getConnection(OracleConnectionCacheImpl.java:298)
at oracle.jdbc.pool.OracleConnectionCacheImpl.getConnection(OracleConnectionCacheImpl.java:268)
at com.indigo.zclasses.DBTradingSource.getConnection(DBTradingSource.java:127)
This is happens in Production and despite our exhaustive efforts,we have been unable to reproduce it in our Testing environment so far.
A large number of login attempts are seen in the Oracle login monitoring table, around 50,000 but we dont think that should be an issue. At the time, when this problem occurs, there are other processes making connection to the DB without any issues. Also, after sometime, the connection is restored and no exceptions are thrown.
Any insight into how we could simulate,resolve or monitor this issue would be greatly appreciated.
Thanks,
Zuber

Hi. This a long-known issue, and is caused by the DBMS listener's incoming
request buffer becoming overloaded by many simultaneous connection
requests. It will fail some of them. I have seen this with a simple java
program that calls Driver.connect() identically 20 times in a tight loop.
Some of the calls will fail in this way, while others will succeed. The
solution BEA's pool has, is to have a delay option to have the thread
sleep a bit (half-second to a secod or so) between successive connection
requests. After that, don't close connections until they're broken. Keep
them and re-use them.
HTH,
Joe Weinstein at BEA Systems

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

Similar Messages

Maybe you are looking for