strange soapUI TimeOut

[Dimitri]

Dear,

I've a very simple asynchronous scenario: web service -> SAP PO 7.4 -> file.

Without a operation mapping in my ICO object, it performs as expected.

But when I include the operation mapping, containing a graphical message mapping with only 2 fields, I get this error in soapUI:

ERROR:java.net.SocketTimeoutException: Read timed out

java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(Unknown Source)

at java.net.SocketInputStream.read(Unknown Source)

at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)

at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)

at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)

at org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)

at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)

at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)

at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)

Any thoughts?

Thanks a lot.

[udo_martens · Accepted solution]

Hi Dimitri,

I've a very simple asynchronous scenario: web service -> SAP PO 7.4 -> file.

There must be a missunderstanding.

A webservice can only receive messages, not send. You mean a web client?

An asynchronous message actually does not have a timeout.

How did u develop?

I guess you have built the scenario in PO and created the WSDL from the integrated configuration. Please check your sender adapter: Quality of Service should be "Exactly Once".

/Udo

[anand_shankar10 · Accepted solution]

Hi Udo,

This must be a wsdl created by SAP PI which is consumed by a webclient to send messages to PI using SOAP sender channel.

Regards

Anand

[Dimitri · Accepted solution]

Hi Udo,

You're absolutely right. I re-used a SOAP communication channel which I used before in a synchronous scenario. Now, the message is entering the SAP PO system. Apologies for this.

What I see is that this message remains in status delivering and the message log is mentioning executing request mapping "name of the operation mapping".

Any ideas?

Thank you.

[udo_martens · Accepted solution]

Hi Dimitri,

look to your integrated configuration -> Receiver Interface / Operation Mapping. May be delete the configuration and create it new, just 1 minute.

/Udo

[Former Member · Accepted solution]

Hi Dimitri,

Please create the integrated scenario from scratch. Think Udo is right that something might be missing.

Regards,

Jannus Botha

[Dimitri · Accepted solution]

Hi Udo,

I tried several things and also created new Service Interfaces and a new communication channel.

Still no success and the message remains in status delivering.

Any suggestions?

Thanks -.

[Former Member · Accepted solution]

Hi Dimitri,

A message in delivering state cannot be cancel or reprocessed. You need to force into error status. You can achieve this by restarting the java instance.

And if you make changes to the configuration make sure to test with a new message.

Did you try and resend a old message, if so please test with a new message.

Your target is SOAP correct? Please ask the third party to make sure that the service is up and running.

Please also confirm with the network guys that the Firewall Rules have been added to allow communications in and out.

Good luck,

Regards,

Jannus Botha

[Dimitri · Accepted solution]

Hi Jannus, Udo,

I focused on the message mapping step...

When I test my message mapping, it all looks good.

But when I compare my message mapping input structure with the one imported in soapUI (coming from the exported WSDL, based on ICO), I see many differences.

How can it be the message mapping structure deviates from the WSDL structure in soapUI ?

Thanks