Menu
▾
▴
Re: [ebxmlms-general] Hermes servlet problem
|
From: David RR W. \(XML\) <da...@dr...> - 2006-09-07 12:01:10
|
<div>If you read Patricks note carefully - it clearly says "do not recommend turning on" - which means its does work if you do - just that the results will depend on the SMTP setup you have.</div> <div> </div> <div>Most people using this have direct SMTP server setup - so delivery is not via WWW in-direct routing.</div> <div> </div> <div>DW<BR></div> <DIV id=wmMessageComp name="wmMessageComp"><BR><BR> <BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT: blue 2px solid">-------- Original Message --------<BR>Subject: Re: [ebxmlms-general] Hermes servlet problem<BR>From: "Arnstein Vestad" <ar...@ki...><BR>Date: Thu, September 07, 2006 4:03 am<BR>To: "General discussions" <ebx...@li...><BR><BR>>Torsten Kirschner<BR>>Sendt: 7. september 2006 08:17<BR>>Til: 'General discussions'<BR>>Emne: Re: [ebxmlms-general] [SPAM] - Hermes servlet problem<BR>-BayesianFilter >detected spam<BR><BR>>Hi Arnstein,<BR>><BR>>I think You might be wrong here. <BR>><BR>>Hermes1 does support reliable messaging, and if I recall correctly,<BR>this is<BR>>implemented in a transport-agnostic way. <BR>><BR>>Anyway, I have seen Hermes1 both send and receive acknowledgement<BR>messages,<BR>>as well as re-send messages if an acknowledgement was not received in<BR>time.<BR>>All over SMTP.<BR><BR>Well - we certainly couldn't get it working, and this is all very<BR>strange, as I had confirmation of the problem from the developers as<BR>well as an offer of paid consulting work to fix it:<BR><BR><BR>>>> -----Opprinnelig melding-----<BR>>>> Fra: Patrick Yee [mailto:kc...@ce...]<BR>>>> Sendt: 20. januar 2006 03:51<BR>>>> Til: Arnstein Vestad<BR>>>> Kopi: 'ope...@ce...'<BR>>>> Emne: Re: Smtp-fix for Hermes 1<BR>>>><BR>>>> Hi Arnstein,<BR>>>><BR>>>> Thanks for using Hermes.<BR>>>><BR>>>> We did not implement a complete acknowledgment mechanism on SMTP. <BR>>>> From our deployment experience, the time for using SMTP to transport<BR><BR>>>> ebXML message is not as predictable as the case we use HTTP. This is<BR><BR>>>> mainly due to the fact that SMTP is a connectionless protocol. In <BR>>>> our experiement which we tried to send ebXML message between two <BR>>>> Hermes installed in two different sites using SMTP, the messages may<BR><BR>>>> take days to travel from the sending server to the receiving one.<BR>>>><BR>>>> Given this behaviour, the reliability parameters cannot be set <BR>>>> properly. Our conclusion is then we do not encourage to turn on <BR>>>> reliable messaging (i.e. ack) when using SMTP.<BR>>>><BR>>>> So, will you consider to solve the reliablility requirement by using<BR><BR>>>> other workaround? e.g. to use a business message for synchronizing <BR>>>> the the status on both sides.<BR>>>><BR>>>><BR>>>> Regards,<BR>>>> Patrick Yee<BR>>>> Center for E-Commerce Infrastructure Development<BR>>>><BR>>>> Making E-Commerce Everyday Commerce<BR><BR><BR><BR><BR><BR>-------------------------------------------------------------------------<BR>Using Tomcat but need to do more? Need to support web services, security?<BR>Get stuff done quickly with pre-integrated technology to make your job easier<BR>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo<BR>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642<BR>_______________________________________________<BR>ebxmlms-general mailing list<BR>ebx...@li...<BR>https://lists.sourceforge.net/lists/listinfo/ebxmlms-general </BLOCKQUOTE></DIV> |
