My Oracle Support Banner

Unable to Logic from OCA Client. Error:Failed to initialize session, reason: org.xml.sax.SAXParseException: Premature end of file (Doc ID 2793322.1)

Last updated on JULY 20, 2021

Applies to:

Oracle Communications ASAP - Version 7.2.0 to 7.2.0 [Release 7.2]
Information in this document applies to any platform.

Symptoms

While login from OCA Windows Client (type the user and password ) the GUI was not open and send the following error:

"Failed to initialize session, reason: org.xml.sax.SAXParseException: Premature end of file
Please ensure that the ASAP Daemon is running and try again"

ASAP daemon was up and running.

Log level entry for 'SessionManager' was changed to DEBUG in 'log4jAdmin.jsp'.

[ http://<HOST>:<BEA_PORT>/<ASAP_ENVID>/log4jAdmin.jsp ]

Tried to login to OCA Client and issue was reproduced. Following error messages appeared in 'asap.log' file (Location: WebLogic Domain).

asap.log:

We didn't see a message to indicate that SecurityServices is transitioning from STATE_ADMIN to STATE_ACTIVE WebLogic Log. But in WebLogic Admin console under the Deployment Tab, the securityService was showing Active and Health is OK.

 

 

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
Cause
Solution
References


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