Markus,
Check the jar as suggested by Tim; it does not harm and should not take
long. Secondly, modify JVM settings in domain.xml and start JVM with
verbose option. See [1] for available JVM options. The ones that you can
try with are -verbose and -XX:-TraceClassLoading.
Thanks,
Sahoo
[1]
http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp
glassfish_at_javadesktop.org wrote:
> Hi, Markus.
>
> I didn't claim to know for sure that GlassFish being unable to load that class is the problem, although it seems likely to me given the brief output. I also didn't suggest that the class was removed from the JAR. I was just providing a little more information that seems relevant: based on what you wrote earlier I think GlassFish cannot find that class.
>
> There are several ways I can imagine this could have happened - for example, if the JAR file could have been moved. If the virus scanner installation is the only change from when GlassFish used to start up normally then perhaps check the virus scanner's log to see if it might have done something. I have not heard of virus scanners doing anything to the jce.jar file but who knows?
>
> Until you discover what caused the difference in behavior nothing can be ruled out.
>
> - Tim
> [Message sent by forum member 'tjquinn' (tjquinn)]
>
> http://forums.java.net/jive/thread.jspa?messageID=344862
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>