PM12735: THE APPLICATION ENCOUNTERS ILLEGALSTATEEXCEPTION AT SETMANAGEDCONNECTION

Fixes are available

APAR status

Closed as program error.

Error description

The  application encounters IllegalStateException at
setManagedConnection due to MCWrapper was used by another
thread.

in the system.out following error will report.

----------------------------------
10/04/13 21:41:29:758 JST&#65529; 00000026 MCWrapper E
J2CA0079E setManagedConnection
IllegalStateException : java.lang.IllegalStateException:
setManagedConnection:
 : java.lang.IllegalStateException: setManagedConnection:
 illegal state exception. State = STATE_TRAN_WRAPPER_INUSE
 MCW = 25ff25ff
at
com.ibm.ejs.j2c.MCWrapper.setManagedConnection(MCWrapper.java:79
0)
----------------------------------

 When a preTestConnection fails on a managed connection, the
 MCWrapper object is being cached twice on the error path.

Later when there are concurrent getConnection() requests on two
threads, each thread is assigned a copy of MCWrapper object.
Since both the threads pointing to the same object, any state
changes on one thread is immediately seen on another thread. As
this continues,one thread of execution fails with
IllegalStateException.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
****************************************************************
* PROBLEM DESCRIPTION: The application encounters              *
*                      IllegalStateException when              *
*                      preTestConnection fails.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The application encounters IllegalStateException at
setManagedConnection due to MCWrapper is used by another
thread.

In the system.out following error will report.
----------------------------------

10/04/13 21:41:29:758 JST &#130; &#168; 00000026 MCWrapper E
J2CA0079E setManagedConnection
IllegalStateException : java.lang.IllegalStateException:
setManagedConnection:
at
com.ibm.ejs.j2c.MCWrapper.setManagedConnection(MCWrapper.java:79
0)
----------------------------------

When a preTestConnection fails on a managed connection, the
MCWrapper object is being cached twice on the error path.

Later when there are concurrent getConnection() requests on
two threads, each thread is assigned a copy of MCWrapper
object. Since both the threads pointing to the same object, any
state changes on one thread is immediately seen on another
thread.
As this continues,one thread of execution fails with
IllegalStateException.

Problem conclusion

The code is fixed by preventing the MCWrapper object being
cached twice on error path.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM12735
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-21
Closed date
2010-05-25
Last modified date
2010-05-25

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM12735: THE APPLICATION ENCOUNTERS ILLEGALSTATEEXCEPTION AT SETMANAGEDCONNECTION

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?