500 Connection timed out

[Former Member]

Hi All,

While running my BSP application in production system I got a the following output on clicking of a button which performs some search operation.

500 Connection timed out


--------------------------------------------------------------------------------
Error: -5 
Version: 7000 
Component: ICM 
Date/Time: Wed Jul 25 15:12:45 2007  
Module: icxxthr_mt.c 
Line: 2646 
Server: pep168_P92_10 
Error Tag: {-} 
Detail: Connection to partner timed out after 60s

can anyone please help me on this?

Thanks

Shilpa

[Former Member · Accepted solution]

Hi ,

This happen due the Internet communication manager responding time ,first time whenever you call an BSP application it will take some time to load it. As per the error

-

---

Error: -5

Version: 7000

Component: ICM

Date/Time: Wed Jul 25 15:53:02 2007

Module: icxxthr_mt.c

Line: 2646

Server: pep168_P92_10

Error Tag: {-}

Detail: Connection to partner timed out after 60s

you have informed that you have set to 3 hrs. No it is not properly done.It is only 60s only.

Please do this your problem will be solved .

Solution:

In RZ10

go to Instance profile add the profile:

icm/keep_alive_timeout=240 -that is 4 minutes(don't keep this time too high,<5 mins).After that you have to restart the WAS.This change will come in to effect after restart only.Please tell you Basis Admin.

After this also not working , please check your program.

Thanks,

Nagendran

[norbertk]

hi shilpa,

besides setting the mentioned profile parameter you can also set the keep-alive- and processing timeout for the http-service in trans. smicm, goto -> services, service -> change. but this timeout is reset on restart of the server, so it may be better to set the profile-parameter.

the increased session-timeout set in sicf does not help you with your problem.

regards,

norbert

[raja_thangamani]

you can increase the time out parameter icm/keep_alive_timeout.

You can decide how long the session can last if you double click on the application node within SICF. Under the service options, you can define a session timeout.

<i>*Reward each useful answer</i>

Raja T

[Former Member]

Hi

Thanks for the reply,

Can u plz tell me where to set this parameter after identifying the application node.

Thanks

Shilpa

[raja_thangamani]

In Tcode SICF, identify your BSP Application mode. Double click on Node..In "Service Data" tab, mention the Session Time out .

Hope this is clear.

<i>*Reward each useful answer</i>

Raja T

[Former Member]

Hi raja,

I have done the changes as told by you and now i have set it to 3 Hrs .

Still the problem persists.

500 Connection timed out

-

---

Error: -5

Version: 7000

Component: ICM

Date/Time: Wed Jul 25 15:53:02 2007

Module: icxxthr_mt.c

Line: 2646

Server: pep168_P92_10

Error Tag: {-}

Detail: Connection to partner timed out after 60s

[raja_thangamani]

It should work..Try to log-off & login again..also close all the browser. Still if you have an issue, change the profile parameter.

<b>*Reward each useful answer</b>

Raja T

[Former Member]

Hi

Its still not working...

Plz suggest some thg else..

thanks

shilpa

[raja_thangamani]

Did you change the Profile Parameter? If so you need to <b>reboot the WAS</b> to get the effect of new profile.

<b>*Reward each useful answer</b>

Raja T

[Former Member]

Hi Raja,

Can you please elaborate this point of profile setting and server restart?

Thanks and Regards

Shilpa Dhawan

[Former Member]

HI Raja,

Can you please tell me how to change the profile parameter?

which transaction? and which parameter?

Thanks in advance

Regards

Shilpa Dhawan

[Former Member]

Hi,

please goto transaction RZ10 choose the instance profile by value help and mark extended maintainance. Press Change Button.

Search for a parameter looking like icm/server_port_<xx> where parameter value is PROT=HTTP or whatever you are using.

Now double click this parameter and extend its value by adding PROCTIMEOUT=<some_timeout>. Save this and let your basis restart your system. What effects that: ICM waits for processing a requests as many seconds as you defined here. If time is over and ICM has no response from server it will send the HTTP 500 error. I would not set this to something like 3 hours - since I do not know a user who will wait on a website for that time.Another thing, processes could take too long ressources from server.

Regards,

Sebastian