Re: JVM crash, Wicket class mentioned
For the rare JVM crash in the past this is what I've done also, however _17 is the latest so there is no upgrade. Still, we would really like to know what caused this. A Wicket class is referenced in the error. thanks, Steve On 12/01/2010, at 12:07 AM, Martin Makundi wrote: Hi! No, I remember having similar problems before and they were fixed by upgarding jvm (1.6.0_17 - 1.6.0_18 for example). ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: Hi Martin, I'll pass that on, but the JRE version is 1.6.0_17-b04 unless you mean the 14.3-b01 VM version? Heres the system info from the log: OS:SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 2 uname:Linux 2.6.16.60-0.42.5-smp #1 SMP Mon Aug 24 09:41:41 UTC 2009 x86_64 libc:glibc 2.4 NPTL 2.4 rlimit: STACK 8192k, CORE 0k, NPROC 69119, NOFILE 10, AS infinity load average:0.32 1.14 0.74 CPU:total 4 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht Memory: 4k page, physical 8118936k(50388k free), swap 5242872k(5179744k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (14.3-b01) for linux-amd64 JRE (1.6.0_17-b04), built on Oct 11 2009 01:08:48 by java_re with gcc 3.2.2 (SuSE Linux) time: Sat Jan 9 18:54:46 2010 elapsed time: 536 seconds cheers, Steve On 11/01/2010, at 11:54 PM, Martin Makundi wrote: Hi! Did you try newer jvm build? ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: 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=0x2b5fa7fb, 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: [0x488b2000,0x489b3000], sp=0x489af470, 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-2aac13c9 r-xs 4000 fd:01 1204722 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-ioc-1.3.0.jar 2aac13c9-2aac13c92000 r-xs 3000 fd:01 1204729 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-spring-1.3.0.jar 2aac13c92000-2aac13c93000 r-xs 3000 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: JVM crash, Wicket class mentioned
There is an early access version of update 18: https://jdk6.dev.java.net/6uNea.html cheers, Witold Am Wed, 13 Jan 2010 09:52:01 +1100 schrieb Steve Swinsburg steve.swinsb...@gmail.com: For the rare JVM crash in the past this is what I've done also, however _17 is the latest so there is no upgrade. Still, we would really like to know what caused this. A Wicket class is referenced in the error. thanks, Steve On 12/01/2010, at 12:07 AM, Martin Makundi wrote: Hi! No, I remember having similar problems before and they were fixed by upgarding jvm (1.6.0_17 - 1.6.0_18 for example). ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: Hi Martin, I'll pass that on, but the JRE version is 1.6.0_17-b04 unless you mean the 14.3-b01 VM version? Heres the system info from the log: OS:SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 2 uname:Linux 2.6.16.60-0.42.5-smp #1 SMP Mon Aug 24 09:41:41 UTC 2009 x86_64 libc:glibc 2.4 NPTL 2.4 rlimit: STACK 8192k, CORE 0k, NPROC 69119, NOFILE 10, AS infinity load average:0.32 1.14 0.74 CPU:total 4 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht Memory: 4k page, physical 8118936k(50388k free), swap 5242872k(5179744k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (14.3-b01) for linux-amd64 JRE (1.6.0_17-b04), built on Oct 11 2009 01:08:48 by java_re with gcc 3.2.2 (SuSE Linux) time: Sat Jan 9 18:54:46 2010 elapsed time: 536 seconds cheers, Steve On 11/01/2010, at 11:54 PM, Martin Makundi wrote: Hi! Did you try newer jvm build? ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: 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=0x2b5fa7fb, 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: [0x488b2000,0x489b3000], sp=0x489af470, 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-2aac13c9 r-xs 4000 fd:01 1204722 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-ioc-1.3.0.jar 2aac13c9-2aac13c92000 r-xs 3000 fd:01 1204729 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-spring-1.3.0.jar 2aac13c92000-2aac13c93000 r-xs 3000 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: JVM crash, Wicket class mentioned
Hi! Did you try newer jvm build? ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: 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=0x2b5fa7fb, 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: [0x488b2000,0x489b3000], sp=0x489af470, 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-2aac13c9 r-xs 4000 fd:01 1204722 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-ioc-1.3.0.jar 2aac13c9-2aac13c92000 r-xs 3000 fd:01 1204729 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-spring-1.3.0.jar 2aac13c92000-2aac13c93000 r-xs 3000 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: JVM crash, Wicket class mentioned
Hi Martin, I'll pass that on, but the JRE version is 1.6.0_17-b04 unless you mean the 14.3-b01 VM version? Heres the system info from the log: OS:SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 2 uname:Linux 2.6.16.60-0.42.5-smp #1 SMP Mon Aug 24 09:41:41 UTC 2009 x86_64 libc:glibc 2.4 NPTL 2.4 rlimit: STACK 8192k, CORE 0k, NPROC 69119, NOFILE 10, AS infinity load average:0.32 1.14 0.74 CPU:total 4 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht Memory: 4k page, physical 8118936k(50388k free), swap 5242872k(5179744k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (14.3-b01) for linux-amd64 JRE (1.6.0_17-b04), built on Oct 11 2009 01:08:48 by java_re with gcc 3.2.2 (SuSE Linux) time: Sat Jan 9 18:54:46 2010 elapsed time: 536 seconds cheers, Steve On 11/01/2010, at 11:54 PM, Martin Makundi wrote: Hi! Did you try newer jvm build? ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: 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=0x2b5fa7fb, 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: [0x488b2000,0x489b3000], sp=0x489af470, 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-2aac13c9 r-xs 4000 fd:01 1204722 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-ioc-1.3.0.jar 2aac13c9-2aac13c92000 r-xs 3000 fd:01 1204729 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-spring-1.3.0.jar 2aac13c92000-2aac13c93000 r-xs 3000 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org smime.p7s Description: S/MIME cryptographic signature
Re: JVM crash, Wicket class mentioned
Hi! No, I remember having similar problems before and they were fixed by upgarding jvm (1.6.0_17 - 1.6.0_18 for example). ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: Hi Martin, I'll pass that on, but the JRE version is 1.6.0_17-b04 unless you mean the 14.3-b01 VM version? Heres the system info from the log: OS:SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 2 uname:Linux 2.6.16.60-0.42.5-smp #1 SMP Mon Aug 24 09:41:41 UTC 2009 x86_64 libc:glibc 2.4 NPTL 2.4 rlimit: STACK 8192k, CORE 0k, NPROC 69119, NOFILE 10, AS infinity load average:0.32 1.14 0.74 CPU:total 4 (1 cores per cpu, 2 threads per core) family 15 model 4 stepping 1, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ht Memory: 4k page, physical 8118936k(50388k free), swap 5242872k(5179744k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (14.3-b01) for linux-amd64 JRE (1.6.0_17-b04), built on Oct 11 2009 01:08:48 by java_re with gcc 3.2.2 (SuSE Linux) time: Sat Jan 9 18:54:46 2010 elapsed time: 536 seconds cheers, Steve On 11/01/2010, at 11:54 PM, Martin Makundi wrote: Hi! Did you try newer jvm build? ** Martin 2010/1/11 Steve Swinsburg steve.swinsb...@gmail.com: 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=0x2b5fa7fb, 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: [0x488b2000,0x489b3000], sp=0x489af470, 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-2aac13c9 r-xs 4000 fd:01 1204722 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-ioc-1.3.0.jar 2aac13c9-2aac13c92000 r-xs 3000 fd:01 1204729 /usr/local/xxx/webapps/the-app/WEB-INF/lib/wicket-spring-1.3.0.jar 2aac13c92000-2aac13c93000 r-xs 3000 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: JVM crash, Wicket class mentioned
Op maandag 11-01-2010 om 15:07 uur [tijdzone +0200], schreef Martin Makundi: Hi! No, I remember having similar problems before and they were fixed by upgarding jvm (1.6.0_17 - 1.6.0_18 for example). For what it's worth, I've had better luck with the OpenJDK on 64-bit Linux than with the Sun 64-bit JDK. It might have been fixed in the mean time but when I tried it I suffered from random JVM crashes. regards, -- Reinout van Schouwen - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
