BAM JMS connector fails when one JMS server is unavailable in active passive mode
Last updated on MARCH 29, 2007
Applies to:Oracle Application Server Integration BAM - Version: 10.1.3
This problem can occur on any platform.
JMS servers are running in FT mode (Active-Passive mode). If one JMS server goes DOWN (stops), then oracle BAM will not be able to process the messages.
Expect BAM connects to the standby server if the active JMS server is unavailable
The issue can be reproduced at will with the following steps:
- JMS servers are running in FT mode. BAM connectors initially point to FT configuration
(Active-Passive JMS servers) and work fine.
- Stop BAM plans and change the Enterprise Message Source's JNDI URL to point to the stand-by JMS Server.
- Enable the Plan monitoring. The plans show as running but keep restarting because of failure.
- The JMS console shows the BAM connectors as offline and messages continue to grow.
- Restarting the oracle BAM application too will not help, because it never tries to connect to
the active JMS server.
- Change the Enterprise Message source's JNDI URL to point to the FT configuration.
- Restart the BAM plan monitoring.
- The JMS console shows the BAM connectors as online and all the pending messages are flushed.
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