cancel
Showing results for 
Search instead for 
Did you mean: 

AS2 Seeburger Receiver channel error: java.net.SocketException: Connection

Former Member
0 Kudos

Dear Experts,

We are trying to establis a B2B AS2 connection with a Partner(outside the network).We have both inbound and outbound interfaces with this partner.Currently we are facing issues in the outbound flow:

The checks done till now.

1. Our compnay and partner have agreed upon AS2 ID's and Message Subjects.

2. The inbound flow is working. i.e Partner is able to send message to us and we are able to receive them successfully.

For the outbound flow also the partner is receiving the files, but PI channel monitoring and Seeburger workbench screens show the below error logs.

The channel error says

Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: java.net.SocketException: Connection reset # , SEEBURGER AS2: java.net.SocketException: Connection reset #

And Seerburger Workbench says "Error on Send, will be tried"

Status Description - Could not deliver as2 message to partner: java.net.SocketException: Connection reset # null

Please share your inputs/pointers to resolve this issue.

Thank you

Jack Krugmann.

Accepted Solutions (0)

Answers (7)

Answers (7)

nitingupta46
Discoverer
0 Kudos

Dear Jack,

Is your problem resolved? If yes how, we are also facing exactly same issue.

Merina1
Participant
0 Kudos

Dear Jack,

Are you also sending  message of huge size.  In my case the message with small payload is successfull.

Thank you.

Merina

Merina1
Participant
0 Kudos

Dear Experts,

I am also facing the same problem. The IDOC type is PROACT.

I had conducted  the below tests :

1. Small message size and MDN on :

    -the message was successful in PI

2. Large message size and MDN ON :

    - When  tested with large IDOC (48 MB) , the message reached partner but it was in Yellow status in PI    Seeburger work bench with the error "Could not deliver as2 message to partner: java.net.SocketException: Connection reset # null"

3. MDN off with small and large message size:

     - When we tested with large and small data keeping MDN settings OFF the message was successful in Seeburger work bench.


The partner has set correct MDN configurations at their end since it is working  for all other message type except  for PROACT.

Looking forward to hear from you on this.

Thank you .

Merina

Former Member
0 Kudos

you are sending SyncMDN - it shows successful delivery at partner site, but the responce is not able to reach at your side, check with details like proxy setting, firewall(as said above) , other security parameters.... It is sure that there are some authorization/authentication/security issue which is not allowing responce to enter at your system...

Edited by: Jackson on Dec 15, 2011 1:16 PM

Former Member
0 Kudos

Hi all,

Thanks for the initial response.

1. I have requested for the firewall logs from both the sides and the logs seem to be OK. No errors or issues have been observed in the firewall logs shared.

2. We are sending a Sync MDN but we are not receiving the response from the partner. But partner says he has sent out the MDN successfully, The logs have also been shared for this by the partner.

Any more inputs on this will highly be helpful to resolve the issue.

Thank you!!

Jack Krugmann

prateek
Active Contributor
0 Kudos

When you use Sync MDN, partner doesn't send any response. It is like an acknowledgement that the message is delivered to partner. What logs have the partner shared for Sync MDN? Can you share?

Regards,

Prateek Raj Srivastava

prateek
Active Contributor
0 Kudos

What type of MDN mode are you using while trying to send the message to partner? It appears that the message is sent but the MDN is not received successfully.

Regards,

Prateek Raj Srivastava

baskar_gopalakrishnan2
Active Contributor
0 Kudos

You might have firewall issue to transfer outbound message to the target system. You get connection reset error. Check with system admins or BASIS for this.