War Deployment Failed After Restore With java.lang.ClassNotFoundException: org.apache.log4j.Priority (Doc ID 3027827.1)

Last updated on JUNE 17, 2024

Applies to:

Symptoms

When attempting to deploy war file in Weblogic after restore from backup, the following error occurs.


Error:

Weblogic AdminServer.log

####<31 May, 2024 11:52:15,166 AM IST> <Warning> <Deployer> <NAME> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'>
<> <> <39627c8f-7b07-4ade-89e9-d17508416a45-000000e8> <1717136535166> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
<BEA-149078> <Stack trace for message 149004 weblogic.application.ModuleException: java.lang.ClassNotFoundException: org.apache.log4j.Priority
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)

OFSAA_Server-IN.out - weblogic

<31 May, 2024 11:56:43,695 PM IST> <Warning> <WorkManager> <BEA-002919> <Unable to find a Work Manager with name wm/WorkManager. Dispatch policy wm/WorkManager will map to the default Work Manager for the application OFSAA>
May 31, 2024 11:56:45 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener parseAdaptersAndCreateDelegate
SEVERE: WSSERVLET11: failed to parse runtime descriptor: java.lang.NoClassDefFoundError: org/apache/log4j/Priority
java.lang.NoClassDefFoundError: org/apache/log4j/Priority
at java.lang.Class.forName0(Native Method)

Steps:

1. Upgraded to ALM 8.0.7.8
2. Upgraded to PFT 8.0.7.8.
3. Restore files and database to ALM 8.0.7.8.
4. Regenerate war file and deploy war file with errors above.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.