MetaSolv Solution Application Server High CPU; M6 client hangs opening Connection Design through DLRD or RID task (Doc ID 1267874.1)

Last updated on MARCH 29, 2013

Applies to:

Oracle Communications MetaSolv Solution - Version 6.0.15 and later
Information in this document applies to any platform.
*** Reviewed for currency on March, 29th 2013 ***

Symptoms

The problem will have the symptoms listed below:
  • User reports the MetaSolv Solution client (tbs.exe) hangs when attempting to open the Connection Design through a DLRD or RID task by double-clicking the circuit in the Service Request Connections window.
  • High CPU utilization on the machine hosting the WebLogic Server domain where MetaSolv Solution is deployed.
  • Application performance is degraded for users connected to the affected server which must be restarted to recover the system resources.
  • Java thread dumps taken from the WebLogic server show the following code stuck at the same process step.
"ExecuteThread: '10' for queue: 'weblogic.kernel.Default'" daemon prio=5
tid=0x04437598 nid=0x77c runnable [52af000..52afdb8]
     at com.mslv.core.api.internal.NetProv.ConnDesign.CDBaseManager.globalRemove(CDBaseManager.java:81)
     at com.mslv.core.api.internal.NetProv.ConnDesign.DLROrderManager.getRemarks(DLROrderManager.java:2781)
     at com.mslv.core.api.internal.NetProv.ConnDesign.ConnectionDesignManager.getDesignIssue(ConnectionDesignManager.java:952)
     at com.mslv.core.api.internal.NetProv.delegate.pbpackage.ConnDesign.InvInitConnDesign.process(InvInitConnDesign.java:131)
     at MetaSolv.utilities.powerbuilder.BusinessObject.processRequest(BusinessObject.java:67)
     at com.mslv.webapp.pblistener.PBListener.invokeClass(PBListener.java:648)
     at com.mslv.webapp.pblistener.PBListener.doPost(PBListener.java:425)
     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(Web AppServletContext.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)

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