I am getting the following error while bringing up the JBOSS server. Can anyone help me locate what the exact issue is
loader constraint violation:
when resolving method "javax.xml.parsers.DocumentBuilder.setErrorHandler(Lorg/xml/sax/ErrorHandler;)V"
the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/log4j/xml/DOMConfigurator,
and the class loader (instance of <bootloader>) for resolved class, javax/xml/parsers/DocumentBuilder,
have different Class objects for the type org/xml/sax/ErrorHandler used in the signature
I don't see any issues which would let you think this is a problem with Log4J. But I guess that you have a version clash (means: the same JAR in different versions). Find out which JAR in your deployment contains the class "javax.xml.parsers.DocumentBuilder", check then if you have this JAR in two different versions in your setup (most IDEs provide you a dependency graph if you are using Maven) and throw one version out.
Joined: Dec 14, 2004
my JBoss 5.1 server uses the JRE 6 System library.
After digging through the JAR's i see that the DocumentBuilder is present in rt.jar.
I havent been able to find any JARS in the JBOSS that contain the same DocumentBuilder java file. Do you think i should try plugging out rt.jar from my JRE
Joachim, right you are! Apologies for the short replies at the moment, I'm having to use dictation software while I give my arms a rest for a few weeks.
Madhup, have you deployed any apps? Jboss 5.1 with JDK 1.6.0_23 should run just fine.
I'm also going to move this to the Jboss Forum.
Joined: Dec 14, 2004
Thanks for the reply guys!!!
Ok. here is the thing -
We are migrating one of our JSF applications from RAD-Iplanet-WAS to ECLIPSE-Apache-JBOSS combination.
Since our application was dependent on some of the WAS libraries we had to do some changes to the JAR's.
At present the application compiles and executes allright on the JBOSS server, but we are seeing the error mentioned above.
Hope you get the picture of the migration
Chances are that a JAR you have in your app is clashing with the JDK6 version of that class, it's usually a xerces or xalan JAR if I remember correctly. You'll want to make sure that your CLASSPATH isolation is working correctly and/or remove that clashing JAR