WebCenter Application Fails to Load After Upgrading to 12.2.1.3 : Failed to initialize the application "webcenter" due to error weblogic.application.ModuleException: java.lang.ClassNotFoundException: com.wordnik.swagger.jersey.config.JerseyJaxrsConfig
(Doc ID 2573076.1)
Last updated on AUGUST 14, 2023
Applies to:
Oracle WebCenter Portal - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
The WebCenter application fails to load after upgrading from 12.2.1.0 to 12.2.1.3.
The JVM's startst fine, but the webcenter application fails to load.
ERROR
The WC_Portal.out file shows the following errors:
<Date> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application /<DOMAIN_HOME>/servers/WC_Portal/tmp/_WL_user/webcenter/7crphl/webcenter-rest.war. Ensure that the annotations are valid. The error is com.wordnik.swagger.jersey.config.JerseyJaxrsConfig>
<Date> <Error> <Deployer> <BEA-149205> <Failed to initialize the application "webcenter" due to error weblogic.application.ModuleException: java.lang.ClassNotFoundException: com.wordnik.swagger.jersey.config.JerseyJaxrsConfig
weblogic.application.ModuleException: java.lang.ClassNotFoundException: com.wordnik.swagger.jersey.config.JerseyJaxrsConfig
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:192)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:187)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: com.wordnik.swagger.jersey.config.JerseyJaxrsConfig
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:1029)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:990)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:101)
at weblogic.utils.classloaders.GenericClassLoader.doFindClass(GenericClassLoader.java:611)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:543)
Truncated. see log file for complete stacktrace
>
...
<Date> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application "webcenter".
weblogic.application.ModuleException: Module null can not be activated, not in ACTIVATED state: NEW
at weblogic.diagnostics.module.WLDFModule.activate(WLDFModule.java:328)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:212)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:207)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:57)
Truncated. see log file for complete stacktrace
>
<Date> <Warning> <oracle.adf.share.config.ADFConfigFactory> <BEA-000000> <Resource META-INF/adf-config.xml not found on the classpath.>
<Date> <Warning> <oracle.adf.share.config.ADFConfigFactory> <BEA-000000> <A default implementation of ADFConfig is being created for application. This can lead to unexpected results in some cases. Please add a basic META-INF/adf-config.xml to your classpath to avoid functional errors.>
STEPS
The issue can be reproduced at will with the following steps:
- Start the portal managed server.
Here you will see the errors in the log. - Access the webcenter portal URL .
Here you will get a 404 error.
Changes
WebCenter Portal was upgraded from 12.2.1.0 to 12.2.1.3.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |