PQ98256: HEAVY INTER-SERVER TRANSACTIONAL WORK CAN CAUSE A SERVER TO APPEAR TO HANG. | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When running a heavy distributed workload across two servers using interop mode, one of the servers appeared to hang. That is, no new work was being started, and transactions were not completing successfully.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server users. * **************************************************************** * PROBLEM DESCRIPTION: Heavy inter-server transactional work * * can cause a server to hang * **************************************************************** * RECOMMENDATION: * **************************************************************** When running a heavy distributed workload across two servers using interop mode, one of the servers appeared to hang. That is, no new work was being started, and transactions were not completing successfully. The problem was caused by the subordinate server holding a lock when regsitering back to the superior upon receipt of a transaction.Problem conclusion The CoordinatorImpl class will be updated so that when a transaction is imported from another server, the registration back to the superior server will be done while not holding a lock. This fix is available via iFix PQ98256.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ98256
IBM Group: Software Group
Modified date: Feb 14, 2005
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.