PQ75497: REDEPLOY OF WEB APPLICATION RESULTS IN BBOJ0037E AND BBOJ0036E WHEN USING THE IBM HTTP SERVER WITH THE LOCAL REDIRECTOR PLUGIN. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When redeploying an application, the following steps are taken: 1) Delete the old application in one conversation, then commit, and activate. 2) Redeploy the new application in a new conversation, then commit and activate. After this, attempting to run your application without recycling the HTTP Server, will result in messages in your control region log similar to the following: BBOJ0037E APPLICATION ID "B92CAE911C71C601000000CC0000000289466" IN WEBSPHERE FOR z/OS SERVER "xxxxxx" IS NOT A VALID APPLICATION BBOJ0036E COULD NOT LOAD APPLICATION "UNKNOWN" MODULE "UNKNOWN" IN WEBSPHERE FOR z/OS SERVER "xxxxxx" Exception messages from loadBMD or loadBeanMetaData may also be seen along with the BBOJ0037E and BBOJ0036E messages: com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is: com.ibm.websphere.csi.CSIException: WS390BeanMetadataStore exception: classloader == null At this point, the application will not run, and clients requesting the application will receive 404 Not Found errors at the browser.Local fix Recycle the HTTP Server.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: The Application was redeployed as * * described below. * * * * 1) Delete the old application in one * * conversation, then commit, and * * activate. * * 2) Deploy the same application in a new * * conversation, then commit and * * activate. * * After this, attempting to run the * * application without recycling the * * HTTP Server, will result in the * * following messages in the control * * region log. * * * * BBOJ0037E APPLICATION ID * * "B92CAE911C71C601000000CC0000000289466" * * IN WEBSPHERE FOR z/OS SERVER "xxxxxx" * * IS NOT A VALID APPLICATION * * * * BBOJ0036E COULD NOT LOAD APPLICATION * * "UNKNOWN" MODULE "UNKNOWN" IN WEBSPHERE * * FOR z/OS SERVER "xxxxxx" * * * * At this point, the application will not * * run, and clients requesting the * * application will receive 404 Not Found * * errors at the browser. * **************************************************************** * RECOMMENDATION: * **************************************************************** A JNDI Cache of all the RemoteWebAppBean Objects are maintained. When the application was redeployed this cache was not updated with the newly deployed RemoteWebAppBean. So when the clients accessed the redeloyed WebApplication, they were trying to access the old WebApplication which was no longer valid. This caused the server to return a 404 Http Response code.Problem conclusion The JNDI Cache containing the RemoteWebAppBean Objects were updated when an Application was redeployed. APAR PQ75497 is associated with SERVICE LEVEL W401511 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 #: PQ75497
IBM Group: Software Group
Modified date: Sep 5, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.