PQ81037: WEBSPHERE DOES NOT RELOAD THE PROPERTIES FILES WHEN YOU UPDATE THE EAR FILE. | |||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description When updating an enterprise application ( stop ear, uninstall, install and start ear) the properties files are not reloaded. So the previous property files are useds. Not until they recycle the application server will the new property files be reloaded. This is due to the "URLConnection" caching the connection even after the app is reinstalled.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application server users. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere does not reload properties * * files when you update the EAR file * * without server restart * **************************************************************** * RECOMMENDATION: * **************************************************************** If customer updates the EAR file with new properties files inside, WebSphere may not correctly load these files without a server restart. In that case, customer may see application loading contents from the original properties files or even have problem in loading the files.Problem conclusion Code change has been made to disable URLConnection caching which is by default enabled in JDK.Temporary fix Test fix has been provided to customer.Comments
APAR is sysrouted FROM one or more of the following: 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 #: PQ81037
IBM Group: Software Group
Modified date: Nov 20, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.