My Oracle Support Banner

Client/Server Interoperability Is Broken With 12.2.1.2 JMS Client (Doc ID 2231012.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version 12.2.1.2.0 to 12.2.1.2.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

Client/Server interop is broken with 12.2.1.2 JMS client.

Setting up the JMS bridge configuration with WLS 12.2.1.2 as the source and WLS 10.3.6 as the target. But failed with all the versions of Weblogic Server, tested with 10.3.6 , 12.1.3 , 12.2.1.0.0 as the target.

JMS bridge is in status active and forwarding messages when both source and target domains are on Weblogic 12.2.1.2. 

####<Jan 17, 2017, 11:09:08,942 PM IST> <Info> <MessagingBridge> <SATSATAP-IN> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <f4c4dc22-42bb-4e5c-8de1-57ce694dceae-00000012> <1484674748942> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-200043> <Bridge "TestBridge" failed to connect to the target destination and will try again in 25 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: Failed to start the connection
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1747)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:574)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:264)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:194)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:862)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:92)

-------------- Linked Exception ------------
weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException.
weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.rjvm.RJVMImpl.gotExceptionReceiving(RJVMImpl.java:1230)
at weblogic.rjvm.ConnectionManager.gotExceptionReceiving(ConnectionManager.java:1216)
at weblogic.rjvm.MsgAbbrevJVMConnection.gotExceptionReceiving(MsgAbbrevJVMConnection.java:577)
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:669)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:844)

Caused by: java.io.EOFException
... 11 more

at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:324)
at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:586)
at weblogic.jms.client.JMSXAConnectionFactory.createXAQueueConnection(JMSXAConnectionFactory.java:48)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:383)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:264)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:194)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:862)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:92)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1362)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:436)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:350)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:330)

Same behaviour observed for different versions of SAF agents as well .

###<2017-04-27 11:40:15,487> <Info> <JMS> <euhslf0012vdepp> <pqs-1> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <04fc134d-35d0-4e82-a42c-537b75b47e95-00000010> <1493286015487> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-040507> <The JMS store-and-forward (SAF) forwarder failed to connect to the remote destination "t3://demuc1dv75.dev.de.pri.o2.com:44680,demuc1dv76.dev.de.pri.o2.com:44680/prepaid/jms/queue/extern/async/notification", because of javax.naming.CommunicationException: ; nested exception is:
java.io.EOFException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:78)
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:36)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:540)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:452)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:434)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at weblogic.jms.forwarder.Forwarder.connectTarget(Forwarder.java:483)
at weblogic.jms.forwarder.Forwarder.reconnect(Forwarder.java:271)
at weblogic.jms.forwarder.Forwarder.timerExpired(Forwarder.java:364)

Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.rjvm.RJVMImpl.gotExceptionReceiving(RJVMImpl.java:1230)
at weblogic.rjvm.ConnectionManager.gotExceptionReceiving(ConnectionManager.java:1216)
at weblogic.rjvm.MsgAbbrevJVMConnection.gotExceptionReceiving(MsgAbbrevJVMConnection.java:577)
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:669)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:844)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:772)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:971)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:916)
at weblogic.socket.NIOSocketMuxer.process(NIOSocketMuxer.java:596)
at weblogic.socket.NIOSocketMuxer.processSockets(NIOSocketMuxer.java:560)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:30)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:43)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:147)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:119)
Caused by: java.io.EOFException
... 11 more

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.