2510978 - Socket Event XML Output Adapter hung for 43 minutes - SAP Event Stream Processor | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2510978 - Socket Event XML Output Adapter hung for 43 minutes - SAP Event Stream Processor

Symptom

  • Data is being sent to the Event Stream Processor project at a slow pace of around 9 events per second.
  • It is observed that all the queues are empty and the system's CPU was around 8% utilization for all tasks.
  • Multiple Socket Event XML Output Adapters are connected to the same socket server and port.
  • Around 6.5 hours after the project starts receiving data, one of the XML Output Adapters stops sending data.
  • The ESP project keeps receiving events and sending them out, and the events do not appear on the network until 43 minutes later, when the adapter suddenly sends all the backed up events at once.
  • The adapter's log files contain no messages after the startup sequence completed.
  • The project had previously been receiving data at 4 times the speed with no backlog.
  • The project log (esp_server.log) reports a queue at 99% of its limit at the time the adapter stopped sending.

2017-07-21 15:15:26.439 | 24580 | container | [SP-4-108001] (21622.699) sp(11904) GatewayClient(24580:215)::~GatewayClient() destroyed (auto).
2017-07-21 15:49:00.686 | 3076 | container | [SP-4-108060] (23636.944) sp(11904) GatewayClient::S_post(21120:216) queue at 99% of limit.
2017-07-21 15:54:13.983 | 19884 | container | [SP-4-108060] (23950.243) sp(11904) GatewayClient::S_post(27824:148) queue at 99% of limit.
2017-07-21 16:18:16.620 | 27408 | container | [SP-4-108060] (25392.879) sp(11904) GatewayClient::S_post(13196:149) queue at 99% of limit.
2017-07-21 16:32:18.128 | 13196 | container | [SP-4-108001] (26234.388) sp(11904) GatewayClient(13196:149)::~GatewayClient() destroyed (auto).
2017-07-21 16:32:18.504 | 27824 | container | [SP-4-108001] (26234.764) sp(11904) GatewayClient(27824:148)::~GatewayClient() destroyed (auto).
2017-07-21 16:32:19.494 | 23620 | container | [SP-4-108001] (26235.753) sp(11904) GatewayClient(23620:150)::~GatewayClient() destroyed (auto).
2017-07-21 16:32:19.496 | 22556 | container | [SP-4-108001] (26235.756) sp(11904) GatewayClient(22556:153)::~GatewayClient() destroyed (auto).
2017-07-21 16:32:19.498 | 22588 | container | [SP-4-108001] (26235.756) sp(11904) GatewayClient(22588:192)::~GatewayClient() destroyed (auto).
2017-07-21 16:32:19.499 | 28332 | container | [SP-4-108001] (26235.754) sp(11904) GatewayClient(28332:151)::~GatewayClient() destroyed (auto).
2017-07-21 16:32:20.166 | 3076 | container | [SP-4-108061] (26236.426) sp(11904) GatewayClient::S_post(21120:216) queue dropped below 51% of limit.
2017-07-21 16:32:20.211 | 28328 | container | [SP-4-108001] (26236.454) sp(11904) GatewayClient(28328:152)::~GatewayClient() destroyed (auto).
2017-07-21 16:32:20.251 | 21120 | container | [SP-4-108001] (26236.510) sp(11904) GatewayClient(21120:216)::~GatewayClient() destroyed (auto).


Read more...

Environment

  • SAP Event Stream Processor (ESP) 5.1 SP12 Rev122 PL10
  • Microsoft Windows

Product

SAP Event Stream Processor 5.1

Keywords

streaming, processing, esp , KBA , BC-SYB-ESP , Sybase ESP (Event Stream Processor) , 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.