My Oracle Support Banner

"oracle.bam.adapter.adc.ADCManagedConnectionFactory.getCachedConnection" Stuck Threads while Using BAM Adapter when BAM Server is Down (Doc ID 1564113.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle BAM (Business Activity Monitoring) - Version and later
Information in this document applies to any platform.


On : version, BAM Analysis Engine

When BAM Adapter is configured without batching mode and if the BAM Server is down, calls made from the BAM Adapter through a BPEL Process are getting stuck with the below trace


  -- Blocked trying to get lock: java.lang.String@1407399e[fat lock]

The issue can be reproduced at will with the following steps:
1. Call BAM through BAM Adapter from BPEL
2. Disable batching in BAM Adapter (Default)
3. Stop the BAM Server and all calls to BAM will get stuck.


 The product is working as designed. When the BAM Server is down the BAM Adapter will retry the connection to the BAM server.


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.