My Oracle Support Banner

File Persistant Store Connection Factory In JMS Is Not Supporting XA Transactions In WLS 12.2.1.2 (Doc ID 2374952.1)

Last updated on MAY 31, 2019

Applies to:

Oracle WebLogic Server - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Configuration:

1. First WebLogic domain containing the JMS Modules with connection factory and Distributed Queue where the messages will be pushed and consumed from. QueueSend.java program can be run to send the messages to the Queue.

2. Second WebLogic domain where the MDB application will be deployed to use Foreign Server to connect to the JMS queue on the 1st domain. Sample MDB application can be used to achieve this.

3. We see that XA transactions are not working in JMS when Administration Port is enabled for SSL for the AdminServer in the 1st domain getting below error: (Note that the JTA timeout is set to 300 seconds)

<JTA> <app2-devjms1.oracle.com> <devjms1-MS2> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <c3c4f89c-1247-425e-a8d4-7e4c5a367461-00000070> <1510003820555> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-111015> <The commit operation for transaction BEA1-0B26041661E9B3977E92 timed out after 303 seconds.>

  When Administration Port is not enabled, then there is no issue in XA transaction.

4. This time if we monitor the Queue, then the messages go to Message Pending and doesn't get consumed by the consumer even if consumer counts are being shown



Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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