SAP Knowledge Base Article - Preview

2364586 - PI: Message Monitor times out

Symptom

  1. Within Process Integration (PI), you are not able to open PI Message Monitoring. It is taking a long time and it results in the error "500 Connection timed out".
  2. In the defaultTrace file you can see entries like below: 
    ...sap.com/tc~lm~itsam~co~ui~xi~msg~wdcom.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.XIMessageDetailed.fillValueHelpsForIDocTechnicalAttributes...
    ...[EXCEPTION]
    javax.management.InstanceNotFoundException: com.sap.default:SAP_ITSAMJ2eeCluster.CreationClassName=SAP_ITSAMXIIDOCMonitorSvc,SAP_ITSAMXIIDOCMonitorSvc.SystemName=SAP_ITSAMXIIDOCMonitorSvc...
    ...at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.MessageFilter.fillValueHelpsForIDocTechnicalAttributes...
  3. Thread dumps reveal the thread hangs while reading the data from the SocketInputStream coming from the Sybase database, with a call stack similar to the one below:
    java.lang.Thread.State: RUNNABLE
    at java.net.SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I(Native Method)
    at java.net.SocketInputStream.read([BII)I(SocketInputStream.java:129)
    at com.sybase.jdbc4.timedio.RawDbio.reallyRead(J)I(RawDbio.java:404)
    at com.sybase.jdbc4.timedio.Dbio.doRead(J)V(Dbio.java:257)
    at com.sybase.jdbc4.timedio.InStreamMgr.readIfOwner(ILcom/sybase/jdbc4/timedio/StreamContext;)V(InStreamMgr.java:583)
    at com.sybase.jdbc4.timedio.InStreamMgr.doRead(Lcom/sybase/jdbc4/timedio/StreamContext;)V(InStreamMgr.java:319)
    at com.sybase.jdbc4.tds.TdsProtocolContext.getChunk()Lcom/sybase/jdbc4/utils/BufferInterval;(TdsProtocolContext.java:622)
    at com.sybase.jdbc4.tds.PduInputFormatter.readPacket()Z(PduInputFormatter.java:239)
    at com.sybase.jdbc4.tds.PduInputFormatter.read()I(PduInputFormatter.java:72)
    at com.sybase.jdbc4.tds.TdsInputStream.read()I(TdsInputStream.java:91)
    at com.sybase.jdbc4.tds.TdsInputStream.readUnsignedByte()I(TdsInputStream.java:124)
    at com.sybase.jdbc4.tds.Tds.nextResult(Lcom/sybase/jdbc4/jdbc/ProtocolContext;)I(Tds.java:2912)
    at com.sybase.jdbc4.jdbc.ResultGetter.nextResult()I(ResultGetter.java:78)
    at com.sybase.jdbc4.jdbc.SybStatement.nextResult(Lcom/sybase/jdbc4/jdbc/ParamManager;)I(SybStatement.java:294)
    at com.sybase.jdbc4.jdbc.SybStatement.nextResult()I(SybStatement.java:276)
    at com.sybase.jdbc4.jdbc.SybStatement.queryLoop()Ljava/sql/ResultSet;(SybStatement.java:2643)
    at com.sybase.jdbc4.jdbc.SybStatement.executeQuery(Ljava/lang/String;Lcom/sybase/jdbc4/jdbc/ParamManager;)Ljava/sql/ResultSet;(SybStatement.java:2629)
    at com.sybase.jdbc4.jdbc.SybPreparedStatement.executeQuery()Ljava/sql/ResultSet;(SybPreparedStatement.java:279)
    at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery()Ljava/sql/ResultSet;(BasicPreparedStatement.java:102)
    at com.sap.sql.jdbc.syb.SybPreparedStatement.executeQuery()Ljava/sql/ResultSet;(SybPreparedStatement.java:33)
    at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(Lcom/sap/sql/trace/TraceContext;)Ljava/sql/ResultSet;(DirectPreparedStatement.java:314)
    at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery()Ljava/sql/ResultSet;(CommonPreparedStatement.java:245)
    ...

Read more...

Environment

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

Product

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

Keywords

Loading, Load, Performance, Slow, Waiting, Timed_waiting, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.40, PI 7.40, PO 7.40, Process Orchestration 7.50, PI 7.50, PO 7.50, NetWeaver, XI , KBA , BC-NWA-XPI , Process Integration Monitoring , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.