PK13058: Z/OS HTTP SERVER, DURING A RESTART OF THE WEBSERVER THE PLUGIN-CFG.XML IS NOT RE-READ. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description z/OS Http Server, during a restart of the webserver the plugin-cfg.xml is not re-read. If during the first time the plugin-cfg.xml is read and there is an initialization problem, then during a webserver restart using the modify command ("/f <dgw_name>,APPL=-restart") the plugin-cfg.xml is not re-read. .. The following is the scenario that occurr for the customer experiencing the problem for which the APAR was open for. .. First, in the -vv you can see that plug-in was not initialized. .. WebSphere HTTP Plug-in for z/OS and OS/390 Version 5.0 build level W502026 release zwas502 date 03/16/05 13:37:36 is starting .. WebSphere HTTP Plug-in for z/OS and OS/390 initializing with configuration file : /http/config/plugin-cfg.xml .. ws_common: websphereUpdateConfig: Failed parsing the plug-in config file .. WebSphere HTTP Plug-in for z/OS and OS/390 initialization FAILED (rc = 4) :-( .. ErrorLog.... ■23/Sep/2005:01:25:01 +0500 IMW0438E Serverinit Error: server did not load functions from DLL module /sfopt/zWebSphere/bin/ihs390WAS50Plugin_http.so .. .. Second, if you have plug-in trace enabled, by changing the "Error" to "Trace" in the plugin-cfg.xml file <Log LogLevel="Trace" Name="/SY1/tmp/http_plugin.log"/>, then you may see the following... .. ERROR: ws_transport: transportSetServerAddress: unable to resolve host name:ETJIBMVIPA1.OPR.TEST.xxxxxxxxx.XXX ERROR: ws_server: serverAddTransport: Failed to initialize address ERROR: lib_sxp: sxpParse: End element returned FALSE for Transport. line 45 of /http/config/plugin-cfg.xml ERROR: ws_config_parser: configParserParse: Failed to parse the config file /http/config/plugin-cfg.xml ERROR: ws_common: websphereUpdateConfig: WAS_HOME = /usr/WebSphere/AppServer. If the ERROR: plugin-cfg.xml file is not located in the WAS_HOME/config directory please ERROR: set the WAS_HOME environment variable to the appropriate directory ERROR: ws_common: websphereUpdateConfig: Failed parsing the plug-in config file ... ... ERROR: ws_common: websphereInit: Failed to load the config file .. In this customer scenario, they were unable to resolved the hostname. There could be other reason, therefore open the plug-in trace and search the "error" to determine the reason for the failure. .. Also in this scenario we saw that TCP/IP was unable to resolved the hostname. .. TCP......... Local host name is ETJIBMVIPA1 TCP......... gethostname only returned ETJIBMVIPA1; __ipDomainName returned OPR.TEST.XXXXXXXXX.XXX TCP......... Can't find my own internet node address for `ETJIBMVIPA1'!! HTHostName gave "ETJIBMVIPA1.OPR.TEST.XXXXXXXXX.XXX"; sc. hostname is "ETJIBMVIPA1.OPR.TEST.XXXXXXXXX.XXX". .. This APAR will fix the problem when a customer does restart, the plugin-cfg.xml will be re-read and initialize the second time around.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The startup message of the HTTP Plugin * * for z/OS indicates the plugin started * * started successfully when in fact it * * has not. * **************************************************************** * RECOMMENDATION: * **************************************************************** The HTTP Server for z/OS is started and an attempt to start the the HTTP Plugin for z/OS fails with the following messages: ws_common: websphereUpdateConfig: Failed parsing the plugin config file. WebSphere HTTP Plug-in for z/OS and OS/390 initialization FAILED (rc = 4) :-( When the HTTP Server for z/OS is restarted the HTTP Plugin for z/OS appears to successfully initialize with the following message being presented: WebSphere HTTP Plug-in for z/OS and OS/390 initialization went OK :-) When in fact the HTTP Plugin for z/OS did not start or even attempt initialization. When the HTTP Server for z/OS is started the HTTP Plugin for z/OS reads the plugin-cfg.xml file and attempts startup. When the plugin-cfg.xml file is read a switch is set to indicate that the plugin-cfg.xml has been read. When the HTTP Server for z/OS is restarted the HTTP Plugin for z/OS tests the plugin-cfg.xml read switch. If the switch is set no attempt is made by the HTTP Plugin for z/OS to re-read the plugin-cfg.xml file. The switch is set by the HTTP Plugin for z/OS even if startup failed. This means that in those cases of startup failure for the HTTP Plugin for z/OS no attempt is made to start the HTTP Plugin for z/OS.Problem conclusion Changed the HTTP Plugin for z/OS code so that if initialization fails and the HTTP Server for z/OS is restarted the HTTP Plugin for z/OS will attempt to restart also. APAR PK13058 is associated with SERVICE LEVEL W502037 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PK13064 UK10302 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK13058.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 #: PK13058
IBM Group: Software Group
Modified date: Jan 12, 2006
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.