My Oracle Support Banner

JCAPS6 - URA jndi fails when publishing to JMQ: Unexpectd Broker Exception (Doc ID 1025956.1)

Last updated on NOVEMBER 02, 2016

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Oracle Solaris on SPARC (32-bit)
***Checked for relevance on 05-Dec-2013***


The repository-based project receives messages on a JMQ topic and publishes them to a JMQ queue. While sending the message to the queue a JMSException occurs:

A broker error occurred. :[412] Unexpectd Broker Exception: [Transaction [consumer:5883141490084992768, type=NONE]: is not started, ignoring]

The broker logs a similar error.
When the project is disabled then re-enabled, the message is received and published to the queue again (resulting in a duplicate message)

This occurs when the URA container is configured to use "jndi://" and looks up connection factories in ldap to connect to the broker.
The same project does not encounter this error when using "mq://", or when using "jndi://" and looking up JMS Grid connection factories.


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

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