-
Bug
-
Resolution: Duplicate
-
P1
-
None
-
1.4.0
-
generic
-
generic
With Merlin b75, Tomcat hang.
Tomcat is a new bigapps. We deployed the same test model as we used for JWS.
Basically, it is:
1. start Tomcat server
2. run atg.core.net.URLHammer http://${SERVER}:${PORT}/index.html ${THREADS} ${COUNT} in a loop to create continuous workload for Tomcat server
Tomcat is at:
/net/jtgb4u4c/export/sail8/1.3bigapps/ws/master/dist/tomcat
source code is under "src" directory.
Output is captured in run.tomcat.out, output from tomcat server is captured
in tomcat.server.out.
After a few hours, the java processes will hang.
By killing the client, (atg.core.net.URLHammer), the server can continue
to response to new requests.
Tomcat server listens on port 3030, http://<machine name>:3030 should
take you to Tomcat index page if Tomcat server is up and running.
I left hanging processes on jtgb4u2b.
Steps to run tomcat:
1. export JAVA_HOME=<java installation dir>
2. /bs/runtomcat.ksh -server/-client, etc...
###@###.### 2001-08-14
- duplicates
-
JDK-4503136 tomcat server hang with Merlin b79 in C2 mixed mode
-
- Closed
-