jetty fails to launch with a linkage error about run-jetty-run HOT 23 CLOSED

Thanks for the report.

Could you make my life easier by attaching a zip or tar file?  Thanks.

attachment as a zip

Thanks

Disregard this bug.  Apparently using the MX4J library (not the MX4J-Tools 
library)
in Java 5 is the cause of this.  MX4J is an implementation of JMX and is 
suitable for
adding JMX to JDK 1.4 and earlier, but is not needed on JDK 5 and its inclusion 
can
cause problems like this.  Removing this library specifically removes the error 
and
allows full functionality.  I still am not quite sure why this broke between 
1.1.0
and 1.0.1, but I suspect its some obscure class loading order issue that isn't 
really
a defect.

Thanks for the update.

I opened another issue, because i didnt search in all status. 

I am not using mx4j library in the app but having the same problem. The project 
is
run with java-6. I attached the full stack in issue 28.

OK, I'm re-opening this bug.  I have some guesses as to the cause, and will 
investigate.

Pheotmail, can you detail the full list of dependencies in your classpath?  
From what
I've read this problem can also be caused by ANY other JMX implementations in 
the
classpath.  

@9 the dependencies can be seen in the attachement of issue 28. there is a 
bunch of
dependencies especially from spring, hibernate and cxf-webservice. i dont know 
if
there is a jmx implementation included.

Phoetmail, is there an option on the version of java you're using to dump out 
the 
class loading events (java -verbose:class is available from the Sun and IBM 
JREs)?  
If so, this might add some useful info about the LinkageError.

FYI, Jetty defaults to overriding the normal J2SE class loader delegation model 
(which calls for delegating to the parent).  You might try setting:

   -Dorg.mortbay.jetty.webapp.parentLoaderPriority=true

in the VM args, and report back how that impacted things.

I will try the system-property and report back. But i think that it will not be
before next week.

Jetty 6.1.6 defines the following prefixes for system classes (classes that a 
web app can't 
override/replace):

    java.
    javax.servlet.
    javax.xml.
    org.mortbay.
    org.xml.
    org.w3c.
    org.apache.commons.logging.
    org.apache.log4j.

Notice this doesn't include javax.management.
My inclination is to guess this is the source of the problem reported here.

Fortunately, this is a settable value (in code).  So, if we can determine that 
this is the problem, it'll 
be pretty easy to add it to the list.  Alternately, I could add javax. as a 
system classes prefix.

Response to Comment 12: 

   -Dorg.mortbay.jetty.webapp.parentLoaderPriority=true

It works! With this VM arg jetty runs again.
Thanks.

@15 Stefan, what class was failing to load for you?

Please fix this bug on 6.1 and 7 plugins, this is really blocking as soon as we 
use
java6 !!!

Issue 28 has been merged into this issue.

   -Dorg.mortbay.jetty.webapp.parentLoaderPriority=true
Also worked for me. 

Thanks :)

Issue 34 has been merged into this issue.

Plan to make it more clear in 1.2 

Ready since 2011/3/16 , committed in r88 .

I add a option and provide a help link for this config in RJR Run Configuration.
will in version 1.2.1 

-Dorg.mortbay.jetty.webapp.parentLoaderPriority=true

worked for me.

Big thanks