The following error was logged in Web Server 7.0's error log file
Java HotSpot(TM) Server VM warning: Attempt to protect stack guard pages failed.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xf640a984, pid=22095, tid=25
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_03-b07 interpreted mode)
# Problematic frame:
# j com.sun.tools.javac.code.Types$SupertypeFcn.visitClassType(Lcom/sun/tools/javac/code/Type$ClassType;)V+0
#
# An error report file with more information is saved as hs_err_pid22095.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
when the following JSP 2.0 TCK request was sent to the server
GET /jsp_coresyntx_script_el_web/ElNumberCoercionTest.jsp HTTP/1.0
Have attached the test.war file containing ElNumberCoercionTest.jsp.
Also attached
hs_err_pid21784.log - JDK crash log when 1.5.0_03-b07 was run in mixed mode
hs_err_pid22095.log - JDK crash log when 1.5.0_03-b07 and -Xint were used
hs_err_pid22215.log - JDK crash log using 1.5.0_05-ea-b02
Here are the steps to reproduce the problem:
1. Install Web Server 7.0 (MS5 build)
* cd /java/re/sjsws/7.0/promoted/MS5/latest/bundles/solaris
* gunzip and untar sjsws-7.0_2006Q1-MS5-solaris-sparc.tar.gz in a temp directory
* Run ./setup from that directory and follow the instructions to install WS7
into a directory (e.g. /space/ws7)
You don't have to be root to install WS7. You can install as your userid
2. Extract the attached test.war file into some directory (/space/test)
3. Edit the web server's config file - server.xml - and increase the stack size
% cd /space/ws7/https-*/config
% edit server.xml using your fav editor and change
<stack-size>131072</stack-size>
to
<stack-size>231072</stack-size>
4. Add the web-app entry to server.xml
Add the following XML snippet in server.xml after the </search-app> element
<web-app>
<enabled>true</enabled>
<uri>/jsp_coresyntx_script_el_web</uri>
<path>/space/test</path>
</web-app>
5. Start the web server
% cd /space/ws7/https-*/
% bin/startserv
You should see messages such as the following
[19/Jul/2005:15:22:51] info (22215): WEB0100: Loading web module in virtual server [test] at [/jsp_coresyntx_script_el_web]
[19/Jul/2005:15:22:54] info (22215): Starting Servlet Engine
[19/Jul/2005:15:22:59] info (22215): Missing application web.xml, using defaults only StandardEngine[com.sun.web].StandardHost[test].StandardContext[]
[19/Jul/2005:15:22:59] info (22215): HTTP3072: [LS http-listener-1] http://hogswart:1894 ready to accept requests
[19/Jul/2005:15:22:59] info (22215): CORE3274: successful server startup
6. Access the JSP from a browser by sending a request for /jsp_coresyntx_script_el_web/ElNumberCoercionTest.jsp
7. Watch the error log for a crash. WS7's error log is /space/ws7/https-*/logs/errors
Any JDK crash logs will be saved in the 'config' directory of the server instance i.e. /space/ws7/https-*/config
If you want to add more JVM options, you can do so by editing server.xml and adding the options to any of the existing <jvm-options> elements.
I tried -Xint, -Xss2048k but could still see the crash.
###@###.### 2005-07-19 10:19:29 GMT
Java HotSpot(TM) Server VM warning: Attempt to protect stack guard pages failed.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xf640a984, pid=22095, tid=25
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_03-b07 interpreted mode)
# Problematic frame:
# j com.sun.tools.javac.code.Types$SupertypeFcn.visitClassType(Lcom/sun/tools/javac/code/Type$ClassType;)V+0
#
# An error report file with more information is saved as hs_err_pid22095.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
when the following JSP 2.0 TCK request was sent to the server
GET /jsp_coresyntx_script_el_web/ElNumberCoercionTest.jsp HTTP/1.0
Have attached the test.war file containing ElNumberCoercionTest.jsp.
Also attached
hs_err_pid21784.log - JDK crash log when 1.5.0_03-b07 was run in mixed mode
hs_err_pid22095.log - JDK crash log when 1.5.0_03-b07 and -Xint were used
hs_err_pid22215.log - JDK crash log using 1.5.0_05-ea-b02
Here are the steps to reproduce the problem:
1. Install Web Server 7.0 (MS5 build)
* cd /java/re/sjsws/7.0/promoted/MS5/latest/bundles/solaris
* gunzip and untar sjsws-7.0_2006Q1-MS5-solaris-sparc.tar.gz in a temp directory
* Run ./setup from that directory and follow the instructions to install WS7
into a directory (e.g. /space/ws7)
You don't have to be root to install WS7. You can install as your userid
2. Extract the attached test.war file into some directory (/space/test)
3. Edit the web server's config file - server.xml - and increase the stack size
% cd /space/ws7/https-*/config
% edit server.xml using your fav editor and change
<stack-size>131072</stack-size>
to
<stack-size>231072</stack-size>
4. Add the web-app entry to server.xml
Add the following XML snippet in server.xml after the </search-app> element
<web-app>
<enabled>true</enabled>
<uri>/jsp_coresyntx_script_el_web</uri>
<path>/space/test</path>
</web-app>
5. Start the web server
% cd /space/ws7/https-*/
% bin/startserv
You should see messages such as the following
[19/Jul/2005:15:22:51] info (22215): WEB0100: Loading web module in virtual server [test] at [/jsp_coresyntx_script_el_web]
[19/Jul/2005:15:22:54] info (22215): Starting Servlet Engine
[19/Jul/2005:15:22:59] info (22215): Missing application web.xml, using defaults only StandardEngine[com.sun.web].StandardHost[test].StandardContext[]
[19/Jul/2005:15:22:59] info (22215): HTTP3072: [LS http-listener-1] http://hogswart:1894 ready to accept requests
[19/Jul/2005:15:22:59] info (22215): CORE3274: successful server startup
6. Access the JSP from a browser by sending a request for /jsp_coresyntx_script_el_web/ElNumberCoercionTest.jsp
7. Watch the error log for a crash. WS7's error log is /space/ws7/https-*/logs/errors
Any JDK crash logs will be saved in the 'config' directory of the server instance i.e. /space/ws7/https-*/config
If you want to add more JVM options, you can do so by editing server.xml and adding the options to any of the existing <jvm-options> elements.
I tried -Xint, -Xss2048k but could still see the crash.
###@###.### 2005-07-19 10:19:29 GMT