Synchronous Timeout Error in SOAP Axis Receiver Adapter

[Former Member]

Hi PI Experts,

For  SOAP -> PI  -> SOAP Synchronous scenario, I am using SOAP Protocol (HTTP Axis) receiver adapter as receiver web service is using SOAP 1.2 protocol,

But I am getting Synchronous timeout exceeded error and Read timeout error after 5 mins in receiver Axis adapter.

Can you please help in sorting this issue ?

And where EXACTLY(in which processing sequence) in module configuration of Axis receiver adapter I can added XMBWS.Timeout 1200000 if that can solve my problem?

PS: there are no network issues (like firewall) and wsdl URL is opening perfectly fine in browser and PI server browser as well.

http://PIHost:Port/XIAxisAdapter/MessageServlet is also opening perfectly fine

Axis Receiver adapter configuration as below:

URL : as per WS team,

Authentication basic : user name and password as given as WS team.

SOAP version 1.2

SOAP action : from wsdl file

Encapsulation Format : MIME

Payload Extraction: SOAP body

Module Configuration: as it comes when we create the channel.

Please help

Thanks in advance.

Regards,

SV

[Former Member]

Hi,

Can you confirm that all the Ports and IP's have been opened on both your side and the 3rd party side? This might also cause a timeout. Is third party name resolving on your DNS or your host file? If not it might be unable to resolve.

So if networks is open. Then can you please ask the third party if the service is up and running and receiving data?

Because it might be going into an infinite loop on there side(maybe).

Can you please switch from SOAP action 1.2 to 1.1.

Please send me what you have in your adapter modules  tab? And what error is being generated on NWA Logs under developer logs?

Regards,

Jannus Botha

[Former Member]

Hi Jannus,

All ports and IP's are opened and third party services are up and running but they are not receiving any data.

If I switch to SOAP 1.2 to SOAP 1.1 -> getting http 415 error( which says mismatch of versions).

If I use SOAP action in HTTP Axis Adapter receiver , error encountered -> synchronous timeout exceeded in nwa/logs as well.

If I don't use SOAP action in HTTP Axis adapter receiver , error encountered -> error occurred while verifying the security for message.

Third party is using ASP>NET

Adapter Module configuration screenshot attached, it is one which comes standard when we configure Axis (http) receiver adapter.

Please provide your valuable inputs so issue is sorted.

Regards,

SV

[Former Member]

Attachment is missing.

[Former Member]

Sorry, my bad..

here goes the attachment..

Regards,

SV

[Former Member]

All the module keys are not configured. Could you correct it and check?

[Former Member]

Hi,

You are missing a few keys. Please see attached.

Regards,

Jannus Botha

[Former Member]

Hi Jannus,

I am getting the  error in channel monitoring as in screenshot when added the module configuration as in screenshot shared by you.

I am using basic authentication with username and password.

URL starts with http:// noy http(s)

SV

[Former Member]

could you show us nwa audit log?

[Former Member]

Hi,

Screenshot attached from nwa/logs.

Regards,

SV

[Former Member]

Hi Sarvjeet,

  What are the missing Optional components on Axis Adapter Message Servlet page? I guess one of the optional components required for your configuration is missing.

Please check the SAP Note 0001039369. It has detailed FAQ and will help you in resolving your issues.

Regards

Charan

[Former Member]

Hi PI experts,

And when I remove the SOAP action from the channel.

I am getting error " error occurred while verifying the security of the message".

Please help if I am missing some configuration in PI or there is some problem at target WS team end?

Regards,

SV

[Former Member]

Hello,

There might be use of RFC Lookup somewhere in your message mapping. Please check the function module used in it. Debug the same and you can hence find out where exactly it is consuming time.

Regards,

Souvik

[Former Member]

Hi Souvik.

I am not using any RFC_Lookup, it is one to one mapping.. any other setting I need to chek

Thanks,

Regards,

SV