Intermittent Connection reset

, ,
1

Hello!
I have an intermittent problem that I can’t resolve. Sometimes (and often!) when our IS webMethods 8.2 sends documents to another IS webMethods 8.2 (using the receiver’s preferred protocol) we obtain this log trace:

Task 5122q9008irf5ipc0001qm9h failed with no more retries available. Reason for failure - Delivery service for 5122q9008irf5ipc0001qm9h failed with a status of fail and status message of com.wm.app.b2b.server.ServiceException: java.net.SocketException: Connection reset

And then I reprocess the documents and they retransmit correctly. By the same time, other documents may transmit correctly too.

I can’t see what could cause the intermittend problem of connection… Any idea?

Thanks!

2

Is the URL/server you are trying is accessible with no issues (can you check more with your network team or IS logs for this intermittent pattern)…It’s completely an issue with the target server connection.

Also are the two IS’s installed on the same landscape/network LAN? Did you check with the network team as you are seeing intermittent socket issues and see if they can assist you in your testing?

Also what core SP fixes level are you up to on 8.2.2?

HTH,
RMG

3

Check the target server setting:
Settings > Resources >Session>Session timeout
make sure it’s long enough

Also check the From server setting:
Settings > Resources >Outbound HTTP Settings
timeout, try to increase it

Also, the network level issue can also be the reason.

4

Interesting… My Outbound HTTP Settings Timeout is zero. I’m going to increase it and see if it fix the problem. Thanks!

And a network guy is also investigating. I’ll let you know the conclusion…

5

Yes default is zero and try to increase it both places as mentioned below:

HTH,
RMG

6

Hello,

The Outbound HTTP Settings Timeout was increased on both sides, and the servers restarted, but it didn’t fix the problem.

…now waiting (and hoping) for the network guys…

Thanks for your replies.

7

Thanks for the update!..hope you will see the light end of the tunnel.

8

Seems the network connection is not persistent until the data handover

9

Thanks for your reply. The problem is still not resolved! I transmit your suggestion to the partner’s network guys…

10

if you can calling pub.client:http, you can set
newSession to yes, so for each document you will open a new session.
If you are not calling it directly. try server setting:

watt.server.new.http.session.context
Specifies whether Integration Server should create a new session object when executing
the pub.client:http service. When this property is set to true, Integration Server ignores the
values from the session object of the last invocation of pub.client:httpand creates a new
session object. When this property is set to false, Integration Server uses the values from
the existing session object. The default value is false.

11

Problem still not resolved… I tried the setting:
watt.server.new.http.session.context=true
as suggested by Tong Wang but I still have many documents with a failed transmission (connection reset, broken pipe, read timed out…).

12

Sorry to hear it not resolved…Lastly did you check with SAG support also and take advise?

HTH,
RMG