HTTP request failed. Error code: "500". Error message

[Former Member]

Hi ,

When we are trying to test webservices (exposed webservice in PI) scenarios in PI box we are getting error related Adapter framework service

HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://xxxx:xxxx/AdapterFramework/rtc]"

in the RWB it is showing that

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 01d76ce0-972e-11e0-c652-b25394b91e0c(INBOUND) expired

Can any body help .

Edited by: subhaniABAP on Jun 15, 2011 11:30 AM

[Former Member]

The parameter: 'xiadapter.inbound.timeout.default' is an Adapter Engine messaging

system parameter.

The value specifies how long the messaging system waits for a response during

synchronous communication. If this time elapses, a "MessageExpired" exception is triggered.

This parameter will apply to all synchronous messages going through the Adapter Engine messaging

system.

Set property of Service "XPI Adapter: XI" within SAP NetWeaver Administrator

xiadapter.inbound.timeout.default

Default: 180000 [ms]

If this parameter value is not increased to > 3 minutes then the messages will

continue to timeout with the message expired exception.

In NWA, Go to->Operation Management->Systems-> Start & Stop -> Java Services -> (Under Related

Tasks) Java System Properties.

[Former Member]

Hi,

My scenario is Asynchronous,is the above solution applicable

[Former Member]

Are you testing with SoapUI or some other tool?

What is the QualityOfService setted in your endpoint call?

Http error 500, can be also caused by a wrong request format that raise an execution error in destination program.

[Former Member]

Are you testing with SoapUI or some other tool?

was doing the Self Test in PI box.

What is the QualityOfService setted in your endpoint call?

tried both Best Effort/Exactly once

Http error 500, can be also caused by a wrong request format that raise an execution error in destination program.

was using the correct request format

[former_member4985]

Hi,

If you want to resolve this error when dealing with the messages, please try the cache refresh with the link:

http://host:j2eeport/CPACache/refresh?mode=full

And also go thorugh:

- In Integration Repository/Directory go to menu Environment ->

Clear SLD Data Cache

- In R/3 go to transaction SXI_CACHE -> menu XI Runtime Cache -> Start

Complete Cache Refresh

MESSAGE EXPIRED:

Increase the value of the timeout parameter 'xiadapter.inbound.timeout.default' under Services -> 'XPI Adapter:XI'

to a higher value say '600000'.

Regards,

Caio Cagnani

[Former Member]

Check Alert Configuration

SA_COMM parameter CHECK_FOR_ASYNC_RESPONSE_TIMEOUT

This parameter specifies the maximum time in seconds that can pass between the arrival of the synchronous request message on the Integration Server and the asynchronous response message. If this time period is exceeded, a system error is returned to the caller.

See also SAP Note 791379.

[Former Member]

Hi ,

This issue has been solved by changing time out parameters.

Thanks for all the help