Re: [ebxmlms-general] RE: Hermes - repeated delivery attemptsLOOPING

[David W. \(XML\) <da...@dr...>]

Ladislav,

Good to know.

We are using Oracle app' server however, so no Tomcat for us ; -)

DW

----- Original Message ----- 
From: "Ladislav Urban" <lad...@we...>
To: <ebx...@li...>
Sent: Tuesday, November 08, 2005 12:35 PM
Subject: Re: [ebxmlms-general] RE: Hermes - repeated delivery
attemptsLOOPING


> Hello David,
> If there is still a problem with timeouts with http transport.
> There is a configuration file in Tomcat in conf directory server.xml
> In section Connector, attribute connectionTimeout in seconds. If there
> is not the attribute default value is used.
>
>
>
> <Connector className="org.apache.catalina.connector.http.HttpConnector"
>                port="19998" minProcessors="10" maxProcessors="200"
>                enableLookups="true" redirectPort="8447"
>                acceptCount="10" debug="0" connectionTimeout="1800000"/>
>
> PS
> We use hermes for large payloads too.
>
>
>
> On Fri, 2005-11-04 at 06:28 -0700, David RR Webber (XML) wrote:
> > OK - we resolved this - turns out the the Hermes config setting
> > in msh_client.properties..
> >
> > We resolved it by setting the time to 2mins (120000ms).
> >
> > For bigger payloads - if the delivery time internal is exceeded then
> > at the Hermes level (not the data handler) - then it will attempt to
> > retry the interchange of the transmission.
> >
> > DW
> >
> >
> >
> >
> >         -------- Original Message --------
> >         Subject: Hermes - repeated delivery attempts LOOPING
> >         From: "David RR Webber (XML)" <da...@dr...>
> >         Date: Thu, November 03, 2005 8:28 am
> >         To: eb
> >         Folks,
> >
> >         We suddenly encountered a problem over the last couple of days
> >         having deployed to a new test environment having made some
> >         enhancements to the Hermes <-> Hermes interfacing we are
> >         using.
> >
> >         What happens is that for some items delivery completes - and
> >         then a few minutes later - delivery repeats again, and then
> >         again, and so on.  We have to manually remove the offending
> >         transaction by setting its status to DELIVERED.
> >
> >         We are suspecting that the SOAP level ACKs are not quite
> >         correct in Apache - such that the server does not think it
> >         received the delivery cleanly even though it did.
> >
> >         Has anyone else experienced this?  Right now we are going to
> >         try just setting temporarily the reliable delivery 'false' -
> >         but we need a better solution!
> >
> >         Thanks, DW
> > ------------------------------------------------------- SF.Net email
> > is sponsored by: Tame your development challenges with Apache's
> > Geronimo App Server. Download it for free - -and be entered to win a
> > 42" plasma tv or your very own Sony(tm)PSP. Click here to play:
> > http://sourceforge.net/geronimo.php
> > _______________________________________________ ebxmlms-general
> > mailing list ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> -- 
> Ladislav Urban
> CEO
> Webswell Inc.
> 1333 Howe Avenue, Suite 100
> Sacramento, 95825 CA
> email: lad...@we...
> phone: +1 (916) 290-2040
> fax: +1 (916) 921-2850
> http://www.webswell.com
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> ebxmlms-general mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
>