[Building Sakai] Wicket related JVM death on Java 1.6

David Horwitz david.horwitz at uct.ac.za
Sun Jan 10 23:37:39 PST 2010


Hi All,

We hit this worrying error that our production environment. It seems
that at least some tool that use wicket via the Sakai-wicket library can
lead to JVM death when running under java 1.6, the same tool runs fine
under java 1.5. We saw this with the edia branch of the UC Davis scrorm
tool. The crash report references a wicket call:

2010-01-09 18:54:27,539 INFO http-8443-Processor23
org.sakaiproject.tool.su.SuTool - [SuTool] Username dhorwitz becoming
00011398
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00002aaaab5fa7fb, pid=21669, tid=1218128192
#
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) 64-Bit Server VM (14.3-b01 mixed mode
linux-amd64 )
# Problematic frame:
# J
org.apache.wicket.util.io.WicketObjectOutputStream.writeObjectOverride(Ljava/lang/Object;)V

#
# An error report file with more information is saved as:
# /usr/local/sakai/logs/hs_err_pid21669.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp

Any ideas/advise/fixes appreciated.


Regards

David


More information about the sakai-dev mailing list