The only hint I can find is the fact that it happens during
applicationinitialization. I can see
"You are in DEVELOPMENT mode"
and the init method of the WebApplication class terminates correctly. The the
exception is thrown. It only happens when I re-deploy the application. The
error message is
12:29:29,375 INFO [WebappClassLoader] Illegal access: this web application inst
ance has been stopped already. Could not load
org.jboss.mx.util.JMXExceptionDecoder. The eventual following stack trace is
caused by an error thrown for debug
ging purposes as well as to attempt to terminate the thread which caused the
illegal access, and has no functional impact.
java.lang.IllegalStateException
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1238)
at
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at
org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1436)
at
org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376)
at wicket.jmx.Initializer.init(Initializer.java:66)
at wicket.Initializer.init(Initializer.java:51)
I can't figure out why JBoss?/Tomcat?/Wicket? can't load the
org.jboss.mx.util.JMXExceptionDecoder class. I resides in the jmx-client.jar
archive wich is part of my application's WEB-INF\lib folder.
Stefan.
________________________________
Von: Eelco Hillenius [mailto:[EMAIL PROTECTED]
Gesendet: Mo 16.10.2006 11:25
An: [email protected]
Betreff: Re: DEPRECATED! Please use WicketFilter instead
Stefan, you could comment
// register JMX beans
new wicket.jmx.Initializer().init(application);
in wicket.Initializer if this is giving you too much trouble. Though
we'd have to fix this sooner or later, so if you can find out why this
is a problem for JBoss/ Tomcat...
Eelco
