JMS BINDING ERRORS: BINDING.JCA-12133, BINDING.JCA-12134, BINDING.JCA-12136 (Doc ID 1380354.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version 11.1.1.4.0 and later
Information in this document applies to any platform.

Symptoms

You have created two composites publishing and subscribing messages using JMS Adapter.
You are using the following architecture:

SOA_composite_1 -> JMS adapter (publisher) -> Load balancer -> weblogic JMS Farm
SOA_composite_2 <- JMS adapter (subscriber) <- Load balancer <- weblogic JMS Farm

The following FactoryProperties are used for oracle.tip.adapter.jms.IJmsConnectionFactory:

java.naming.factory.initial=weblogic.jndi.WLIInitialContextFactory;java.naming.provider.url=http://loadbalancer:80;ClientID=myClientID

However, the system works only when
- you are sending one message at a time or
- when only publisher is enabled and subscriber is retired or vice versa or
- when the call is made directly from the composite to JMS server bypassing load balancer.

The problem is accompanied by multiple errors of the following type

BINDING.JCA-12133
ERRJMS_JMS_EXCEP.
ERRJMS_JMS_EXCEP.
Unable to create JMSConnection due to JMSException.
Please examine the log file to determine the problem.

at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:235)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:113)
at oracle.tip.adapter.jms.JMS.WLJMSConnection.<init>(WLJMSConnection.java:76)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:311)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:305)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:286)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:92)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:803)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)


and


BINDING.JCA-12134
ERRJMS_ERR_CR_TOPIC_CONS.
ERRJMS_ERR_CR_TOPIC_CONS.
Unable to create Topic consumer due to JMSException.
Please examine the log file to determine the problem.

at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:559)
at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:493)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:346)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:920)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:894)
at oracle.tip.adapter.jms.JmsDDEndpoint.onDestinationsAvailable(JmsDDEndpoint.java:175)
at weblogic.jms.extensions.JMSDestinationAvailabilityHelper$DestinationAvailabilityListenerWrapper$2.run(JMSDestinationAvailabilityHelper.java:375)
at weblogic.jms.extensions.JMSDestinationAvailabilityHelper$DestinationAvailabilityListenerWrapper.callOutListener(JMSDestinationAvailabilityHelper.java:391)
at weblogic.jms.extensions.JMSDestinationAvailabilityHelper$DestinationAvailabilityListenerWrapper.onDDMembershipChange(JMSDestinationAvailabilityHelper.java:372)
at weblogic.jms.common.CDS$DD2Listener.run(CDS.java:1237)


and


BINDING.JCA-12136
ERRJMS_ERR_CR_TOPIC_PROD.
ERRJMS_ERR_CR_TOPIC_PROD.
Unable to create Topic producer due to JMSException.
Please examine the log file to determine the problem.

at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:680)
at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:642)
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:180)
at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:337)
at oracle.tip.adapter.jms.WLSJmsInvoker.invoke(WLSJmsInvoker.java:109)
at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:166)
at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:140)


and

<Error> <RJVM> <BEA-000515> <execute failed
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '392'
java.net.ProtocolException: Tunneling result not OK, result: 'DEAD', id: '392'
at weblogic.rjvm.http.HTTPClientJVMConnection.receiveAndDispatch(HTTPClientJVMConnection.java:376)
at weblogic.rjvm.http.HTTPClientJVMConnection.run(HTTPClientJVMConnection.java:244)
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)


and


java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):host.com:7201:null:-1';



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms