Saturday, December 13, 2014

java.net.ConnectException,Bootstrap to server failed while deploying the compoite - Orace SOA Suite

 java.net.ConnectException,Bootstrap to server failed while deploying the compoite - Orace SOA Suite

Sometimes we may receive the following exception while deploying the composite to Oracle SOA Suite server using even though the sever is running fine and reachable.

oracle.rc.asadapter.connection.ConnectionException
at oracle.rc.asadapter.weblogic.connection.spi.Weblogic10JndiProvider.getPresentation(Weblogic10JndiProvider.java:86)

Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://127.0.0.1:8000: Bootstrap to localhost/127.0.0.1:8000 failed. It is likely that the remote side declared peer gone on this JVM]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)

Caused by: java.net.ConnectException: t3://127.0.0.1:8000: Bootstrap to localhost/127.0.0.1:8000 failed. It is likely that the remote side declared peer gone on this JVM

Caused by: java.rmi.ConnectException: Bootstrap to localhost/127.0.0.1:8000 failed. It is likely that the remote side declared peer gone on this JVM
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:334)


This issue can be resolved by configuring valid machine IP or complete name of the machines, including the domain extension as listen address in weblogic server.



On client side,  enter the host entry for the server in the hosts file -C:\Windows\System32\drivers\etc




5 comments:

  1. The information shared is very much useful Thanks for sharing it
    Hadoop Training in Chennai

    ReplyDelete
  2. It's the best time to make a few planning for the future and the time has come to be cheerful. I've perused this post and in the event that I would I am able to need to propose you few fascinating things or suggestions. You can write next articles alluding to this article. I desire to read in detail appreciably more things about it..
    SEO Training in Chennai|SEO Training|SEO Course in Chennai

    ReplyDelete
  3. The solution about /etc/hosts suggested here helped us to solve our JNDI connection issue between webMethods and Weblogic. Thanks!

    ReplyDelete
  4. The solution suggested in this blog about /etc/hosts file helped us to resolve the JNDI connection from webMethods to Weblogic server. Thanks!

    ReplyDelete
  5. It Worked. Thanks for the solution!!

    ReplyDelete