Problem with SOAP receiver

[Former Member]

Hello,

Our PI system is 7.4 . We have a lot of interface with related to  proxy to soap.When they are used  very intensively, errors occur in soap receiver .

Types are error: 

503 server  not avalibale,

401 unauthorized ,

invalid content type for SOAP:TEXT/HTML  such as...

When system is restarted, mostly it is worked but after while again errors occur and a lot of message is waiting in queue.

what can we do for it?

Thanks in advance,

Nurhan

[markangelo_dihiansan · Accepted solution]

Hi,

It has something to do with timeouts. See section 2.2 of this document for 401 and 503 errors. It also contains the solution.

Hope this helps,

Mark

[Former Member]

Check with your basis, Its all due to problem with timeout paramenters, Max connections settings.

Check this note as well : 824554

Thanks & Reagrds,

A.Neelima.

[claudia_liszy]

Hi Nurhan,

is your PI based on a single or dual stack? Where does the error occur?

If you get this error on the ABAP stack, there could be communication issues between ABAP and Java stack. That is why restarting the PI helps temporarily.

If it is only Java, the receiver could cause this issue. Can you give me more information about the communication scenario?

Claudia

[Former Member]

Hi Claudia,

It is dual stack installation. While calling  soap receiver adapter, error occur. In sxmb_moni  display error  as follows:

After restart, we have new error:

It is abap proxy to soap scenario. It's synchronous communication.

Thanks,

Nurhan

[claudia_liszy]

Hi Nurhan,

it seems like the message failed because of a performance issue on the java stack. In my opinion the 401 unauthorized error is just a aftereffect of the main error 503 service unavailable.

Can you check with your basis colleagues whether all server nodes are configured correctly and properly to be able to process a high amount of messages?

Regards

Claudia