CODEWITHSUNDEEP
javadeploymentweblogicearweblogic12c
schibbl
schibbl

Reputation: 106

NullPointerException at deployment of EAR at Weblogic 12c

We move our Application from Weblogic 9.2 to Weblogic 12.1.2. Deploying the EAR using Admin Console fails due to an not documented NullPointerException. After searching a lot for this stacktrace and Error message, we found very little. One OTN Thread with similar topic pointed to the doubling of JARs within Weblogic Classpath and EAR. So we searched for JAR doubling in Weblogic Installation and EAR. The EAR has packed xml-apis-1.3.02.jar and WL Classpath includes xml-apis.jar. After removing xml-apis-1.3.02.jar from EAR and a new deployment, we faced the same NullPointerException again.

The stacktrace of the Exception

Ingredients of the EAR:

Thats what comes with Weblogic:

Upvotes: 0

Views: 3654

Answers (2)

cpurdy
cpurdy

Reputation: 1236

I'll log a bug on this to make sure it's looked at. You should never get an NPE.

Upvotes: 1

Display Name is missing
Display Name is missing

Reputation: 6227

First, I do not believe the exception you have pasted is the "real" error but is rather a symptom of another error. It is failing to activate the change, i.e. install your .ear file. That exception is not helpful. If I had to guess there is another error somewhere in the logs. Generally duped jars on the classpath will cause a NoClassDefFoundError or a ClassNotFoundException. Check for those.

Second, if you are having classes conflict between your deployments and the default weblogic classpath, you can try adding this to your weblogic.xml to force it to use the libraries in your ear:

<wls:prefer-application-packages>
    <wls:package-name>package.that.conflicts.*</wls:package-name>
</wls:prefer-application-packages>

Upvotes: 1

Related Questions