TimeOut Error Occuring when trying to connect to MessageMonitorin g in RWB

[Former Member]

Hello All,

I am getting the below error when trying to connect to MessageMonitoring in RWB

500 Connection timed out

-

---

Error: -5

Version: 7000

Component: ICM

Date/Time: Wed Dec 17 18:36:44 2008

Module: icxxthr.c

Line: 2646

Server: DB0I2P01_SIP_10

Error Tag: {-}

Detail: Connection to partner timed out after 60s

[Former Member · Accepted solution]

hI,

HTTP 500

o Internal error in J2EE

o Check SAP Note 807000 - Http requests are not fully read

after timeout

Regards,

Sreenivas

[Former Member]

Hi Rajesh

error code 5xx stand for Server Error

The server failed to fulfill an apparently valid request.

Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.

error code 500 stands for internal Server Error

First increase the time out. if not solved then

your problem will be solved by restarting J2EE engine

steps to restart J2EE engine

1) run transaction SMICM

2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart

by this java engine will restart and will be up in 5-10 minutes and your problem will be solved

for more details on error code follow the link

http://www.web-cache.com/Writings/http-status-codes.html

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm

Thanks

sandeep sharma

[Former Member]

It Worked by refreshing the cache.

Thanks for all your responses.

-Rajesh

[dharamveer_gaur2]

Hi Rajesh

Increase value for icm/conn_timeout

Have a look on note note 824554

If any thing don't work then try Re-starting the JAVA Stack will solve your issue.