Unable to access WebLogic Console: Error is "Unable to set the activation state to true for the application 'consoleapp'"

Unable to access WebLogic Console: Error is “Unable to set the activation state to true for the application ‘consoleapp'”

Hi All,

I’ve been working on WebLogic Server startup issue since 3 days and I am glad that issue is fixed. There is a WebLogic 10.3.2 environment where OIM 10g is installed. We’re able to start the OIM application through xlStartManagedServer.sh properly and able to access OIM admin console. However while starting up WebLogic Admin Server using xlStartWLS.sh, we are getting the below exception:

INFO: Completed initializing Sun’s JavaServer Faces implementation (1.2_03-b04-FCS) for context ‘/console’
<Jan 28, 2013 10:09:55 AM PST> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.NoClassDefFoundError: javax/xml/parsers/SAXParserFactory.
java.lang.NoClassDefFoundError: javax/xml/parsers/SAXParserFactory
at com.sun.faces.config.ConfigureListener$WebXmlProcessor.getConfiguredFactory(ConfigureListener.java:1987)
…………
…………
Caused By: java.lang.ClassNotFoundException: javax.xml.parsers.SAXParserFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
…………
…………
<Jan 28, 2013 10:09:55 AM PST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application ‘consoleapp’.
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1399)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
…………
…………
<Jan 30, 2013 10:59:00 PM PST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server “AdminServer” for domain “oim_domain” running in Production Mode>
<Jan 30, 2013 10:59:00 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jan 30, 2013 10:59:00 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

Since the server status is showing as RUNNING, I have tried accessing WebLogic Console http://host:port/console and it is throwing 404 Not Found error

There’re no any other clue in Admin Server logs which console is not accessible. So here is fix for the issue:

The weblogic-application.xml located under $WL_HOME/server/lib/consoleapp/META-INF has the package name <package-name>javax.xml.*</package-name> defined under the section <prefer-application-packages>

This package has been removed and bounced the server using xlStartWLS.sh and the server started without any exception and I am able to access the WebLogic console properly.

Learn Oracle Weblogic Server Administration

Get 100 USD OFF + 100% Money Back Guarantee

Click here to get Early Bird Discounts

About the Author Mahendra

I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com

Leave a Comment:

4 comments

kd_tcs_mumbai says February 18, 2013

Hi Mahendra,
I am curious to know
1)how this package playing role in WebLogic console.
2)When oracle has bundled this package with WL, shouldn’t we require it for any purpose.
3) How you came to know that this is creating problem.

Thanks,
KD

Mahendra says February 19, 2013

KD,

I am not a WebLogic expert, but as far as I know the weblogic console is itself an enterprise application deployed in weblogic app server.

Ideally we don’t modify the consoleapp application. However the error says the exception is due to SAXParserFactory. There were lot of trails made to fix this exception but atlast removing the sax class reference in weblogic-application.xml resolved the issue.

Thanks
Mahendra.

nares says August 27, 2013

when I’m deploying war file we are getting the issue any one please help me.

BG says July 30, 2014

I am running into similar issue when runnning Oracle Weblogic 10G

starting weblogic with Java version:
java version “1.6.0_05”
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Picked up _JAVA_OPTIONS: -Dsun.java2d.d3d=false
Starting WLS with line:
C:\Oracle\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=C:\Oracle\WLSERV~1.3 -Dwls.home=C:\Oracle\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\patch_wlw1030\profiles\default\sysext_manifest_classpath;C:\Oracle\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\Oracle\patch_cie660\profiles\default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server

Can someone please help?
Thank you

Add Your Reply