SAP Knowledge Base Article - Preview

3662450 - High CPU Usage by JStart Due to Blocked Threads in Custom Pulsar Adapter (Advantco)

Symptom

  • Excessive CPU utilization by JStart process observed in an SAP NetWeaver system.
  • Thread dumps reveal blocked threads referencing the class: com.crimp.pulsarreceiver.adapter.ra.SPIManagedConnectionFactory.

Thread Dump shows log similar to:

java.lang.Thread.State: BLOCKED (on object monitor)
at com.crimp.pulsarreceiver.adapter.ra.SPIManagedConnectionFactory.createClientSession
 - waiting to lock <0x0000000000000> (a java.lang.Class for com.crimp.pulsarreceiver.adapter.ra.SPIManagedConnectionFactory)


Read more...

Environment

  • SAP NetWeaver
  • SAP Process Integration

Product

SAP NetWeaver all versions ; SAP Process Integration all versions

Keywords

JStart high CPU, SAP NetWeaver CPU usage, blocked thread SPIManagedConnectionFactory, Pulsar adapter SAP PO, Advantco Pulsar adapter issue, custom adapter CPU problem, JStart thread dump blocked, Apache Pulsar SAP integration, com.crimp.pulsarreceiver.adapter.ra.SPIManagedConnectionFactory, high CPU usage SAP PO custom adapter, SAP PI PO JStart performance issue, thread blocking Pulsar adapter SAP, SAP PO supported adapters list; , KBA , SV-PERF-PI , SAP Process Integration (PI) related performance issues , SV-PERF-JAS , SAP NetWeaver AS Java related performance issues , Problem

About this page

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

Search for additional results

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