PQ75346: STARTING SERVERINSTANCE IN WSAD, GET CONCURRENTMODIFICATIONEXE | |||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When starting the serverInstance in WSAD, customer intermittenly see's java.util.ConcurrentModificationException in the ConsoleLocal fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users; * * WebSphere Studio Application Developer * * Unit Test Environment users. * **************************************************************** * PROBLEM DESCRIPTION: In environments where dynamic class * * reloading is enabled (e.g. WebSphere * * Studio Application Developer Unit * * Test Environment), intermittent * * ConcurrentModificationException's may * * be encountered. * **************************************************************** * RECOMMENDATION: * **************************************************************** Classloader reloading code was not thread-safe in the particular area where file timestamp changes are detected.Problem conclusion Added synchronizing logic to the classloader so that the reload detection code is now threadsafe.Temporary fix Passing test fix up to L2.Comments
APAR is sysrouted FROM one or more of the following: PQ73332 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: 00W
Software edition:
Reference #: PQ75346
IBM Group: Software Group
Modified date: Jun 17, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.