PM12339: WEBSPHERE APPLICATION SERVER TAKES A LONG TIME TO STOP WHEN MULTIPLE MESSAGE DRIVEN BEANS HAVE INFLIGHT WORK TO COMPLETE

Fixes are available

APAR status

Closed as program error.

Error description

A WebSphere Application Server v7 server can take a long time
to stop due to new logic added in the resource adapter that
waits for in-flight Message Driven Bean (MDB) threads before
stopping the resource adapter. Once the MDB threads complete,
the resource adapter will stop, in turn allowing the
application server to stop.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for IBM WebSphere Application Server v7     *
****************************************************************
* PROBLEM DESCRIPTION: Server shutdown waits for all           *
*                      in-flight Message Driven Bean threads   *
*                      to complete.                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Logic within the Service Integration Bus (SIBus) Resource
Adapter causes shutdown processing to wait for all Message
Driven Bean (MDB) threads to finish. For certain MDB
applications with long running onMessage() methods, this can
mean the server can could take a long time to shutdown.

Problem conclusion

This APAR introduces a new custom property that can be set on
the application server to control how long the SIBus Resource
Adapter should wait before continuing shutdown. The custom
property is set on the <Application Server> -> Server
Infrastructure -> Administration -> Custom Properties. The new
custom property is:

property: com.ibm.ws.sib.ra.inbound.impl.MDBQuiescingTimeout
value:    (value in milliseconds)
default-value: 0

A value of 0 means wait until all MDBs have finished.
A value of -1 means don't wait at all.
Any other value dictates the maximum about of time to wait
for MDBs to finish before continuing the server shutdown
process.

The property needs to be set on the application server
hosting the MDB application. The server needs to be restarted
before the property is picked up.

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
PM12339
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-15
Closed date
2010-06-24
Last modified date
2010-06-24

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
PLAT MSG COM
Fixed component ID
620800101

Applicable component levels

R300 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:
24 October 2021

Tips

PM12339: WEBSPHERE APPLICATION SERVER TAKES A LONG TIME TO STOP WHEN MULTIPLE MESSAGE DRIVEN BEANS HAVE INFLIGHT WORK TO COMPLETE

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

R300 PSY

Document Information

Share your feedback

Need support?