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).
>
--
View this message in context:
http://www.nabble.com
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:
fxsr, mmx, sse, sse2, sse3, ssse3
Memory: 4k page, physical 67107112k(18792216k free), swap
69649820k(14739920k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (10.0-b23) for windows-amd64 JRE
(1.6.0_07-b06), built on Jun 10 2008 01:06:11 by "java_re" with MS VC++ 8.0
time: Thu Mar 19 18:00:49 2009
elapsed time: 94857 seconds
--
View this message in context:
http://www.nabble.com/JVM-exception_access_violation-tp22623667p22623667.html
Sent from the Solr - User mailing list archive at Nabble.com.
