WebLogic Console Access Fails with Error 503-Service Unavailable

Error:

In the FMW environment, when trying to access Weblogic console, it fails with the error "Error 503-Service Unavailable".

Admin Server is up and running and Fusion Middleware Control is accessible.

The log file shows below errors:

<Error> <HTTP> <BEA-101216> <Servlet: "action" failed to preload on startup in Web application: "console".

<ECID> <TID> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101064> <[WebAppModule(consoleapp:console)]

Error parsing descriptor in Web appplication "/wlserver/server/lib/consoleapp/webapp"

javax.xml.stream.XMLStreamException: Error at line:438 col:6 ' ' expect a valid beginning name character

at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:361)

at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:429)

at javax.xml.stream.util.StreamReaderDelegate.next(StreamReaderDelegate.java:88)

at weblogic.application.descriptor.DebugStreamReaderDelegate.next(DebugStreamReaderDelegate.java:88)

at weblogic.application.descriptor.BasicMunger2.next(BasicMunger2.java:427)

at weblogic.application.descriptor.VersionMunger._next(VersionMunger.java:346)

at weblogic.application.descriptor.VersionMunger.next(VersionMunger.java:231)

Solution:

The problem is caused due to corruption of console application which is present under ORACLE_HOME/wlserver/server/lib/consoleapp directory

Please execute the following to fix the issue

1. Stop AdminServer, Nodemanager and all managed servers.

2. Take a backup of consoleapp directory under ORACLE_HOME/wlserver/server/lib

3. Restore consoleapp directory from backup or any other similar working environment

4. Backup and delete the cache and tmp folder from the Domain_Home/server/AdminServer/

5. Restart the AdminServer and access the console.

If you like please follow and comment