PQ57895: WEB GROUP NOT FOUND/DEFINED ERRORS DUE TO NATIVEGETREQUESTURI CALL RESULT ERROR. 404 RETURNED TO BROWSER. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer experienced 404 Web Group Errors when stressing his system. The errors appear showing the nativeGetRequestURI() method returning an erroneous Web application (a port, part of the URI, a TCP number, etc. -- not the expected URI). This was causing the 404 Error: ServletReques X Web Group Not Found com.ibm.servlet.engine.WebGroupNotFoundException: The web group nnn.nnn.nn.nnn has not been defined. This method does an HTTPD_extract for the URI, and the -vv trace shows that the HTTP server was returning the correct URI. The URI extracted becomes corrupted in nativeGetRequestURI().Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * Version V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: The customer experienced 404 Web Group * * Errors when stressing his system. * **************************************************************** * RECOMMENDATION: * **************************************************************** The customer experienced 404 Web Group Errors when stressing his system. With tracing enabled, the native.log for the Plug-In shows the nativeGetRequestURI() method returning an erroneous Web application (a port, part of the URI, a TCP number, etc. --not the expected URI). This was causing the 404 Error: ServletReques X Web Group Not Found com.ibm.servlet.engine.WebGroupNotFoundException: The web group nnn.nnn.nn.nnn has not been defined. The nativeGetRequestURI() method does an HTTPD_extract for the URI. The VV trace shows that the extract for the URI returns the correct URI, but the nativeGetRequestURI() method returns the "port number", instead of the actual URI passed. The problem was caused in nativeGetRequestURI() because the memory used for the extract call was not initialized, resulting in a memory corruption with successive calls to extract the URI.Problem conclusion The 404 errors are caused when the method nativeGetRequestURI() returns a bad URI as the result of memory getting corrupted upon successive HTTPD_extract calls to extract the URI. This problem is corrected by initializing the memory before extracting the URI in the nativeGetRequestURI() method. This change affects COMPID 5655A9800 R401 for z/OS and OS/390. The code changes are stored in CMVC under defect PQ57895. 401Y EJSCASIN EJSCCLAS EJSCCMSV EJSCCNFG EJSCJNUT EJSCJNWR EJSCLOAD EJSCLOGR EJSCOEUT EJSCOSUT EJSCPLUG EJSCPLUT EJSCPOOL EJSCPROP EJSCRULS EJSCSTUB EJSCSVHS EJSCVALD EJSCVERS EJSCWSUT EJSLNLS EJSTLDAT EJSXASIN EJSXJVMX * Cross Reference between External and Internal NamesTemporary 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 #: PQ57895
IBM Group: Software Group
Modified date: Apr 1, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.