PK04470: MESSAGE-DRIVEN BEANS STOP RECEIVING MESSAGES AFTER UPGRADE TO WEBSPHERE APPLICATION SERVER V5.1.1.4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Due to an error in one of the APARs that was included in Cumulative Fix 4 (V5.1.1.4) for WebSphere Application Server V5.1.1, message-driven beans (MDBs) will only process a small number of messages after starting. Additional messages will remain on the queue or topic and the MDB will not receive them. The number of messages that the MDB will receive after it starts is equal to the Maximum sessions setting on the listener port that the MDB is associated with. . This problem only occurs in WebSphere Application Server V5.1.1.4, but it impacts all users of MDBs at the V5.1.1.4 level.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server version 5.1.1.x * * users * **************************************************************** * PROBLEM DESCRIPTION: After several hours of a long-running * * test, the application Message-Driven * * Beans (MDBs) stopped receiving * * messages. * **************************************************************** * RECOMMENDATION: * **************************************************************** This i-fix prevented a three way deadlock which was the original error. Once all the server sessions have been used the queue agent will block until another one becomes available. The problem here was that when a server session was returned to the pool the queue agent would pick it up and the pool would become empty again. It would then continue to block due to the pool being empty even though it had just obtained a server session. The only way it would come out of this is if two server sessions became available at the same time.Problem conclusion The call to obtain a server session was moved out of the while loop that ensures the pool is not empty. The fix for this APAR is currently targeted for inclusion in 5.1.1.5. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 10A
Software edition:
Reference #: PK04470
IBM Group: Software Group
Modified date: Jun 26, 2007
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.