RE: [ebxml-msg] EBMS0005 and EBMS0301

Makes sense to keep this implementation specific, or configurable in the best case…

 

Kr

 

Toon Vanhoutte

Integration Architect – Competence Manager – Microsoft Certified Trainer
|
Codit  

M
+32 479 90 51 15 
| 
 E


W
www.codit.eu 
| 
 Blog
blog.codit.eu  |
 www.integrationcloud.eu
               

 

From:  [mailto:]
On Behalf Of Makesh Rao (marao)

Sent: Monday, August 17, 2015 11:12 PM

To: Pim van der Eijk <>; 

Subject: Re: [ebxml-msg] EBMS0005 and EBMS0301

 

Hi Pim

 

I’d agree with Sander here. For the Missing Receipt error, we should atleast have delivered or gotten a 200/201. I think our implementation gives a EBMS0005 today
 for connection failures.

 

~Makesh

 

From:
"" on behalf of Pim van der Eijk

Date: Monday, August 17, 2015 at 1:57 PM

To: ""

Subject: Fwd: Re: [ebxml-msg] EBMS0005 and EBMS0301

 

 

-------- Forwarded Message -------- 

Subject: 

Re: [ebxml-msg] EBMS0005 and EBMS0301

Date: 

Mon, 17 Aug 2015 22:50:58 +0200

From: 

Sander Fieten <>

To: 

Pim Van Der Eijk, van der 
<>

Hi Pim, 

 

actually I think it does not matter much which of those errors is reported as both indicate failure of message delivery. I would say this is implementation specific.
 For the MissingReceipt error I can imagine that someone expects that the message is at least sent once to the receiving MSH and that the sending MSH is waiting for a receipt. So it could be a recommendation that this error is only generated after a successful
 send operation on the http level. 

Reporting both errors is the most clearly indication of what happened. 

 

But as said I would leave it up to the implementations to decide which error(s) to generate and report.

 

Regards

Sander

 

----

Sander Fieten

IT Architect

FIETEN IT

e: 

t:  +31 6 51507886

 

On 17 Aug 2015, at 19:45, Pim van der Eijk <> wrote:

 

Hi,

In case an AS4 gateway, with a PMode configured to use AS4 reception 

awareness and retries, attempts to send a message but, despite retries, 

does not succeed in doing so because of persistent HTTP connection 

failures,  it could generate errors, including the following:

-  an EBMS0005 (ConnectionFailure)

-  an EBMS0301 (MissingReceipt)

Which of the two do you think could, or should, be reported?  Only a 

EBMS0005, only a EBMS0301,  both or  none?

Are there any other error cases that you think could apply?

Kind regards,

Pim

---------------------------------------------------------------------

To unsubscribe from this mail list, you must leave the OASIS TC that 

generates this mail.  Follow this link to all your TCs in OASIS at:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php