Adaptor Error : Message XXX(OUTBOUND) expired

[Former Member]

Hello Experts,

Good Day!! I am getting the following error in Production for a very time critical interface

Adaptor Error : Message XXX(OUTBOUND) expired

Looking at the error , it somewhat seems to be related to the timeout. Is it?

Can you please advise on the root cause? Really appreciate your fast replies as its a time critical interface.

Thanks and regards,

Vikas

[suchitatomar]

Hi ,

1) Check if firewall is there, if yes then Can you reach the URL if you paste it into a browser?

2) or Check if your port is active in smicm

3) check if you have the profile maintained

icm/server_port_0                           PROT=HTTP,PORT=80$$

icm/host_name_full

[Former Member]

Thanks Suchita.

Does it mean the root cause of this error is the timeout and this timeout is applicable only and only if the scenario is synchronous or is it applicable for async scenarios as well ?

Thanks and regards,

Vikas

[Former Member]

Hello Experts,

Any suggestions on the root cause of this error ?

Thanks and regards,

Vikas

[former_member186851]

Hello Vikas,

check our replies,,listed all possibilities.

[Former Member]

Hello Raghu,

As per SAP Note 2206410 - PI Adapter Engine cannot connect to remote system via HTTP(S)

It is saying

The IAIK security library is using the W3C HTTP client library. The SOAP adapter with HTTPS, the J2EE destination service (used in addressing mode "destination" in the SOAP adapter and also other runtime components of PI and J2EE engine are using the IAIK library. With the W3C HTTP library the number of HTTP connection is per default restricted to a very low number (e.g. 50 connections). When a high number of SOAP threads try to establish a HTTP connection there are not enough free threads in the connection pool.

What can I say in one line about the root cause of this error based on the above description?

Can I say the root cause based on the above description as

Number of SOAP threads trying to establish a HTTP connection is exceeding the number of free threads in the connection pool  and the number of HTTP connections per default is restricted in W3C HTTP library (e.g 50 connections). This is resulting into this error.

Please help me on this

Thanks and regards,

Vikas

[former_member186851]

Hello vikas,

yes,could be,

Did you make sure no firewall/port/proxy restrictions.

[Former Member]

Hello Raghu,

What kind of proxy/port restrictions can there be?

Thanks and regards,

Vikas

[iaki_vila]

Hi Fresher,

I had this timeout and in my case was an external server of PI that it had its own timeout and in certain casse with overload it raised a timeout exception.

Regards.

[former_member186851]

Hello Vikas,

From PI to establish you need to open some ports need to be opened and proxy is like some pages might be restricted @ ur office network just an example.When you use proxy you can access them.

But first check with the timeout parameter.

[Former Member]

Thanks a lot Inaki for a very valuable reply.

So does the description of the SAP Note indicate the case of overloading?

The IAIK security library is using the W3C HTTP client library. The SOAP adapter with HTTPS, the J2EE destination service (used in addressing mode "destination" in the SOAP adapter and also other runtime components of PI and J2EE engine are using the IAIK library. With the W3C HTTP library the number of HTTP connection is per default restricted to a very low number (e.g. 50 connections). When a high number of SOAP threads try to establish a HTTP connection there are not enough free threads in the connection pool.

If so then can I say the root cause of the error as

Number of SOAP threads trying to establish a HTTP connection is exceeding(case of overload sometimes) the number of free threads in the connection pool  resulting in this timeout exception

Please advise.

Thanks and regards,

Vikas

[Former Member]

Hi Vikas,

It sounds like timeout issue. Try to increase time out in your receiver channel

If that doesn't work . The message might be timed out in messaging system. So you would need to check the below values in XPI Adapter : XI.

xiadapter.outbound.persistDuration.default

xiadapter.inbound.timeout.default

[Former Member]

Thanks Raghu,Evgeniy and T S.

The Flow is something like this the message is being sent from a messaging system to the SAP system and getting this error.

The complete message log says

SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.RuntimeException: Error while silently connecting: org.w3c.www.protocol.http.HttpException: Unable to contact target server

Is the timeout the root cause?

Thanks and regards,

Vikas

[Eoin_Kierans]

Hi BRM Fresher,

You may wish to check the following notes which detail the timeouts to increase for this type of issue:

2206410 - PI Adapter Engine cannot connect to remote system via HTTP(S)
2211725 - Messages fail in the PI SOAP Adapter with Unable to Contact Target Server Error.

Regards

Eoin

[former_member186851]

Hello vikas,

Could be timeout or may be firewall/proxy issue.

[former_member190293]

Hi BRM Fresher!

If you use synchronous interface it might mean that no response is got within timeout interval.

Regards, Evgeniy.

[former_member186851]

Hello Vikas,

Could be because of timeout.

Post the complete error screenshot and adapter used.