cancel
Showing results for 
Search instead for 
Did you mean: 

500 Connection timed out

former_member182374
Active Contributor
0 Kudos

Hello Experts,

I've a Web Dynpro ABAP application.

When a user clicks a button he runs time intensive function (if I run the function directly from SE37 it takes 90 seconds).

I'm getting a timeout 500 error message (see screenshot).

I read that timeout errors in WDA usually related to ICM but as far as I remember ICM errors contain the word 'ICM' in the error message (c module, error line etc).

Also, I didn't find any log entry in SM21 for the error.

Where can I find the detailed error message?

Regards,

Omri

Accepted Solutions (1)

Accepted Solutions (1)

former_member182374
Active Contributor
0 Kudos

Solved by changing to icm/keep_alive_timeout from 60 seconds to 300 seconds.

Omri

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Omri,

It seems like the timeout of the HTTP connections is too low. Contact the basis team and ask them to increase the timeout of HTTP connections.

-Manish

former_member182374
Active Contributor
0 Kudos

Hi Manish Kumar,

Do you know the exact name of the profile parameter?

Regards,

Omri

Former Member
0 Kudos

Hi Omri,

To ensure that we are talking about the right timeout, do you observe any relevant error logged in the ICM trace (dev_icm)? For a time-consuming applicaiton, I would suspect the ICM processing timeout (PROCTIMEOUT in icm/server_port).

The so-called connection timeout (icm/conn_timeout) specifies the timeout for connection establishment to a remote server. This has something to do with the network performance of connection establishment and has nothing to do with the application intensiveness.

Best regards,

Jun

former_member182374
Active Contributor
0 Kudos

Hi Jun,

As far as I know ICM errors looks like this:

Error: -5

Version 7010

Component: ICM

Connection to partner  timed out after 60s

In my case only  "500 Connection timed out" is displayed on screen.

Regards,

Omri

Former Member
0 Kudos

Hi Omri,

That means, it is the ICM processing timeout. Please increase the ICM processing timeout (PROCTIMEOUT as mentioned earlier) accordingly and restart the server/ICM to accommodate the time intensive applications.

Best regards,

Jun