-
Bug
-
Resolution: Fixed
-
P1
-
6
-
b59a
-
sparc
-
solaris_8
-
Verified
With Mustang b56, SAP J2EE engine 6.3.0 cannot startup properly.
It will startup properly if b56 jre/lib replaced by b55 jre/lib.
Thus, the regression happens in build 56.
How to reproduce the problem:
1. login big5server.sfbay as root, (please contact the submitter for the password)
su - e03adm
2. /usr/sap/scripts/start_sap.ksh
3. after 15 minutes, use "jcmon.sh" to monitor the startup status.
4. At the choice prompt, choose "20", it shows "dispatcher", "server0" as "starting", while "SDM" as "running" status. However, in a successful startup, the state of all three components should change from "initial" -> "starting" -> "running".
The log file is "/usr/sap/E03/JC03/j2ee/cluster/server0/log/defaultTrace.8.trc.failure".
Please see the attached file for the stack trace.
Based on the stack trace, the failure may relate with XML engine change by the following putback in build 56.
http://jre.sfbay/restatus/reformat_event_details.jsp?event_details=/usr/local/tomcat-5.0.28/bin/../webapps/restatus/data/j2se/6/event_details-j2se-jsuttor-101005_160957.html
In the begining, I thought it may relate with resources.jar work done by Xiaobin Lu in build 56. As he suggested in order to rule out the possibility with his fix, I had tried out removing meta-index in jre/lib directory, the J2EE engine still failed at the startup with the same stack trace.
It will startup properly if b56 jre/lib replaced by b55 jre/lib.
Thus, the regression happens in build 56.
How to reproduce the problem:
1. login big5server.sfbay as root, (please contact the submitter for the password)
su - e03adm
2. /usr/sap/scripts/start_sap.ksh
3. after 15 minutes, use "jcmon.sh" to monitor the startup status.
4. At the choice prompt, choose "20", it shows "dispatcher", "server0" as "starting", while "SDM" as "running" status. However, in a successful startup, the state of all three components should change from "initial" -> "starting" -> "running".
The log file is "/usr/sap/E03/JC03/j2ee/cluster/server0/log/defaultTrace.8.trc.failure".
Please see the attached file for the stack trace.
Based on the stack trace, the failure may relate with XML engine change by the following putback in build 56.
http://jre.sfbay/restatus/reformat_event_details.jsp?event_details=/usr/local/tomcat-5.0.28/bin/../webapps/restatus/data/j2se/6/event_details-j2se-jsuttor-101005_160957.html
In the begining, I thought it may relate with resources.jar work done by Xiaobin Lu in build 56. As he suggested in order to rule out the possibility with his fix, I had tried out removing meta-index in jre/lib directory, the J2EE engine still failed at the startup with the same stack trace.