401 Error Proxy to SOAP

[Former Member]

Hi,

We have sync interface for Proxy to SOAP. This interface works fine when run once.

When we did volume testing, 10% of the messages ( randomly) failed with 401 Unauthorized & 503 Service not aviabale.

After researching we found a note 821026 which talks about the issue. We have done changes as per the note & inclease the connection Pool max to 100.

Please advice, if there is anything we can do as it is still failing with 401 & 503 in PI.

Regards

[prateek]

Would that be ok if you just receive the messages without error but a bit delayed? If yes parameter max_wait_time shoudl be set properly. poolmaxsize have a limit. Don't increase it randomly. Try 50.

This all will still be valid for only 401 error. For 503, usally means that the target system is unable to handle that load. So there is nothing much you can do at PI for it. You need to contact the target system admin to review the connection pool at their end.

Regards,

Prateek Raj Srivastava

[Former Member]

Hi All,

Thanks for reply. We have 3 PI Systems which calls the same Web service via SOAP ( Syn proxy-SOAP.

First we observed this error in one of the system & now it comes in all. The error is

com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out

The sequence of event is Inbound message from ECC looks good, the Mapping is OK. I see in response the red & the error is in Inbound of Response.

Below is the log in MDT

02.02.2012 18:12:03 Information The message was successfully received by the messaging system. Protocol: XI URL: http://xxxxpd312.r1-core.r1.xxx.net:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

02.02.2012 18:12:03 Information Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.

02.02.2012 18:12:03 Information Message successfully put into the queue.

02.02.2012 18:12:03 Information The message was successfully retrieved from the request queue.

02.02.2012 18:12:03 Information The message status was set to DLNG.

02.02.2012 18:12:03 Information Delivering to channel: CC_SOAP_Rcvr_PaymentVerification

02.02.2012 18:12:03 Information MP: entering1

02.02.2012 18:12:03 Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

02.02.2012 18:12:03 Information SOAP: request message entering the adapter with user J2EE_GUEST

02.02.2012 18:12:18 Error SOAP: call failed: java.net.SocketTimeoutException: Read timed out

SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out

02.02.2012 18:12:18 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out

02.02.2012 18:12:18 Error Adapter Framework caught exception: java.net.SocketTimeoutException: Read timed out

02.02.2012 18:12:18 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out. Setting message to status failed.

• SXMB Log from ECC . This is shown

<!-- Inbound Message

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

I am not sure if this is issue in calling adapter engine( while sedning to web service) or When the Data is being send to Proxy this issue comes in.

Ps: We have gone through many notes & increase the connection pool & max wait time.

Also we have increase the time out in SOAP adapter with no effect. BASIS is looking at SXMB_ADM Http paramterto increase but this was systems were working fine before that.

Now even one message is not flowing.

Thanks & please advice

I

[Former Member]

HI All,

Any suggestion is appreciated

Regards.

[Former Member]

Hi All,

We are getting 401 unauthorized error while sending the high volume ( Proxy-to SOAP) Sync. This is in between the success messages and no password issues as we are getting in only 10% of the message

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>

<SAP:P1>401</SAP:P1>

<SAP:P2>Unauthorized</SAP:P2>

<SAP:P3>(See attachment HTMLError for details)</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

Can you please advice on this.

Regards

Edited by: harry101_SAP on Feb 9, 2012 4:25 PM

[Former Member]

Hi Harry,

How many concurrent messages are you sending ?

Did you try limiting that number to 100 ?

Regards,

Horia

[Former Member]

Hi,

We have around 1000+ messages coming from ECC. The ECC runs the payment run & PI get all the messages.

There is no way to control the messages numbers as it deepens upon the other factors

We have done many things including suggested in below note. We have increased the connection to 1000, with worst results.

Also we are getting diff kinds of errors with 503 & 401, may be all pointing to performance.

Please advice, if anything else can be don on this.

Regards