3098733 - Message Status Overview is slow and no data displayed in it

The Message Status Overview in Message Monitor is slow and there is no data displayed after that.

If you capture thread dumps while the Message Monitor is being load, you should see one of the following threads:

• "HTTP Worker [@1421387776]" #169 prio=5 os_prio=64 cpu=179526.78 [reset 1509.91] ms elapsed=1761286.21 [reset 301.16] s allocated=13518798480 B (12.59 GB) [reset 38283920 B (36.51 MB)] defined_classes=549
  io= file i/o: 366786280/550853351 B, net i/o: 49166118/27828892 B, files opened:767, socks opened:29  [reset file i/o: 7487/29774 B, net i/o: 298911/386228 B, files opened:3, socks opened:7 ] 
  user="saposs" session="747496781" request="334316" application="sap.com/com.sap.xi.mdt2" isapplicationthread="true" tid=0x00000001068d5800 nid=0xc2 / 194  lwp-id=194 runnable   [_thread_blocked (_call_back), stack(0xffffffff48380000,0xffffffff48580000)] [0xffffffff48577000] top_bci: 4
     java.lang.Thread.State: RUNNABLE
   at java.io.FilterInputStream.read()I(FilterInputStream.java:86)
   at com.sap.bc.krn.enqu.EnquConv.convToResponse([BII)Lcom/sap/bc/krn/enqu/ServerResponse;(EnquConv.java:554)
   at com.sap.bc.krn.enqu.EnquLocktableClient.lockOpInternal(CIZLjava/lang/String;Ljava/lang/String;CLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Lcom/sap/bc/krn/enqu/EnquLocktableGranule;ZIZ)Lcom/sap/bc/krn/enqu/EnquStatistic;(EnquLocktableClient.java:895)
   at com.sap.bc.krn.enqu.EnquLocktableClient.lockOpChunkTimeout(CILjava/lang/String;Ljava/lang/String;CLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Lcom/sap/bc/krn/enqu/EnquLocktableGranule;ILcom/sap/bc/krn/enqu/EnquWaitTimeCal;)V(EnquLocktableClient.java:712)
   at com.sap.bc.krn.enqu.EnquLocktableClient.lockOpTimeout(CIZLjava/lang/String;Ljava/lang/String;CLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Lcom/sap/bc/krn/enqu/EnquLocktableGranule;ILcom/sap/bc/krn/enqu/EnquWaitTimeCal;)V(EnquLocktableClient.java:377)
   at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;CLjava/lang/String;I)V(LockingManagerImpl.java:159)
   at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;CLjava/lang/String;I)V(AbstractLockingManagerImpl.java:466)
   at com.sap.engine.core.locking.ServerInternalLockingImpl.lock(Ljava/lang/String;Ljava/lang/String;CI)V(ServerInternalLockingImpl.java:52)
   at com.sap.aii.af.service.statistic.impl.LockManager.blockAndSetLock(Ljava/lang/String;I)Z(LockManager.java:66)
   at com.sap.pi.monitor.statistics.LocalMsgOverviewDataProvider.getIViewData(Lcom/sap/aii/af/service/statistic/IView;Lcom/sap/aii/af/service/statistic/UIPeriod;ZZ)[Lcom/sap/aii/af/service/statistic/IViewData;(LocalMsgOverviewDataProvider.java:187)
   at com.sap.pi.monitor.statistics.AFMsgOverviewDataProvider.getIViewData(Lcom/sap/aii/af/service/statistic/IView;Lcom/sap/aii/af/service/statistic/UIPeriod;ZZ)[Lcom/sap/aii/af/service/statistic/IViewData;(AFMsgOverviewDataProvider.java:96)
   at com.sap.pi.monitor.statistics.MessageOverviewBean.getViewData(Lcom/sap/aii/mdt/server/statistics/Interval;Z)[Lcom/sap/aii/mdt/server/statistics/IViewData;(MessageOverviewBean.java:368)
  ...
  
• "HTTP Worker [@711911119]" #150 prio=5 os_prio=0 cpu=109218.75 [reset 312.50] ms elapsed=282468.97 [reset 54.48] s allocated=31531449896 B (29.37 GB) [reset 39392272 B (37.57 MB)] defined_classes=3793
  io= file i/o: 213634205/296945928 B, net i/o: 286709131/62117533 B, files opened:1486, socks opened:-14  [reset file i/o: 8739/0 B, net i/o: 277504/288749 B, files opened:4, socks opened:6 ] 
  user="SAP_PXJ_OSS1" session="-1653299035" request="85325" application="sap.com/com.sap.xi.mdt2" isapplicationthread="true" tid=0x000001b709ce9000 nid=0x2338 / 9016 waiting on condition   [_thread_blocked (_at_safepoint), stack(0x0000003f23200000,0x0000003f23400000)] [0x0000003f233fb000]
     java.lang.Thread.State: TIMED_WAITING (sleeping)
   at java.lang.Thread.sleep(J)V(Native Method)
   at com.sap.bc.krn.enqu.EnquLocktableClient.lockOpChunkTimeout(CILjava/lang/String;Ljava/lang/String;CLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Lcom/sap/bc/krn/enqu/EnquLocktableGranule;ILcom/sap/bc/krn/enqu/EnquWaitTimeCal;)V(EnquLocktableClient.java:702)
   at com.sap.bc.krn.enqu.EnquLocktableClient.lockOpTimeout(CIZLjava/lang/String;Ljava/lang/String;CLjava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;[Lcom/sap/bc/krn/enqu/EnquLocktableGranule;ILcom/sap/bc/krn/enqu/EnquWaitTimeCal;)V(EnquLocktableClient.java:377)
   at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;CLjava/lang/String;I)V(LockingManagerImpl.java:159)
   at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;CLjava/lang/String;I)V(AbstractLockingManagerImpl.java:466)
   at com.sap.engine.core.locking.ServerInternalLockingImpl.lock(Ljava/lang/String;Ljava/lang/String;CI)V(ServerInternalLockingImpl.java:52)
   at com.sap.aii.af.service.statistic.impl.LockManager.blockAndSetLock(Ljava/lang/String;I)Z(LockManager.java:66)
   at com.sap.pi.monitor.statistics.LocalMsgOverviewDataProvider.getIViewData(Lcom/sap/aii/af/service/statistic/IView;Lcom/sap/aii/af/service/statistic/UIPeriod;ZZ)[Lcom/sap/aii/af/service/statistic/IViewData;(LocalMsgOverviewDataProvider.java:187)
   at com.sap.pi.monitor.statistics.AFMsgOverviewDataProvider.getIViewData(Lcom/sap/aii/af/service/statistic/IView;Lcom/sap/aii/af/service/statistic/UIPeriod;ZZ)[Lcom/sap/aii/af/service/statistic/IViewData;(AFMsgOverviewDataProvider.java:96)
   at com.sap.pi.monitor.statistics.MessageOverviewBean.getViewData(Lcom/sap/aii/mdt/server/statistics/Interval;Z)[Lcom/sap/aii/mdt/server/statistics/IViewData;(MessageOverviewBean.java:374)
  ...

If you check the Default traces as well, you could see the following entry:

• com.sap.pi.monitor.statistics.LocalMsgOverviewDataProvider.getIViewData: Unable to get monitoring lock for Profile Data.

• SAP enhancement package 1 for SAP NetWeaver 7.3
• SAP NetWeaver 7.4
• SAP NetWeaver 7.5

Process Integration, Process Orchestration, PI 7.4, PO 7.5, Message, monitor, Message Status Overview, overview, Aggregation, EnquLocktableClient, enqueue server, SOLMAN, XI_AF_PROF_CACHE, PROF_AGG_JOB, PROF_AGG_JOB_MON, lock, monitoring, getIViewData, Profile, Data , KBA , BC-NWA-XPI , Process Integration (PI) Monitoring , Problem