PK12350: WEBSPHERE PLUGIN-CFG.XML PARSING PROBLEM | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Here is the customer's scenario: He had a virtual host that was mapped to web modules in his application. He then deleted the virtual host and created a scenario of some applications deployed and mapped to a non-existent virtual host. A uri element in the ROUTE statement (of the plugin-cfg.xml) was defined for each of the context roots in these applications. The VirtualHostGroup defined in the ROUTE, thus, pointed to a non-existing virtual host. Therefore the HTTP server could not locate the non-existent VirtualHostGroup when parsing the ROUTE element. This causes a parsing error for the plugin-cfg.xml file. The following error occurs during the startup of the HTTP server: . WebSphere HTTP Plug-in for z/OS and OS/390 initializing with configuration file : /web/webesw01/plugin-cfg.xml ws_common: websphereUpdateConfig: Failed parsing the plugin config file . WebSphere HTTP Plug-in for z/OS and OS/390 initialization FAILED (rc = 4) :-( . He manually removed the ROUTE element in the xml file and the plugin-cfg.xml could then be parsed. Although there was a discrepancy in the WAS configuration, the problem is not detected or reported during the generation of the HTTP plug-in but only surfaces at the time he brings up the HTTP server. The customer feels that this parsing error should have manifested itself earlier in this process, for example when they updated the web server plugin via the adminconsole - instead of during the time that the webserver is attempting to parse it.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The plugincfg.xml file is not properly * * updated when a virtual host which is * * associated with an web application is * * deleted. This causes the Web Server to * * fail. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a virtual host is deleted which was associated with a web application, the Route and UriGroup Name for that virtual host is not deleted from the plugincfg.xml when it is updated. If the Web Server is started using this updated plugincfg.xml, it fails with: WebSphere HTTP Plug-in for z/OS and OS/390 initializing with configuration file : /web/webesw01/plugin-cfg.xml ws_common: websphereUpdateConfig: Failed parsing the plugin config file. WebSphere HTTP Plug-in for z/OS and OS/390 initialization FAILED (rc = 4) because the VirtualHostGroup name associated with the Route statement points to a non-existent virtual host. This should be caught sooner.Problem conclusion The code was modified to skip URI generation for a module if the referencing virtual host has been deleted. The plugin config file will need to be re-generated after this fix is installed/applied. APAR PK12350 is associated with SERVICE LEVEL W502034 of WebSphere Application Server V5.0 for z/OS. If you are currently running your WebSphere Application Server and apply this fix, then you will need to re-generate the plugin config file in order for this change to take affect. This can be done using the Admin console (Environment > Update WebServer Plugin).Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PK10238 APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK12350.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK12350
IBM Group: Software Group
Modified date: Oct 4, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.