How to Disable the JMS Wrappers Session Pooling for the WebLogic J2EE Containers (Doc ID 1470562.1)

Last updated on NOVEMBER 27, 2023

Applies to:

Goal

How to disable the JMS Wrappers session pooling for the WebLogic J2EE containers?

In the J2EE Specification, it states:

A J2EE container may throw a JMSException (if allowed by the method) if the application component violates these restrictions.
Application components in the web and EJB containers must not attempt to create more than one active (not closed) Session object per connection. An
attempt to use the Connection object’s createSession method when an active Session object exists for that connection should be prohibited by the container.
The container may throw a JMSException if the application component violates this restriction. Application client containers must support the creation of multiple
sessions for each connection.

JMS generic resource adapters are compliant to the J2EE specification that are actually causing the error at runtime.

For an example, in the IBM HTTP MQ Bridge adapter, the error is as follows due to the session pooling when weblogic JMS wrappers are enabled.

MQJCA1018: Only one session per connection is allowed.  The application attempted to create more than one JMS session on the same JMS connection.  This exception occurs only if the application is running in a managed environment. Modify the application so that it creates only one JMS session on a JMS connection.

Solution

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