pi to bpm - Failed to call the endpoint: Error in call over HTTP: HTTP 0 null

[former_member183906]

hi

i am using pi 740 single stack system. the scenario is PI to BPM to 3rd party server.

If 1000 successful messages from PI to BPM , 5 messages fail from PI to BPM with below error -

Failed to call the endpoint: Error in call over HTTP: HTTP 0 null

SOAP: Call failed: java.net.SocketTimeoutException: Read timed out

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out

Same scenario,same interface,same kind of message data 1000 messages are successful ,but 5 gets failed.

BPM URL -http://localhost:50000/MessagingSystem/receive/JPR/XI and it is working perfectly fine.

What could be the cause of this error from PI to BPM messages ?

[AnilDandi · Accepted solution]

Hi,

Try recreating the issue while XPI Inspector is started.

Looks like the system is unable to handle the spike in volume and resulting in many requests to wait until timeout.

Try increasing max number of threads (icm/max_threads) and timeout for http service (icm/server_port_0 = PROT=HTTP,PORT=5$(SAPSYSTEM)00,TIMEOUT=1800,PROCTIMEOUT=16000) in ICM.

Increase XMBWS.Timeout value in the Communication Channel.

regards

AKD

[former_member183906 · Accepted solution]

where is http timeout setting done in PI single stack

Try increasing max number of threads (icm/max_threads) and timeout for http service (icm/server_port_0 = PROT=HTTP,PORT=5$(SAPSYSTEM)00,TIMEOUT=1800,PROCTIMEOUT=16000) in ICM.

[AnilDandi · Accepted solution]

You can change/set both the parameters in the instance profile in /usr/sap/<SID>/SYS/profile.

Please get the Basis admin to make the changes if you are not the admin.

[former_member183906 · Accepted solution]

(icm/server_port_0 = PROT=HTTP,PORT=5$(SAPSYSTEM)00,TIMEOUT=1800,PROCTIMEOUT=16000) in ICM.

1800 seconds and 16000 seconds is too much..

SAP help tells its parameter in seconds.. Whats your say in it..

[AnilDandi · Accepted solution]

You may try increasing in steps of 5 mins until the issue doesn't occur anymore.