PQ63671: XMLCONFIG BEING NON-TRANSACTIONAL CAUSES DATABASE CORRUPTION DUETO MULTIPLE CLIENTS UPDATING THE SAME DATA | |||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description XMLConfig needs a transactional mechanism to prevent concurrently running clients from modifying the same data. Because each XMLConfig operation is a transaction, but there is no transactional nature for the entire import, overlapping imports can leave the database in an inconsistent state.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users who * * sometimes get database corruption. * **************************************************************** * PROBLEM DESCRIPTION: Running multiple copies of XMLConfig * * simultaneously can cause corruption of * * data in admin repository. * **************************************************************** * RECOMMENDATION: * **************************************************************** Running multiple copies of XMLConfig simultaneously can cause corruption of data in admin repository.Problem conclusion Changes were made to XMLConfig client codes and a new bean was added in the adminserver to correct this problem.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ57352 APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ63671
IBM Group: Software Group
Modified date: Jul 30, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.