MetaSolv Solution Application Server Stops Responding, Idle Threads go down, White Screen at login (Doc ID 959155.1)

Last updated on JUNE 13, 2017

Applies to:

Oracle Communications MetaSolv Solution - Version 6.0.10 to 6.0.16 [Release 6.0.10 to 6.0.16]
Information in this document applies to any platform.
*** Checked for relevance on 12-Jan-2016 ***

Symptoms

The MetaSolv Solution application server no longer responds or processes new requests.  The application server's "Idle Threads" are significantly reduced or completely consumed.  Users report a blank white screen immediately after login and the application hangs/hourglasses. 

Below are known errors associated with the problem:



<log4j:event logger="cmm.invFromPB" timestamp="1217522171326" level="ERROR" thread="pool-1-thread-395" dateTime="Thu Jul 31 11:36:11 CDT 2008" userName="{USER}"
moduleName="cmm.invFromPB" appServerName="DEF_APPSERVER" messageID="10122" productName="nur" className="DEF_CLASS"debugCode="0" machineName="{SERVER}">
<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[java.sql.SQLException: ORA-00028: your session has been killed ORA-00028: your session has been killed
ORA-06512: at "ASAP.PACKAGE_PSR_COPY", line 4172
ORA-06512: at "ASAP.PACKAGE_PSR_COPY", line 1803
ORA-06512: at "ASAP.PACKAGE_PSR_COPY", line 753
ORA-06512: at "ASAP.PACKAGE_PSR_COPY", line 245
ORA-06512: at line 1
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:305)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:626)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:181)
at oracle.jdbc.driver.T4CCallableStatement.execute_for_rows(T4CCallableStatement.java:870)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1081)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2905)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:2977)
at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(OracleCallableStatement.java:4141)
at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:147)
at com.metasolv.jdbc.MSVPreparedStatement.executeUpdate(MSVPreparedStatement.java:85)
at MetaSolv.utilities.powerbuilder.PBStoredProcedure.executeStoredProc(PBStoredProcedure.java:151)
at MetaSolv.utilities.powerbuilder.PBStoredProcedure.process(PBStoredProcedure.java:258)
at com.metasolv.concurrent.PBRunnable.run(PBRunnable.java:146)
at com.metasolv.concurrent.SerialExecutor$1.run(SerialExecutor.java:35)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:660)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:685)
at java.lang.Thread.run(Thread.java:534)
]]></log4j:throwable>
</log4j:event>


<log4j:event logger="cmm.System" timestamp="1217448357088" level="ERROR" thread="ExecuteThread: '81' for queue: 'weblogic.kernel.Default'" dateTime="Wed Jul 30 15:05:57 CDT 2008" userName="{USER}" moduleName="cmm.System" appServerName="DEF_APPSERVER" messageID="10122" productName="nur" className="DEF_CLASS" debugCode="0" machineName="{SERVER}">
<log4j:message><![CDATA[The server encountered the following Error: MSLVListenerContext.setClientTraceOnReq]]></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[java.lang.RuntimeException: Failed to setAutoCommit to true for pool connection.
at weblogic.jdbc.wrapper.PoolConnection.init(PoolConnection.java:52)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnectionObj(RmiDataSource.java:353)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:319)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:334)
at com.mslv.core.api.internal.shared.MSLVListenerContext.obtainConnection(MSLVListenerContext.java:411)
at com.mslv.core.api.internal.shared.MSLVListenerContext.setClientTraceOnReq(MSLVListenerContext.java:172)
at MetaSolv.utilities.powerbuilder.PBPackage.endElement(PBPackage.java:1075)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
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>


<log4j:event logger="cmm.invFromPB" timestamp="1217448357088" level="ERROR" thread="pool-1-thread-1107" dateTime="Wed Jul 30 15:05:57 CDT 2008" userName="{USER}"
moduleName="cmm.invFromPB" appServerName="DEF_APPSERVER" messageID="10122" productName="nur" className="DEF_CLASS" debugCode="0" machineName="{SERVER}">
<log4j:message><![CDATA[The server encountered the following Error: The context had a null connection.]]></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:event>

<log4j:event logger="cmm.invFromPB" timestamp="1217448357104" level="ERROR"
thread="pool-1-thread-1107" dateTime="Wed Jul 30 15:05:57 CDT 2008" userName="{USER}"
moduleName="cmm.invFromPB" appServerName="DEF_APPSERVER" messageID="10122" productName="nur"
className="DEF_CLASS" debugCode="0" machineName="{SERVER}">
<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[java.lang.NullPointerException
at MetaSolv.utilities.powerbuilder.PBPackage.manageContext(PBPackage.java:1846)
at com.metasolv.concurrent.PBRunnable.run(PBRunnable.java:176)
at com.metasolv.concurrent.SerialExecutor$1.run(SerialExecutor.java:35)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:660)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:685)
at java.lang.Thread.run(Thread.java:534)
]]></log4j:throwable>
</log4j:event>

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms