When trying to sent a JMS message to a remote Weblogic Application Server the following Exception is raised:

2011-11-29 09:42:00,512[Thread-7]DEBUG RequestSender -Releasing resources
2011-11-29 09:42:00,512[Thread-7]DEBUG ChargerPinger -method : void pingPortalServer()
2011-11-29 09:42:00,518[Thread-7]ERROR PortalJMSSender -Error during portal queue lookup t3:// Bootstrap to failed. It is likely that the remote side declared peer gone on this JVM
   at weblogic.rjvm.RJVMFinder.findOrCreate(
   at weblogic.rjvm.ServerURL.findOrCreateRJVM(
   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(
   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(
   at weblogic.jndi.WLInitialContextFactory.getInitialContext(
   at javax.naming.spi.NamingManager.getInitialContext(
   at javax.naming.InitialContext.getDefaultInitCtx(
   at javax.naming.InitialContext.getURLOrDefaultInitCtx(
   at javax.naming.InitialContext.lookup(
   at com.fizzy.PortalJMSSender.<init>(


- Make sure that Remote weblogic server is up and running. Verify the host and port credentials are valid. At times even if the server is up but did go down, it may fail to connect, so restart your client app to reset the connection state.

Also make sure that JVM version of the client and destination the same or compatible else this error will occur.