EMS Reconnection After Jms Queues Are Restarted (Doc ID 1339873.1)

Last updated on AUGUST 05, 2016

Applies to:

Oracle BAM (Business Activity Monitoring) - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 11-December-2013***

Symptoms


2 domains :
- cluster of 2 managed servers, used exclusively as a JMS server, on which we have some UDD queues
- Bam Installation (11.1.1.3.0) on which we created some Enterprise Message Services, listening on JMS queues of first domain

If JMS server is restarted - EMS is not consuming messages from the JMS queue after JMS server is restarted ( we have to restart BAM server , which is not acceptable)

Error message on BAM side:

<Dec 23, 2010 6:39:32 PM EET> <Warning> <oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry> <BEA-000000> <Recovery thread for destination=internal.BAMSensors.SOA_To_BAM.request.handleThrowable error=oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination internal.BAMSensors.SOA_To_BAM.request failed. destination=internal.BAMSensors.SOA_To_BAM.request
oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination internal.BAMSensors.SOA_To_BAM.request failed.
at oracle.bam.common.messaging.base.operation.MessageOperationBase.onRecoveryFailedException(MessageOperationBase.java:2022)
at oracle.bam.common.messaging.api.MessageConsumerRegistry.onRecoveryFailedException(MessageConsumerRegistry.java:955)
at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1860)
at oracle.bam.common.messaging.base.operation.MessageOperationBase$3.performOperation(MessageOperationBase.java:1822)
at oracle.bam.common.messaging.base.operation.MessageOperationBase$UtilityThread.run(MessageOperationBase.java:2541)

Caused By: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination internal.BAMSensors.SOA_To_BAM.request failed.
at oracle.bam.common.messaging.base.operation.MessageOperationBase.performRecovery(MessageOperationBase.java:1974)
at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1851)
at oracle.bam.common.messaging.base.operation.MessageOperationBase$3.performOperation(MessageOperationBase.java:1822)
at oracle.bam.common.messaging.base.operation.MessageOperationBase$UtilityThread.run(MessageOperationBase.java:2541)

Caused By: weblogic.jms.extensions.ConsumerClosedException: Consumer destination was closed
at weblogic.jms.backend.BEConsumerImpl.closeWithError(BEConsumerImpl.java:730)
at weblogic.jms.backend.BEDestinationImpl.closeAllConsumers(BEDestinationImpl.java:1063)
at weblogic.jms.backend.BEDestinationImpl.shutdownInternal(BEDestinationImpl.java:867)
at weblogic.jms.backend.BEDestinationImpl.shutdown(BEDestinationImpl.java:840)
at weblogic.jms.backend.BackEnd.removeDestination(BackEnd.java:1580)
at .......
>
<Dec 23, 2010 6:39:34 PM EET> <Warning> <oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry> <BEA-000000> <Recovery thread for destination=internal.commonBAM.OSB_to_BAM.request.handleThrowable error=oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination internal.commonBAM.OSB_to_BAM.request failed. destination=internal.commonBAM.OSB_to_BAM.request
oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination internal.commonBAM.OSB_to_BAM.request failed.
at ....

Caused By: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination internal.commonBAM.OSB_to_BAM.request failed.
at ....

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