Excessive 'Transaction acknowledgement' warnings in log file (Doc ID 1026214.1)

Last updated on FEBRUARY 18, 2013

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Information in this document applies to any platform.
Information in this document applies to any platform.
***Checked for relevance on 18-Feb-2013***

Symptoms

If the JMQ broker connected to application in an HA Cluster gets restarted, JMSBC starts to generate excessive logs entries with the following exception and the application stops working (until the JMSBC is restarted)
Unexpected exception encountered while executing a JMS CC-session: javax.resource.ResourceException: JMSBC-E0711: Failed in beforeDelivery. Associated exception: javax.resource.ResourceException: JMSBC-E0711: Failed in beforeDelivery
javax.resource.ResourceException: JMSBC-E0711: Failed in beforeDelivery


In Java MQ 4.3 there are excessive log Warnings and reconnect messages in server.log. These do not affect message flow. The log shows:
com.sun.messaging.jms.JMSException: [ACKNOWLEDGE_REPLY(25)] [C4036]: A broker error occurred. :[409] [B1261]: Transaction acknowledgement could not be added because message has already been removed user=jmq, broker=localhost:20001
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.throwServerErrorException(ProtocolHandler.java:3982)

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