PQ84322: UNRECOGNIZED CHARACTER IN THE PLUGIN-CFG.XML,CAUSED THE CONFIG PARSER TO STOP & DISPLAY "FAILED PARSING THE PLUGIN CONFIG FILE" | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description AN unrecognized character in the Plugin-cfg.xml,caused the config parser to stop and displayed "Failed parsing the plugin config file". The displayed message is as follows" .. "ws_common: websphereUpdateConfig: Failed parsing the plugin config file" .. but then a message was written to the JobLog indicating that everything was OK. .. "10.06.56 STC00085 EJS3093I WebSphere HTTP Plug-in for z/OS and OS/390 initialization went OK :-)" .. The messages in the SYSPRINT: IMW0162E Internal error running function service_exit from DLL module /usr/lpp/WebSphere/WebServerPlugIn/bin/ihs390WASPlugin_http.so .. After implementing the HTTP plugin the first HTTP request may causes a S0C4 although we see message: EJS3093I WebSphere HTTP Plug-in for z/OS and OS/390 initialization went OK :-) The service_exit gets an 0c4,initialization is indicated to be OK, but user may sees an internal error 500 (500). .. The message from CEEDUMP: CEE3204S The system detected a protection exception (System Completion Code=0C4). Location: Program Unit: Entry: configIncReferenceCount Statement: Offset: +0000005C .. The problem seems to be with the comment. The first byte after the < should be !, but on the EBCDIC host and PC it is | vertical bar. The relevant hex values are 0x4f for the vertical bar and 0x5a for the exclamation mark. ..Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: The configuration file parser failed * * and displayed an error message. * **************************************************************** * RECOMMENDATION: * **************************************************************** The customer intended to insert a comment into the configuration file. A comment is indicated by the characters <!. In the reported case the customer typed <| instead. The configuration file parser recognized the problem, stopped parsing, and issued the following error message. ws_common: websphereUpdateConfig: Failed parsing the plugin config file Then the following message was incorrectly displayed in the Job Log: 10.06.56 STC00085 EJS3093I WebSphere HTTP Plug-in for z/OS and OS/390 initialization went OK :-) The customer may see the following message(s) in the HTTP Plugin log: ERROR: lib_sxp: sxpParse: Expected '=' token; got 'Possible'. line <line #> of <path>/plugin-cfg.xml ERROR: ws_config_parser: configParserParse: Failed to parse the config file <path>plugin-cfg.xml ERROR: ws_common: websphereUpdateConfig: Failed parsing the plugin config file Other symptoms that may appear when requests are attempted through the WebSphere HTTP Plugin for z/OS and OS/390: The Customer may see the following message in the Job Log: IMW3542E SA 50335622 0.0.0.0:8881 * * DUMPING The HTTP Server will abend with an ABEND0C4 and the customer may see a CEEDUMP TraceBack entry such as: configIncReferenceCount 0F328430 +0000005C *PATHNAM Exception The Customer may see the following messages at the browser: IMW0254E ERROR 500 at the Client/browser IMW0162E Internal error running function service_exit from DLL module <path>/ihs390WASPlugin_http.so The Customer may see the following messages in the HTTP Server ErrorLog: IMW0193I OK host: 9.27.176.235 IMW0085E ABEND signal 11 has been caught for thread type 1 IMW0193I OK host: 9.27.176.235 IMW0086E Crashing request was: GET <URL> HTTP/1.1 IMW0193I OK host: 9.27.176.235 IMW0162E Internal error running function service_exit from DLL module <path>/ihs390WASPlugin_http.soProblem conclusion Changed the code in the configuration parser to pass the error indication to its caller. APAR PQ84322 is associated with SERVICE LEVEL W401610 of WebSphere Application Server version 4.0.1 for z/OS and OS/390.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
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ84322
IBM Group: Software Group
Modified date: Apr 3, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.