PK27424: WEBSPHERE CONTROLLER MAY GO DOWN WITH THE ASSERTION FAILURE 'BRANCHTABLE_P != NULL' IMMEDIATELY AFTER EC3 TIMEOUT. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description There is a very small timing window where a transaction could time out while the transaction is still starting. This may happen if requests are extremely backed up, but the window is very small and it is a rare occurrence. When this occurs, it would be right after the EC3 timeout abend and the following messages are seen in the CR before it goes down, . Trace: 2006/06/27 11:40:58.130 01 t=78D0F0 c=UNK key=S2 (0000000A) Description: Log Boss/390 Error from filename: ./bbottmcr.cpp at line: 4440 error message: BBOO0021E Assertion failed: 'branchTable_p != NULL', file ./bbottmcr.cpp, line 4440. . and just before this there would an ec3/0413000x timeout in the servant with corresponding BBOO0232W message in the controller. . This apar will address this problem.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Controller Region terminates due to * * "BBOO0021E Assertion failed: * * 'branchTable_p!=NULL'file * * /bbottmcr.cpp" * **************************************************************** * RECOMMENDATION: * **************************************************************** The transaction services attempted to check for a piece of infrastructure that was no longer available due to a timeout event that occurred during the final stages of a transaction's creation. The timeout occurred due to severe system hold up in those last stages. The timeout caused the transaction infrastructure to be recycled as the transaction's creation process had not completed. This rare event caused the Controller Region to come down and traces similiar to the following to be observed in the Controller Region: Trace: xxxx/xx/xx xx:xx:xx.xxx xx t=xxxxxx c=UNK key=xx (xxxxxxxx) Description: Log Boss/390 Error from filename: ./bbottmcr.cpp at line: 4440 error message: BBOO0021E Assertion failed: ?branchTable_p != NULL?, file ./bbottmcr.cpp, line 4440. Trace: xxxx/xx/xx xx:xx:xx.xxx xx t=xxxxxx c=UNK key=xx (xxxxxxxx) Description: Log Boss/390 Error from filename: ./bbottmcr.cpp at line: 4440 error message: BBOO0021E Assertion failed: ?branchTable_p != NULL?, file ./bbottmcr.cpp, line 4440. Trace: xxxx/xx/xx xx:xx:xx.xxx xx t=xxxxxx c=UNK key=xx (xxxxxxxx) Description: Log Boss/390 Error from filename: ./bbooboai.cpp at line: 1451 error message: BBOO0006E WEBSPHERE FOR Z/OS PROCESS xxxxxxx ENDED ABNORMALLY, REASON=C9C21236.Problem conclusion Code was added to account for the timeout scenario during transaction creation. APAR PK27424 is associated with SERVICE LEVEL W502042 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PK27427 PK27445 PK27480 UK17760 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK27424.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK27424
IBM Group: Software Group
Modified date: Oct 3, 2006
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.