cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

HTTP_TIMOUT SXMB_MONI

Go to solution
Former Member

on ‎07-05-2014 7:14 AM

0 Kudos

Hi All,

we got issues very weird, we use SAP PI as middleware between SAP and non-SAP, we use synchronization method

we use SAP PI 7.3 double stack and backend is SAP ECC EHP6, the data transferred between legacy system to SAP ECC via SAP PI about 5 MB.

we always got stuck error about TIMEOUT 402 at SXMB_MONI about 900 second, we do not know what problem came from...

<Trace level="1" type="T">Client = 300</Trace>

  <Trace level="1" type="T">Language = E</Trace>

  <Trace level="3" type="T">Creating HTTP-client</Trace>

  <Trace level="3" type="T">HTTP-client: creation finished</Trace>

  <Trace level="1" type="T">Security: Basic authentication SAP</Trace>

  <Trace level="1" type="T">Serializing message object...</Trace>

  <Trace level="1" type="T">HTTP Multipart document length: 22129182</Trace>

  <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

  <Trace level="1" type="T">Timeout: 900</Trace>

  <Trace level="1" type="T">HTTP-client: request sent</Trace>

  <Trace level="3" type="T">HTTP-client: request sent</Trace>

  <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

  <Trace level="1" type="T">402 ICM_HTTP_TIMEOUT</Trace>

  <Trace level="1" type="T">SXMB_ADMIN RUNTIME HTTP_TIMEOUT = 1800000</Trace>

  <Trace level="1" type="T">HTTP:<hostname_fqdn>:52000 PROCTIMEOUT = 3600</Trace>

  <Trace level="3" type="System_Error">HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE</Trace>

  </Trace>

  <Trace level="3" type="System_Error">HTTP-client: error response= <html><head><title>Application Server Error</title></head><body> <H2>500 Connection timed out</H2><br> <hr>Sat Jul 5 07:11:05 2014 </body></html></Trace>

  <Trace level="3" type="T">HTTP-client: closing...</Trace>

  <Trace level="3" type="System_Error">Error while receiving by HTTP (error code: 402 , error text: ICM_HTTP_TIMEOUT)</Trace>

  </Trace>

  </Trace>

  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

-

we already set the system is :

--> SAP PI : we added parameter icm/server_port_0 = PROT=HTTP,PORT=52000,TIMEOUT=3600,PROCTIMEOUT=3600 as well as we set at SXMB_ADM for Category TUNING (HTTP_TIMEOUT = 1800000) also rdisp/max_wprun_time = 3600

--> SAP ECC : add icm/server_port_0 = PROT=HTTP,PORT=8020,TIMEOUT=1800,PROCTIMEOUT=1800

between SAP PI and SAP ECC at same subnet network, no issues about latency network.

thanks

Gho


Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Harish
Active Contributor
‎07-05-2014 2:56 PM
0 Kudos

Hi Gho,

you need to investigate which step is taking more time which leads the message in time out error. Are you using any mapping in pi? What are the adapter used in sender and receiver side (XI for proxy or SOAP over XI)?

Please refer the below doc which can help to investigate the time out

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03...

regards,

Harish

Show replies
Show replies
Former Member
‎07-06-2014 11:36 AM
0 Kudos

Hi harish,

after we analyzed problem root was at SOAP Sender Adapter, on that document is relevant for SAP PI below 7.3 version.

document as your advise is same that we have right now, but thanks you share us also

so our solution is because we use SAP PI with 7.3 version (with SAP XI Adapter Framework SP8) performed by adjust parameter syncTimeout instead of timeout (this parameter only relevant for version below 7.3)

default timeout was 5 minutes, so we increase value of syncTimeout greater than error occurred.

thanks

Answers (0)

Ask a Question