2757 views

Description

Loading data for history view can cause severe performance issues.

Steps to Reproduce

 

Open an instance with Service Mapping and at least 1 business service.

Workaround

If the instance has severe performance issues and threads.do shows something similar to the stack trace below, the immediate solution is to disable a property under Service Mapping > Properties named Sync Service Mapping operations with Service Modeling.

java.lang.Thread.State: RUNNABLE
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:170)
at com.glide.util.ClassUtil.newInstance(ClassUtil.java:95)
at com.glide.glideobject.GlideObjectManager.create(GlideObjectManager.java:108)
at com.glide.script.glide_elements.GlideElementGlideObject.setED(GlideElementGlideObject.java:41)
at com.glide.script.GlideElement.newGlideElement(GlideElement.java:156)
at com.glide.script.GlideElement.newGlideElement(GlideElement.java:116)
at com.glide.script.GlideRecord.loadRow0(GlideRecord.java:3276)
at com.glide.script.GlideRecord.loadRow(GlideRecord.java:3150)
at com.glide.script.GlideRecord.next(GlideRecord.java:5761)
at com.glide.script.GlideRecord.get(GlideRecord.java:1516)
at com.snc.cmdb.service.modeling.impl.DataAccess.get(DataAccess.java:42)
at com.snc.cmdb.service.modeling.impl.ServiceLayerImpl.getRecord(ServiceLayerImpl.java:546)
at com.snc.cmdb.service.modeling.impl.ServiceLayerImpl.<init>(ServiceLayerImpl.java:58)
at com.snc.cmdb.service.modeling.impl.ServiceImplementationFactory.loadLayer(ServiceImplementationFactory.java:267)
at com.snc.cmdb.service.modeling.impl.TimeLineImpl.<init>(TimeLineImpl.java:51)
at com.snc.cmdb.service.modeling.impl.ServiceImplementationFactory.loadTimeLine(ServiceImplementationFactory.java:162)
at com.snc.cmdb.service.modeling.impl.CheckpointImpl.getTimeLine(CheckpointImpl.java:164)
at com.snc.sw.modeling.history.ServiceHistory.getParentDependency(ServiceHistory.java:138)
at com.snc.sw.modeling.history.ServiceHistory.doGetDependencies(ServiceHistory.java:110)
at com.snc.sw.modeling.history.ServiceHistory.doGetDependencies(ServiceHistory.java:111)
at com.snc.sw.modeling.history.ServiceHistory.doGetDependencies(ServiceHistory.java:111)
at com.snc.sw.modeling.history.ServiceHistory.getDependantCheckpoints(ServiceHistory.java:101)
at com.snc.sw.modeling.history.ServiceHistory.getServiceTimeline(ServiceHistory.java:72)
at com.snc.sw.history.HistoryHandler.getModelTimeline(HistoryHandler.java:160)
at com.snc.sw.history.HistoryHandler.getModelTimeline(HistoryHandler.java:132)
at com.snc.sw.history.HistoryHandler.getServiceTimeline(HistoryHandler.java:109)
at com.snc.sw.history.HistoryManager.getServiceTimeline(HistoryManager.java:25)
at com.snc.sw.ui.processors.SWMapProcessor.getServiceTimeline(SWMapProcessor.java:1001)
at com.snc.sw.ui.processors.SWMapProcessor.doProcess(SWMapProcessor.java:126)
at com.snc.sw.ui.processors.SwMapUserActionsProcessor.doProcess(SwMapUserActionsProcessor.java:71)
at com.snc.sw.ui.processors.SaBaseProcessor.process(SaBaseProcessor.java:39)
at com.glide.processors.AProcessor.runProcessor(AProcessor.java:404)
at com.glide.processors.AProcessor.processTransaction(AProcessor.java:178)
at com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:165)
at com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:32)
at com.glide.sys.ServletTransaction.run(ServletTransaction.java:34)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:682)


Related Problem: PRB653962

Seen In

Eureka Patch 13 Hot Fix 5
Fuji Patch 13 Hot Fix 1
Geneva Patch 1
Geneva Patch 1 Hot Fix 5

Fixed In

Geneva Patch 3
Geneva Patch 4
Helsinki

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2016-09-30 17:00:03
Published:2016-02-10