[Building Sakai] Wicket related JVM death on Java 1.6

[Earle Nietzel]

I noticed it seems to work fine on 1.5 and not on 1.6 and also saw

(Ljava/lang/Object;)V

Try adding this to your jvm options when using java 1.6 should fix the 
problem.

-Dsun.lang.ClassLoader.allowArraySyntax=true

Earle



From:
Steve Swinsburg <steve.swinsburg at gmail.com>
To:
David Horwitz <david.horwitz at uct.ac.za>
Cc:
sakai-dev <sakai-dev at collab.sakaiproject.org>
Date:
01/11/2010 06:49 AM
Subject:
Re: [Building Sakai] Wicket related JVM death on Java 1.6
Sent by:
sakai-dev-bounces at collab.sakaiproject.org



Hi David,

That class is a part of the Serialization that Wicket handles. Can you 
send me the crash log and I'll follow it up on the Wicket lists.

Do you mean this version of the SCORM player?
https://svn.edia.nl/edia-sakai/edia-sakai-scorm/branches/2.5.3/

Unfortunately it uses a very old version of Wicket, wrapped inside Sakai 
Wicket, which is an old version of the 1.3 series, possibly even 1.3.0. 
This old version is most likely the cause.

If possible, you could try to upgrade the Wicket version that Sakai Wicket 
uses to 1.3.7, which is the latest (and last) in the 1.3 series.  It 
should be fully compatible. Wicket is on the 1.4 branch now (almost 1.4.6 
in fact), but its an API change and introduces generics. Ideally, Sakai 
Wicket should be upgraded, tagged for Wicket 1.3.7 so older tools can use 
it, then deprecated. I've extracted the components it provides into 
separate parts which means no dependency on Sakai Wicket at all, and easy 
upgrades when new Wicket versions are released.

cheers,
Steve



On 11/01/2010, at 6:37 PM, David Horwitz wrote:

> 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
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to 
sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of 
"unsubscribe"

[attachment "smime.p7s" deleted by Earle Nietzel/ADM/Marist] 
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to 
sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of 
"unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100111/86ad5084/attachment.html