|
| Problem | Websphere Application Server version 3.5.x, when Application Server brings down and brought back up appserver accepts requests from plug-in before all webapps are fully initialized. This symptoms of problem failed requests and browser reports with error 500 (Internal Server Error). | | | | Solution | Question: Why do you see the error 500 (Internal Server Error) in browser?
Answer: Error 500 is HTTP error which indicates that Application Server is not fully initialized or in running state even thus you will see the PID in tracefile.
Check this open an admin console and see if the application server is current state is running. This is working as design in websphere architecture. This behavior is cause under load when appserver started. Websphere recommend starting with clean shutdown and startup. When AppServer started you will see PID which is own JVM, but at same time we have no idea how many other classes in pipe line for initializing and we see error because JVM is started but all classes is not load there for when request is made in load environment the browser received the error 500 which is Internal Server Error. This is normal behavior of WAS (WebSphere Application Server) 3.5.x.
For 3.5, plug-in own the listening port, but we don't control when the port is opened - the engine tells us when to initialize the transport. It would be up to the engine to hold off initializing the transport until the webapps were up, if possible. (I wouldn't guarantee it's easily possible for them, given some of the dependencies in the initialization). And there isn't any delay you can set in the plug-in’s to wait between the time the server is marked up and the time we actually start sending request. The idea smells of a hack to me - something that would only work right in the majority of cases if you set a ridiculously high delay. (Think of the wide variation of application server startup times you can get on a single machine, without even adding/changing webapps).
This is a design limitation within 3.5.X. This problem does not exist in 4.0.X. To address the limitation, the customer would need to migrate to WAS 4.0.X. | |
| | | | Historical Number | PMR 21503
B004
C000 | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Classloader Operating system(s): Multi-Platform Software version: 3.5 Software edition: Advanced Reference #: 1114198 IBM Group: Software Group Modified date: 2003-07-04
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|