NoClassDefFoundError on weblogic 10.3 managed server

[Tony Yan]

Hi, All:

I have had this problem for three days or more, a major block in my app. I have an ear file with three war files. Two are webservices modules, and one regular web app module. The ear file works fine on weblogic Admin Server, both on Windows and Solaris. But, when I deploy it (the same ear) to a managed server or a single managed server in a cluster, it has following NoClassDefFoundError. Stacktrace shown here. We have a Duration type in our XSD, that's why we need this DurationImpl. Searching thru the net, it seems that the managed server and adminserver of Weblogic 10 are a bit different in terms of classpath. I have tried many options in weblogic.xml weblogic-application.xml etc. No luck. I feel the best method to solve this is first to find out what's the difference between managed and the admin server. Of course, any work around is certainly good.

Thanks.

-Tony

java.lang.NoClassDefFoundError: Could not initialize class org.apache.xerces.jaxp.datatype.DurationImpl
	at org.apache.xerces.jaxp.datatype.DatatypeFactoryImpl.newDuration(Unknown Source)
	at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$25.parse(RuntimeBuiltinLeafInfoImpl.java:787)
	at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl$25.parse(RuntimeBuiltinLeafInfoImpl.java:780)
	at com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.parse(TransducedAccessor.java:241)
	at com.sun.xml.bind.v2.runtime.unmarshaller.LeafPropertyLoader.text(LeafPropertyLoader.java:61)
	at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.text(UnmarshallingContext.java:462)
	at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.processText(SAXConnector.java:168)
	at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.endElement(SAXConnector.java:141)
	at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
	at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
	at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:211)
	at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:184)
	at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
	at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:194)

[Tony Yan]

Pretty much found this problem, semi-incidentally. We have Wily monitoring system on the server, it must have an older version of xerces in its classpath that doesn't have a util class in xerces that only exists after 2.8. We deployed to another managed server w/o Wily. Problem went away. End of 4 days of stupid tail spin.

<T/>