“loader constraints violated when linking javax/xml/namespace/QName class” from webapp on Oracle 10g

点点圈 提交于 2019-12-05 08:45:21

This class is in half the WS Java libraries out there. It's really easy to load it from multiple classloaders and later compare them, causing a LinkageError.

One effective (but sledgehammer) technique to tracking this down is to modify Classloader from the Java source to dump which jar this particular class is loading from at load time, then prepend your bootclasspath with your modified version:

-Xbootclasspath/p:/path/to/hackedBin

What version of Java are you using? The newest versions ship with this class in the rt.jar.

May be it's completely unrelated, but I remember a problem Weblogic had with the very same class. The reason for the problem was the changed serial id of the class (Sun changed it accidentally). The workaround was to provide a -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 to the JVM.

Could it be the same problem, just misreported? Try it.

See here: http://forums.bea.com/thread.jspa?threadID=600014563

Can you just update the JAXB jar under the app server's lib folder?

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!