I assume that you're not using any Tomcat native libs? If you are,
try removing them... if not (and the crash happened more than once in
the same place) then it looks like a JVM bug rather than flakey
hardware and the easiest path forward would be to try the latest Java6
(update 12).
-Yonik
http://www.lucidimagination.com
On Fri, Mar 20, 2009 at 12:42 PM, wojtekpia wrote:
>
> I'm running Solr on Tomcat 6.0.18 with Java 6 update 7 on Windows 2003 64
> bit. Over the past month or so, my JVM has crashed twice with the error
> below. Has anyone experienced this? My system is not heavily loaded, and the
> crash seems to coincide with an update (via DIH). I'm running trunk code
> from late January. Note that I update my index ~50 times per day, and this
> crash has happened twice in the past month (so 2 of 1500 updates seem to
> have triggered the crash).
>
> This Windows deployment is for demos, so I'm not too concerned about it.
> Interestingly, my production deployment is on a 64 bit Linux system (same
> versions of everything) and I haven't been able to reproduce the bug there.
>
> #
> # An unexpected error has been detected by Java Runtime Environment:
> #
> # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x080e51c3,
> pid=4404, tid=956
> #
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b23 mixed mode
> windows-amd64)
> # Problematic frame:
> # V [jvm.dll+0xe51c3]
> #
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> #
>
> --- T H R E A D ---
>
> Current thread (0x01de2000): GCTaskThread [stack:
> 0x,0x] [id=956]
>
> siginfo: ExceptionCode=0xc005, reading address 0x
>
> Registers:
> EAX=0x3000, EBX=0x01e40330, ECX=0x000184b49821,
> EDX=0x000184b4b580
> ESP=0x07cff9b0, EBP=0x, ESI=0x000184b4b580,
> EDI=0x0935
> EIP=0x080e51c3, EFLAGS=0x00010206
>
> Top of Stack: (sp=0x07cff9b0)
> 0x07cff9b0: 01e40330
> 0x07cff9c0: 000184b4dd88 0935
> 0x07cff9d0: 08464b08 01dbbdc0
> 0x07cff9e0: 01dbf190 8a65
> 0x07cff9f0: 2f5b4000 0002015f
> 0x07cffa00: 0002 01dbf2f0
> 0x07cffa10: 01e40330 01dbf430
> 0x07cffa20: 01dbf4f0 000201602d18
> 0x07cffa30: 07effa00 07cffb40
> 0x07cffa40:
> 0x07cffa50: 0830484d
> 0x07cffa60: 0002015f 0002
> 0x07cffa70: 0048 0001
> 0x07cffa80: 0001 00bb8501
> 0x07cffa90: 01dbf378 080ea807
> 0x07cffaa0: 07cffb40 07cffb40
>
> Instructions: (pc=0x080e51c3)
> 0x080e51b3: 4c 8d 44 24 20 48 8b d6 48 8b 41 10 48 83 c1 10
> 0x080e51c3: ff 90 c0 01 00 00 44 8b 1d 08 f2 44 00 45 85 db
>
>
> Stack: [0x,0x], sp=0x07cff9b0,
> free space=127998k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> V [jvm.dll+0xe51c3]
>
> [error occurred during error reporting (printing native stack), id
> 0xc005]
>
>
> --- P R O C E S S ---
>
> Java Threads: ( => current thread )
> 0x10286c00 JavaThread "Thread-135" daemon [_thread_blocked,
> id=4892, stack(0x1169,0x1179)]
> 0x10285400 JavaThread "http-8084-10" daemon [_thread_blocked,
> id=5108, stack(0x1201,0x1211)]
> 0x10287400 JavaThread "http-8084-9" daemon [_thread_blocked,
> id=1772, stack(0x149a,0x14aa)]
> 0x1028a400 JavaThread "http-8084-8" daemon [_thread_blocked,
> id=1656, stack(0x11f1,0x1201)]
> 0x01dc2c00 JavaThread "http-8084-7" daemon [_thread_blocked,
> id=2056, stack(0x11e1,0x11f1)]
> 0x10288400 JavaThread "http-8084-6" daemon [_thread_blocked,
> id=4792, stack(0x11d1,0x11e1)]
> 0x10286800 JavaThread "MultiThreadedHttpConnectionManager cleanup"
> daemon [_thread_blocked, id=3792,
> stack(0x1251,0x1261)]
> 0x0f6e8400 JavaThread "http-8084-5" daemon [_thread_blocked,
> id=3540, stack(0x11c1,0x11d1)]
> 0x0f6e7800 JavaThread "http-8084-4" daemon [_thread_blocked,
> id=4048, stack(0x11b1,0x11c1)]
> 0x0f6e8000 JavaThread "http-8084-3" daemon [_thread_blocked,
> id=1932, stack(0x1159,0x1169)]
> 0x0f6e7000 JavaThread "http-8084-2" daemon [_thread_blocked,
> id=996, stack(0x114900
