I'll try cross-posting this on over to the jdk6.dev.java.net list, thanks.
We tried running glassfish with -server but it was mid-day on our live
server and after it wasn't up after 5 minutes we needed to switch back to
-client.
sdo wrote:
>
> To me, it looks like bug id 6506476 for the JVM (which you can see at
> bugs.sun.com). Perhaps someone on the dev_at_jdk6.dev.java.net alias could
> give more information about that.
>
> One thing I notice about that bug and its related bug is that they've
> been filed only against the client compiler (and are related to the
> compiled code) -- have you tried running glassfish with the -server
> compiler?
>
> -Scott
>
> On Tue, 2007-04-24 at 11:04, glassfish_at_javadesktop.org wrote:
>> The JVM went down once again this morning with the following hs_err_pid
>> file resulting:
>>
>> #
>> # An unexpected error has been detected by Java Runtime Environment:
>> #
>> # Internal Error (4E4D4554484F440E435050071F), pid=22601, tid=1175010224
>> #
>> # Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode)
>> # If you would like to submit a bug report, please visit:
>> # http://java.sun.com/webapps/bugreport/crash.jsp
>> #
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>
--
View this message in context: http://www.nabble.com/java-process-ending-tf3631940.html#a10164291
Sent from the java.net - glassfish users mailing list archive at Nabble.com.