Skip to Content
author's profile photo Former Member
Former Member

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

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 17, 2008 at 02:19 PM

    hI,

    HTTP 500

    o Internal error in J2EE

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

    after timeout

    Regards,

    Sreenivas

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 18, 2008 at 03:42 AM

    Hi Rajesh

    Increase value for icm/conn_timeout

    https://blogs.sap.com/?p=41828

    Have a look on note note 824554

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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 18, 2008 at 07:28 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.