Hi,

This came up on another list I am part of, and being a member of this list, 
thought I'd ask here to see if this is a known fixed issue. This is with an app 
written using Wicket 1.3.0. Essentially, the JVM crashed with this error under 
Java 1.6, the same app runs fine under Java 1.5:

#
# 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

Some relevant parts from the log:

Stack: [0x00000000488b2000,0x00000000489b3000],  sp=0x00000000489af470,  free 
space=1013k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
J  
org.apache.wicket.util.io.WicketObjectOutputStream.writeObjectOverride(Ljava/lang/Object;)V

2aac13c5d000-2aac13c81000 r-xs 0017e000 fd:01 1204727                    
/usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-1.3.0.jar
2aac13c81000-2aac13c83000 r-xs 0002d000 fd:01 1204728                    
/usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-datetime-1.3.0.jar
2aac13c83000-2aac13c8e000 r-xs 0004e000 fd:01 1204719                    
/usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-extensions-1.3.0.jar
2aac13c8e000-2aac13c90000 r-xs 00004000 fd:01 1204722                    
/usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-ioc-1.3.0.jar
2aac13c90000-2aac13c92000 r-xs 00003000 fd:01 1204729                    
/usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-spring-1.3.0.jar
2aac13c92000-2aac13c93000 r-xs 00003000 fd:01 1204724                    
/usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-spring-annot-1.3.0.jar


I can send the log to interest parties, but there is only this reference to the 
Wicket class, as well as a few Wicket jars on the classpath, unless there is 
more you need to see.

So, any known issues? An upgrade is required of course, but we'd like to 
resolve what the problem was to start with.

thanks,
Steve


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to