Destination unreachable exception ..???

Dear Sirs/Madam,
While restarting web logic managed servers in a clusters; we encountered below shown errors:
"avax.naming.CommunicationException. Root exception is java.net.ConnectException: t3://myservername.com:8100: Destination unreachable; nested exception is:
     java.net.ConnectException: Connection refused; No available router to destination"
We are running 4 managed servers in one cluster. One cluster spans 2 physical servers. Thus each box has 2 managed servers.
The cluster is running on weblogic 7.x on hpux 11i.
Please suggest what are the possible root cause of this exception and what are the mitigations ?
Thanks,
Shiv

Basically, it can't find the server.
Is the server running?
configured to listen on localhost?
try 3://127.0.0.1:7001 instead.
Check the port the server is listening on.
Pete

Similar Messages

  • Destination unreachable; nested exception

    Environment:
    JDeveloper 11.1.1.3.0
    Build JDEVADF_11.1.1.3.PS2_GENERIC_100408.2356.5660
    Oracle 12.1.1
    JDK 1.6
    I got this exception on the '23rd' step of this tutorial
    http://www.oracle.com/technology/obe/obe11jdev/ps1/ejb/ejb.html
    Thanks for your help.
    [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:\JDeveloper\mywork\HR_EJB_JPA_APP\.adf;C:\JDeveloper\mywork\HR_EJB_JPA_APP\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\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;C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\oracle\11g\ojdbc6.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-collation.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-lcsd.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-mapping.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-servlet.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-translation.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n-utility.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.nlsrtl_11.1.0\orai18n.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.odl_11.1.1\ojdl.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.dms_11.1.1\dms.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.idm_11.1.1\identitystore.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adfm.jar;C:\Oracle\Middleware\oracle_common\modules\groovy-all-1.6.3.jar;C:\Oracle\Middleware\jdeveloper\adfdt\lib\adf-dt-at-rt.jar;C:\Oracle\Middleware\jdeveloper\adfdt\lib\adf-transactions-dt.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\adfdt_common.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\db-ca.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1\jdev-cm.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.ldap_11.1.1\ojmisc.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\commons-el.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\jsp-el-api.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\oracle-el.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.security_11.1.1\adf-share-security.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.security_11.1.1\adf-controller-security.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\adf-share-support.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share.ca_11.1.1\adf-share-ca.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share.ca_11.1.1\adf-share-base.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.adf.share_11.1.1\adflogginghandler.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xmlef_11.1.1\xmlef.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.bali.share_11.1.1\share.jar;C:\Oracle\Middleware\modules\com.bea.core.apache.xercesImpl_2.8.1.jar;C:\Oracle\Middleware\modules\glassfish.jaxb_1.0.0.0_2-1-9.jar;C:\Oracle\Middleware\modules\javax.xml.bind_2.1.1.jar;C:\Oracle\Middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.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 oracle.MovieFacadeClient
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; 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.MovieFacadeClient.getInitialContext(MovieFacadeClient.java:49)
         at oracle.MovieFacadeClient.main(MovieFacadeClient.java:13)
    Caused by: java.net.ConnectException: t3://127.0.0.1:7101: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; 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.net.ConnectException: Connection refused: connect; 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.
    Edited by: user13272654 on Jun 18, 2010 5:02 PM

    Basically, it can't find the server.
    Is the server running?
    configured to listen on localhost?
    try 3://127.0.0.1:7001 instead.
    Check the port the server is listening on.
    Pete

  • 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

  • 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

    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

  • 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

  • Error with SessionBeans:Destination Unreachable

    Hi all,
    I'm trying to develop a simple Session Bean using Weblogic 8.1.
    While deploying i got message as ejbc successful.
    But while running client application i got following error.
    Please anyone help to resolve this.
    Thanks,
    latha
    E:\slsb>java Client
    Exception in thread "main" javax.naming.CommunicationException [Root exception i
    s java.net.ConnectException: t3://raghu:7001: Destination unreachable; neste
    d exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(Exceptio
    nTranslator.java:47)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLIni
    tialContextFactoryDelegate.java:636)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:306)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:239)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:135)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    62)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at Client.main(Client.java:12)
    Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachab
    le; nested exception is:
    java.net.SocketException: Invalid argument: connect; No available router
    to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:296)
    ... 7 more

    Please check the following:
    1. Check whether the weblogic is running on the localhost.
    2. Check the port address is right or wrong
    (I have never used weblogic so I can't tell you how to check it, if you don't know then browse the google)
    3. Change the server name to 127.0.0.1 in the client code.
    If the server is running perfectly at 127.0.0.1:7001 then there should be no problem. So check this constraints first.
    Note: I have used Websphere there are lots of ports, the one I need for lookup in websphere is the BOOTSTRAP_ADDRESS. There are many other ports also. In websphere one can create multiple profile and for that profil;e this prot address varies from 2809,2810... etc.. I don't know whether in weblogic it is called as BOOTSTRAP_ADDRESS or not. But you have ensure that the particular port for weblogic (to perform lookup) is 7001 in your m/c. Please search through google for getting information on how to know the port in weblogic.

  • VPN "Destination Unreachable"

    Trying to use VPN in Lion (to connect to a Lion Server I configured in another building), when I try to connect, it fails. Viewing console messages on the server shows my requests never arrived. So I used Wireshark to do a packet capture of en0 (my wifi is off). I think I have discovered the problem, but I don't know the solution. The packet capture shows the following error about 30 times in a row each time i try to enable VPN:
    Source: 10.0.1.4
    Destination: 10.0.1.1
    Protocol: ICMP
    Info: Destination unreachable (port unreachable)
    10.0.1.4 is my Mac and 10.0.1.1 is my AEBS. Why would attempting to initiate VPN cause this error?

    Ok, so your "in another building" reference was intended to indicate this is a remote connection, across the internet, and definitely across an insecure connection, and not (as I'd erroneously interpreted it) in a campus network at a somewhat larger school or business site.  The "in another building" can be a reference to a different IP subnet within a larger organization's internal network.
    All of which means you're not going to be using an IP router to bridge to an outer and trusted network; you'll want a gateway device, and you're probably also stuck with the morass that is NAT.  And parts of what I've referenced earlier will be wrong for your requirements.
    I'd guess that there's an IP routing configuration issue here.  A bad subnet, or a bad gateway address, would be my initial suspicion.
    As a first test, switch your iMac to the wireless connection, and see if that works.  Get it using the same path as your iPad.
    Unless you have a public static IP address, you'll (unfortunately) need NAT here (somewhere).  But the question is whether your "modem" is actually a gateway device. Iis your Airport getting a private-block address from that modem device?
    If you're getting a private-block address from the modem, then the modem has implemented NAT, or your ISP has implemented NAT gateway somewhere outside of your modem.  For instance, AT&T Uverse implements a private NAT address on the "outside" of your local modem configuration, and this then leads to very specific (and somewhat weird) private network set-up requirements for that ISP.
    What features does the modem have, and what access into its configuration are you permitted by your ISP?
    If your modem is providing gateway features (some do), and particularly if it is providing DHCP and NAT services, then I'd switch the Airport to bridged mode (AP mode), and let the modem deal with NAT and DHCP for your network.
    If your modem is providing DHCP and NAT, then switch your iMac to use what the modem is providing, and not what the Airport Express is providing.
    Above all, you do NOT want double NAT here.
    Though it probably won't help you for this specific modem (unless you can gain control of it directly or via the ISP), I prefer the following general configuration for connecting a small business network to the Internet, when the ISP requires a modem:
    The wild and wooly of the Internet,
    and which conects to modem (and the "dumber" the better; preferably a modem implemented as a "bridge" and not as a "router", and with as few features and capabilities as I can acquire from the ISP),
    and the modem then connects to a gateway device I manage  (and which is inherently also a router, and provides the NAT),
    the gateway then connects to network switches if and as needed,
    and the switch (or the gateway, if that has an embedded switch) connects to WiFi.
    And I prefer the gateway implement the NAT and VPN here, and not the WiFi device nor the modem.

  • PXE DHCP ICMP:Destination Unreachable Message

    Hi
    I have a question regarding PXE and DHCP. Is it possible to ping a machine, which is in PXE boot with a DHCP address and able to access my SCCM server? Unfortunately i cannot ping the machine and in network traffic i see:
    12913 17:00:17 01.04.2015 759.8323064  SRV-SCCMDP-501 <00> 172.16.10.66 ICMP ICMP:Destination Unreachable Message, Port Unreachable, 172.16.8.38:69 {IPv4:228}
    No firewall between the machines and is the same subnet.
    Thank you in Advance

    Hi Torsten
    Thank you for your reply. I'm in hardware pxe, so no firewall is active.
    Here is the network traffic:
    1525597 11:55:38 02.04.2015 68880.5266514  172.16.10.25 SRV-SCCMDP-501   TFTP TFTP: Read Request - File: SMSBoot\x64\wdsnbp.com, Transfer Mode: octet tsize: 0  {UDP:1483, IPv4:1477}
    1525598 11:55:38 02.04.2015 68880.5266948  SRV-SCCMDP-501   172.16.10.25 ICMP ICMP:Destination Unreachable Message, Port Unreachable, 172.16.8.38:69 {IPv4:1477}
    1525701 11:55:44 02.04.2015 68886.5143787  172.16.10.25 SRV-SCCMDP-501   TFTP TFTP: Read Request - File: SMSBoot\x64\wdsnbp.com, Transfer Mode: octet tsize: 0  {UDP:1488, IPv4:1477}
    1525702 11:55:44 02.04.2015 68886.5144115  SRV-SCCMDP-501   172.16.10.25 ICMP ICMP:Destination Unreachable Message, Port Unreachable, 172.16.8.38:69 {IPv4:1477}
    I'm lost....

  • ICMPv6 Destination Unreachable (no route to the destination)

    I deployed an IPv6 multicast using EIGRP for IPv6, hosts within the network can ping each other and multicast address (FF08::6678 and FF0E::6678); routers can see all routes in the network. However, when video is streamed from server by VLC, client cannot see the SAP announcement. Packets have been captured by Wireshark, there is an error message of ICMPv6 Destination Unreachable (no route to the destination) with the source address of the server and destination address of the client. The cable, EIGRPv6, ping command have been checked. I cannot find the fault why there is such a problem. 
    Could you please give me advice on the issue.

    Try opening the file /etc/ssh_config from the terminal (you will need to use sudo) with the editor of your choice... eg:
    sudo emacs /etc/ssh_config
    Add the following lines to the end:
    AddressFamily inet
    BindAddress x.x.x.x
    where x.x.x.x is the IP address of your computer behind your router (I use static IPs for consistent results).
    Save and see if you don't have better luck with ssh.

  • Call function destination XI exception

    Hello,
    in R3 i call to function in XI, it's follow:
    call function 'XXX'
    --destination 'XI'
    --exporting
    AA = aa
    --importing
    BB = bb
    --exceptions
    system_failure = 1
    communication_failure = 2
    other = 3
    when this call produce a exception, why sometimes I can not see anything in XI - SXMB_MONI / runtime workbench -?
    thank you very much

    HI,
    If in case the message failed at entry point i.e. RFC sender communication channel, then it would not be available in SXMB_MONI.
    You may trace it from Communciation Channel Monitoring from RWB..
    Thanks
    Swarup

  • RFC Destination Catch Exceptions

    Hello,
    I've a program with call to RFC destination 'XI' , i want to know if it is possible catch exceptions when in the other system (XI) a fault occurs, for example, the database table in which I want to insert the data is not created. Now, if this happens a dump occurs
    thanks very much,

    Hello,
    You can try this way with your RFC function module:
    CALL FUNCTION 'RFC_WRITE_FILE'
        DESTINATION FP_P_DEST
        EXPORTING
          FILE                  = L_V_NAME
          FORMAT                = L_C_BIN
          SIZE                  = L_V_SIZE
          LANGUAGE              = SY-LANGU
        IMPORTING
          SIZE                  = L_V_SIZE
        TABLES
          FILEDATA              = L_IT_FILE
        EXCEPTIONS
          SYSTEM_FAILURE        = 1  MESSAGE L_V_RFC_MESS
          COMMUNICATION_FAILURE = 2  MESSAGE L_V_RFC_MESS
          ILLEGALNAME           = 3
          OTHERS                = 6.
      CASE SY-SUBRC.
        WHEN 0.
        WHEN 1.
        WHEN 2.
        WHEN 3.
        WHEN 6.
      ENDCASE.
    The SY-SUBRC value can be captured this way. Hope this helps.
    BR,
    Suhas
    Edited by: Suhas Saha on Mar 24, 2009 4:14 PM

  • Raw Socket always drop packets and return Destination Unreachable

    Ho folks,
    I have an application program that opens a raw socket to expect for UDP message incoming from the network.
    However everytime I receive a package the Solaris 10 OS return a ICMP - Destination (port) unreachable, and no message
    is send to my application.
    I did test the same application in linux and it worked well, all that I have to do was disable ICMP responses using iptables.
    Just to make things clear:
    In linux the OS was sending the ICMP - Destionation (port) unreachable, however my program was
    receiving the packets anyway. So just to stop those messages I did use the iptables. However, in
    Solaris 10 the ICMP response is sending back and no message is forward to my application.
    Would your guys help me to solve that?
    Thanks in advance

    Folks, here I go again...:-)
    I have been spent some time, trying to figure out why it is not work. I read in books and internet, that BSD raw sockets DO NOT allow us to receive TCP/UDP packages. However the linux implementation DOES allow. That is because it work in linux but not in solaris.
    Given that, such information is 100% true (book: Unix NetworkProgramming, 3rd edition), I would like to ask your guys what I can do to solve my problem.
    Basically what I need is create an application that:
    1) Allows to bind thousand of sockets at the same time (it is a media server that handles thousand of RTP connections)
    This I believe I can do using socket multiplexing (e.g. select() )
    2) Read not only the packet data, I need to retrieve the whole packet address (including IP, UDP, Upper Layers...)
    When using SOCK_DGRAM with IPPROTO_UDP, I can get the messages but I can't get the IP header
    3) Uses something like raw socket to send messages, here I believe I can use raw socket with no problem, is just sending messages
    Thanks and Regards

  • Udp client: destination port unreachable question

    Hello,
    I used "trivial" UDPClient / Server example to send datagrams from one local interface (eth1) on my Linux box to Datagram server on yhe host not included into local routing table and I tried to capture outgoing udp traffic on interface eth1. I've got IOException
    "ICMP: destination unreachable" and I only could capture outgoing
    packets on loopback interface ( with Ethereal). Can someone help to
    resolve my confusion: I thought UDP is "connectionless", e.g. will be
    sent regardless. What does ICMP have to do with it and why does this
    traffic appear on loopback interface?
    Thank you,

    If you are using a specific destination it still has to route.

  • JMSAn error occurred while forwarding a message for distributed destination

    Hi,
    i have getting issue with JMS Server delivery fail, below is the errors
    ####<Aug 24, 2012 2:03:54 PM CDT> <Warning> <JMS> < <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default
    (self-tuning)'> <<WLS Kernel>> <BEA1-0979336B7FF44582D27D> <> <1345835034568> <BEA-040498> <An error occurred while forwarding a message for distribute
    d destination member SystemModule-0!d4a JMS Server@D Distributed Topic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExcepti
    on: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, java.rmi.ConnectException: Destina
    tion unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, jav
    a.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination
    weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[
    8011,8011,-1,-1,-1,-1,-1]:d:d4a, java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, jav
    a.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination
    at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:155)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
    at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:492)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:488)
    at weblogic.jms.backend.BEForwardingConsumer.pushMessages(BEForwardingConsumer.java:300)
    at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:256)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:d:d4a, java.rmi.Con
    nectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, jav
    a.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    ####<Aug 24, 2012 2:03:54 PM CDT> <Warning> <JMS> <dal604se113com> <a> <[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default
    (self-tuning)'> <<WLS Kernel>> <BEA1-0979336B7FF44582D27D> <> <1345835034568> <BEA-040498> <An error occurred while forwarding a message for distribute
    d destination member SystemModule-0!d4a JMS Server@D Distributed Topic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExcepti
    on: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, java.rmi.ConnectException: Destina
    tion unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:dsa, jav
    a.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination
    weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[
    8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, jav
    a.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination
    at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:155)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
    at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:492)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:488)
    at weblogic.jms.backend.BEForwardingConsumer.pushMessages(BEForwardingConsumer.java:300)
    at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:256)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.rmi.RemoteException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, java.rmi.Con
    nectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with -2037322150112737172S:10.110.7.114:[8011,8011,-1,-1,-1,-1,-1]:ds:ds4a, jav
    a.rmi.ConnectException: Destination unreachable; nested exception is:
    java.net.SocketException: Connection reset; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    Edited by: Ikhan on Aug 29, 2012 4:00 AM
    Edited by: Ikhan on Aug 29, 2012 4:01 AM

    The distributed topic forwarders replicate messages to every member of a "replicated distributed topic". They will report errors if intra-cluster communication is interrupted or if servers in the cluster shut down. I recommend checking your server logs to see if other errors/warnings exist, and, if you suspect an intra-cluster communication problem, consulting the cluster troubleshooting guide(s) in the edoc.
    Most newer apps (apps hosted on versions 10.3.4 or higher) should consider using the new "partitioned distributed topics" instead of "replicated distributed topics". These don't use forwarders and scale better.
    HTH,
    Tom

  • Stoping Weblogic Server -Exception

    Hi,
    I get following exception on trying to stop the server
    [weblogic@igbu-apps ~]$ /u01/Oracle/Middleware/user_projects/domains/base_domain/bin/stopWebLogic.sh MyServer http://10.177.188.90:7001
    Stopping Weblogic Server...
    java.lang.RuntimeException: Error: JMX connector server communication error: null
    at oracle.jrockit.management.server.Messages.error(Messages.java:109)
    at oracle.jrockit.management.server.Messages.error(Messages.java:123)
    at oracle.jrockit.management.server.Agent.main(Agent.java:158)
    at oracle.jrockit.management.server.Agent.agentmain(Agent.java:94)
    at oracle.jrockit.management.server.Agent.start(Agent.java:207)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at jrockit.management.AgentStarter.startAgent(AgentStarter.java:135)
    Caused by: oracle.jrockit.management.server.AgentError
    at oracle.jrockit.management.server.JMXConnector.startNewServerImpl(JMXConnector.java:82)
    at oracle.jrockit.management.server.RemoteJMXConnector.newServer(RemoteJMXConnector.java:233)
    at oracle.jrockit.management.server.sun.RemoteJMXConnectorImpl.newServer(RemoteJMXConnectorImpl.java:112)
    at oracle.jrockit.management.server.RemoteJMXConnector.startNewServer(RemoteJMXConnector.java:181)
    at oracle.jrockit.management.server.JMXConnector.start(JMXConnector.java:64)
    at oracle.jrockit.management.server.Agent.start(Agent.java:62)
    at oracle.jrockit.management.server.Agent.main(Agent.java:156)
    ... 7 more
    Caused by: java.rmi.server.ExportException: Port already in use: 7091; nested exception is:
    java.net.BindException: Address already in use
    at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:310)
    at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
    at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
    at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
    at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:188)
    at oracle.jrockit.management.server.sun.SunRMIExporter.exportObject(SunRMIExporter.java:36)
    at javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:84)
    at javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:76)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:388)
    at oracle.jrockit.management.server.JMXConnector.startNewServerImpl(JMXConnector.java:80)
    ... 13 more
    Caused by: java.net.BindException: Address already in use
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
    at java.net.ServerSocket.bind(ServerSocket.java:328)
    at java.net.ServerSocket.<init>(ServerSocket.java:194)
    at java.net.ServerSocket.<init>(ServerSocket.java:106)
    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
    at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:649)
    at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:299)
    at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
    at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:393)
    at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:129)
    at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:188)
    at oracle.jrockit.management.server.sun.SunRMIExporter.exportObject(SunRMIExporter.java:36)
    at javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:84)
    at javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:75)
    at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:388)
    at oracle.jrockit.management.server.JMXConnector.startNewServerImpl(JMXConnector.java:80)
    at oracle.jrockit.management.server.RemoteJMXConnector.newServer(RemoteJMXConnector.java:233)
    at oracle.jrockit.management.server.sun.RemoteJMXConnectorImpl.newServer(RemoteJMXConnectorImpl.java:112)
    at oracle.jrockit.management.server.RemoteJMXConnector.startNewServer(RemoteJMXConnector.java:181)
    at oracle.jrockit.management.server.JMXConnector.start(JMXConnector.java:64)
    at oracle.jrockit.management.server.Agent.start(Agent.java:62)
    at oracle.jrockit.management.server.Agent.main(Agent.java:156)
    at oracle.jrockit.management.server.Agent.agentmain(Agent.java:93)
    at oracle.jrockit.management.server.Agent.start(Agent.java:206)
    ... 5 more
    Could not create the Java virtual machine.
    Done
    Stopping Derby Server...

    Hi Fabian,
    I tried wat u said but i am still unable to stop the server. Am i doing something wrong?
    [weblogic@iapps ~]$ /u01/Oracle/Middleware/user_projects/domains/base_domain/bin/stopWebLogic.sh wlsUserID wlsPassword http://10.177.255.25:9002
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Connecting to http://10.177.255.25:9002 with userid wlsUserID ...
    This Exception occurred at Tue Dec 18 07:32:26 IST 2012.
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: http://10.177.255.25:9002: Destination unreachable; nested exception is:
            java.net.ConnectException: Connection refused; No available router to destination]
    Problem invoking WLST - Traceback (innermost last):
    File "/u01/Oracle/Middleware/user_projects/domains/base_domain/shutdown.py", line 3, in ?
    File "<iostream>", line 22, in connect
    File "<iostream>", line 648, in raiseWLSTException
    WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at http://10.177.255.25:9002
    Use dumpStack() to view the full stacktrace
    Done
    Stopping Derby Server...
    [weblogic@-apps bin]$

Maybe you are looking for