Problem about java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class

Problem about java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class

[Problem Description]
http://forum.springframework.org/showthread.php?t=54451

< 19 - may - 2008  09H05 '  CEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application  ' mobile - marketing ' .

weblogic.application.ModuleException:

at weblogic.servlet.internal.WebAppModule.startContex ts(WebAppModule.java: 950 )
at weblogic.servlet.internal.WebAppModule.start(WebAp pModule.java: 353 )
at weblogic.application.internal.flow.ModuleStateDriv er$ 3 .next(ModuleStateDriver.java: 204 )
at weblogic.application.utils.StateMachineDriver.next State(StateMachineDriver.java: 26 )
at weblogic.application.internal.flow.ModuleStateDriv er.start(ModuleStateDriver.java: 60 )

Truncated. see log file  for  complete stacktrace

java.lang.LinkageError: loader constraints violated when linking javax / xml / namespace / QName  class

at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafI nfoImpl. < clinit > (RuntimeBuiltinLeafInfoImpl.java: 186 )

at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetI mpl. < init > (RuntimeTypeInfoSetImpl.java: 25 )

at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder .createTypeInfoSet(RuntimeModelBuilder.java: 84 )

at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder .createTypeInfoSet(RuntimeModelBuilder.java: 41 )

at com.sun.xml.bind.v2.model.impl.ModelBuilder. < init >  (ModelBuilder.java: 104 )

Truncated. see log file  for  complete stacktrace

[Suggestion by David.Turing]
When the same class is loaded from two different classloader(weblogic system classloader and application classloader), we will encountering this problem.
I am sure that weblogic use javax/xml/namespace/QName class and your version could be different at the build time.

I found that javax.xml.namespace.QName locate in 3 jar in WebLogic 10:

 

 

So could you please replace the your original jar that contains the javax.xml.namespace.QName with  D:\bea100\wlserver_10.0\server\lib\api.jar

and then rebuild your application.

 

Then try to redeploy again.