You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2007/03/27 01:04:32 UTC
[jira] Created: (WICKET-424) Can't run examples as a WAR with Jetty
6.1.1
Can't run examples as a WAR with Jetty 6.1.1
--------------------------------------------
Key: WICKET-424
URL: https://issues.apache.org/jira/browse/WICKET-424
Project: Wicket
Issue Type: Bug
Components: wicket-examples
Affects Versions: 1.3
Reporter: Jean-Baptiste Quenot
{noformat}
java.lang.LinkageError: Class javax/management/MBeanServer violates loader constraints
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:354)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:325)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at wicket.jmx.Initializer.init(Initializer.java:152)
at wicket.Application.callInitializers(Application.java:781)
at wicket.Application.initializeComponents(Application.java:665)
at wicket.protocol.http.WicketFilter.init(WicketFilter.java:398)
...
{noformat}
If I unpack the war and remove
wicket-examples/WEB-INF/lib/mx4j-3.0.1.jar the application
launches alright.
This error happens because Jetty already provides:
* jetty/lib/management/mx4j-3.0.1.jar
* jetty/lib/management/mx4j-tools-3.0.1.jar
So we should maybe avoid to package those jars in WEB-INF/lib when building the wicket-examples WAR
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-424) Can't run examples as a WAR with
Jetty 6.1.1
Posted by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Quenot resolved WICKET-424.
-----------------------------------------
Resolution: Fixed
Assignee: (was: Jean-Baptiste Quenot)
Dependencies changed by Martijn, and verified by AlMaw and me.
> Can't run examples as a WAR with Jetty 6.1.1
> --------------------------------------------
>
> Key: WICKET-424
> URL: https://issues.apache.org/jira/browse/WICKET-424
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Jean-Baptiste Quenot
> Priority: Critical
>
> {noformat}
> java.lang.LinkageError: Class javax/management/MBeanServer violates loader constraints
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:354)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:325)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at wicket.jmx.Initializer.init(Initializer.java:152)
> at wicket.Application.callInitializers(Application.java:781)
> at wicket.Application.initializeComponents(Application.java:665)
> at wicket.protocol.http.WicketFilter.init(WicketFilter.java:398)
> ...
> {noformat}
> If I unpack the war and remove
> wicket-examples/WEB-INF/lib/mx4j-3.0.1.jar the application
> launches alright.
> This error happens because Jetty already provides:
> * jetty/lib/management/mx4j-3.0.1.jar
> * jetty/lib/management/mx4j-tools-3.0.1.jar
> So we should maybe avoid to package those jars in WEB-INF/lib when building the wicket-examples WAR
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-424) Can't run examples as a WAR with Jetty
6.1.1
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw updated WICKET-424:
--------------------------------
Assignee: Jean-Baptiste Quenot
Yeah, they need specifying in the dependencies with a <scope>provided</scope>. Can you try that and commit if it works?
> Can't run examples as a WAR with Jetty 6.1.1
> --------------------------------------------
>
> Key: WICKET-424
> URL: https://issues.apache.org/jira/browse/WICKET-424
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Jean-Baptiste Quenot
> Assigned To: Jean-Baptiste Quenot
> Priority: Critical
>
> {noformat}
> java.lang.LinkageError: Class javax/management/MBeanServer violates loader constraints
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:354)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:325)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at wicket.jmx.Initializer.init(Initializer.java:152)
> at wicket.Application.callInitializers(Application.java:781)
> at wicket.Application.initializeComponents(Application.java:665)
> at wicket.protocol.http.WicketFilter.init(WicketFilter.java:398)
> ...
> {noformat}
> If I unpack the war and remove
> wicket-examples/WEB-INF/lib/mx4j-3.0.1.jar the application
> launches alright.
> This error happens because Jetty already provides:
> * jetty/lib/management/mx4j-3.0.1.jar
> * jetty/lib/management/mx4j-tools-3.0.1.jar
> So we should maybe avoid to package those jars in WEB-INF/lib when building the wicket-examples WAR
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-424) Can't run examples as a WAR with Jetty
6.1.1
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw updated WICKET-424:
--------------------------------
Apologies if you think me assigning you things is unreasonable, but I assigned this to you because you obviously have an environment set up to recreate the bug otherwise you wouldn't have seen it in the first place.
The suggested fix will therefore take you about one minute to implement and test. Given you're a core committer and obviously care enough about this to file the issue in the first place, I therefore felt assumed you could spend three minutes on this. If you'd just done that rather than bitch in JIRA at me, it would have been closed by now. ;-) Obviously if the suggested fix doesn't work, feel free to unassign it.
> Can't run examples as a WAR with Jetty 6.1.1
> --------------------------------------------
>
> Key: WICKET-424
> URL: https://issues.apache.org/jira/browse/WICKET-424
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Jean-Baptiste Quenot
> Assigned To: Jean-Baptiste Quenot
> Priority: Critical
>
> {noformat}
> java.lang.LinkageError: Class javax/management/MBeanServer violates loader constraints
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:354)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:325)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at wicket.jmx.Initializer.init(Initializer.java:152)
> at wicket.Application.callInitializers(Application.java:781)
> at wicket.Application.initializeComponents(Application.java:665)
> at wicket.protocol.http.WicketFilter.init(WicketFilter.java:398)
> ...
> {noformat}
> If I unpack the war and remove
> wicket-examples/WEB-INF/lib/mx4j-3.0.1.jar the application
> launches alright.
> This error happens because Jetty already provides:
> * jetty/lib/management/mx4j-3.0.1.jar
> * jetty/lib/management/mx4j-tools-3.0.1.jar
> So we should maybe avoid to package those jars in WEB-INF/lib when building the wicket-examples WAR
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-424) Can't run examples as a WAR with Jetty
6.1.1
Posted by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Quenot updated WICKET-424:
----------------------------------------
Priority: Critical (was: Major)
> Can't run examples as a WAR with Jetty 6.1.1
> --------------------------------------------
>
> Key: WICKET-424
> URL: https://issues.apache.org/jira/browse/WICKET-424
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.3
> Reporter: Jean-Baptiste Quenot
> Priority: Critical
>
> {noformat}
> java.lang.LinkageError: Class javax/management/MBeanServer violates loader constraints
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:354)
> at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:325)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
> at wicket.jmx.Initializer.init(Initializer.java:152)
> at wicket.Application.callInitializers(Application.java:781)
> at wicket.Application.initializeComponents(Application.java:665)
> at wicket.protocol.http.WicketFilter.init(WicketFilter.java:398)
> ...
> {noformat}
> If I unpack the war and remove
> wicket-examples/WEB-INF/lib/mx4j-3.0.1.jar the application
> launches alright.
> This error happens because Jetty already provides:
> * jetty/lib/management/mx4j-3.0.1.jar
> * jetty/lib/management/mx4j-tools-3.0.1.jar
> So we should maybe avoid to package those jars in WEB-INF/lib when building the wicket-examples WAR
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.