FWK005 Parse May Not Be Called While Parsing Errors and Associated Behaviors
(Doc ID 780658.1)
Last updated on SEPTEMBER 19, 2024
Applies to:
Oracle Communications MetaSolv Solution - Version 6.0.15 to 6.0.16 [Release 6.0.15 to 6.0.16]Information in this document applies to any platform.
*** ***
***Checked for relevance on 01-Apr-2015***
Symptoms
The errors listed below have been reported by numerous customers. The problem has been intermittent in nature, but encountered more frequently under load or degraded performance conditions as well as known long running processes such as Copy Branch to Order for large amounts of service item data to be copied, Circuit Design for large networks, large data jobs sent to the Background Processor, etc.
Errors displayed to the MetaSolv Solution user or Background Processor
- A database error has occurred. The error message is: Error - No SQLCA defined
- PBPackageError: SAXException - xml parser error
FWK005 parse may not be called while parsing
Error captured in the [SERVERNAME].mss.log
- error in parseorg.xml.sax.SAXException: FWK005 parse may not be called while parsing.
- BEA-101083 messages
- BEA-101326 messages
Error captured in the appserverlog.xml
- <log4j:event logger='cmm.invFromPB' timestamp='1179519213993' level='ERROR' thread='ExecuteThread: '23' for queue: 'weblogic.kernel.Default'' dateTime='Fri May 18 15:13:33 CDT 2007' userName='<USERNAME>' moduleName='cmm.invFromPB' appServerName='DEF_APPSERVER' messageID='10122' productName='nur' className='DEF_CLASS' debugCode='0' machineName='<MACHINENAME>'>
<log4j:message><![CDATA[The server encountered the following Error: ]]></log4j:message>
<log4j:cause><![CDATA[The server encountered the following Error:]]></log4j:cause>
<log4j:action><![CDATA[The server encountered the following Error:]]></log4j:action>
<log4j:throwable><![CDATA[org.xml.sax.SAXException: FWK005 parse may not be called while parsing.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at MetaSolv.utilities.powerbuilder.PBPackage.fromXML(PBPackage.java:518)
at com.mslv.webapp.pblistener.PBListener.getPBPackageFromRequest(PBListener.java:683)
at com.mslv.webapp.pblistener.PBListener.doPost(PBListener.java:399)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6981)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
]]></log4j:throwable>
</log4j:event>
Changes
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 |
References |