PQ61931: XMLCONFIG CREATES WRONG SYSTEM-PROPERTIES ENTRY | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Abstract: XMLConfig creates wrong system-properties entry . System Type: Sun Ultra 10 Operating System: SUN Product Group: Compilers, Development Toolkits and Debuggers . Environment: WebSphere Application Server 4.0.3 Iplanet Webserver 4.2 Oracle 8.1.7 Sun Solaris 8 . Problem: Hello Support . The customer found the following problem when creating an new application server using XMLConfig. . Here is the XML-File we use to create the application server: . <?xml version="1.0"?> <|DOCTYPE websphere-sa-config SYSTEM "file:///$XMLConfigDTDLocation$$dsep$xmlconfig.dtd"> . <websphere-sa-config> <node name="wsmajestix" action="locate"> <application-server name="as_test" action="create"> <jvm-config> <system-properties> <property name="ws.ext.dirs" value="/tmp/somjor.zip"/> </system-properties> </jvm-config> </application-server> </node> </websphere-sa-config> . We integrate the Component Broker ORB, this is why we have to set ws.ext.dirs to /tmp/somojor.zip. . Now, the import itself does work without problems. However, if I start the created application server it just hangs indefinitely. . If I create an application server from the console and define the system property ws.ext.dirs in the JVM settings with the console, I'm able to start the application server without any problems. . If I make an XMLconfig export of both configurations (import and console way) and compare the files I find the following difference: . XMLConfig -import does create two XML tags defineing the ws.ext.dir system property while the console way only leads to a single XML ta for ws.ext.dirs. . XMLConfig does create the following structure: . <application-server name="as_test" action="update"> ......... <system-properties> <property name="ws.ext.dirs" value="/tmp/somjor.zip"/> </system-properties> ................... <jvm-config> .... <system-properties> <property name="ws.ext.dirs" value="/tmp/somjor.zip"/> </system-properties> .... </jvm-config> ........... </application-server> . It creates a <system-properties> section directly below the <application-server> section. This was not what I asked for when I initially imported my XML file. The </system-properties> section directly below the <application-server> section is empty if I define the appl. server using the admin console.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of XMLConfig for WebSphere * * Application Server 4.0 release. * **************************************************************** * PROBLEM DESCRIPTION: XMLConfig creates wrong system- * * properties entry. * **************************************************************** * RECOMMENDATION: * **************************************************************** XMLConfig creates a <system-properties> directly below the <application-server> apart from also creating under <jvm-config> section. The <system-properties> should only appear under <jvm-config> section.Problem conclusion Fixed code in ApplicationServerConfig.java file to correct this problem.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 #: PQ61931
IBM Group: Software Group
Modified date: Jun 17, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.