At 13:08 25.5.01 +0200, you wrote:
>A routing connection is initiated from the connector. If it can be
>established, the connections stays up. If it cannot be established, the
>connector does a retry in a specific retry interval. When there are
>messages for a remote destination which is down, the messages are handled
>in a store/forward manner. All what you have to define is a listener and a
>connector with a retry interval.
OK. On the router that has connectors defined I do have everything you told
me.
But I'm more concerned about the remote router (the router that a
connection points to). If a connection is down will that router be able to
establish a connection, despite the fact that it does not have a connector
to the first router defined?
Bst regards,
Kovi
>Dial-on-demand of ISDN routers are TCP packet driven. If a packet arrives
>for a remote route, the ISDN router dials and establishes an ISDN
>connection. After some time of idling the dial-up connection usually times
>out and goes down until the next packet arrives. When you have an active
>routing connection but no traffic on it then you have no packets to
>transfer, hence, your ISDN dial-up connection is down until there is a
>message to transfer on the routing connection.
>
>--
>Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
>SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
>
>
>-----Original Message-----
>From: Gregor Kovač <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Date: Fri, 25 May 2001 12:40:29 +0200
>Subject: [developers] Keep-alive time
>
> >
> > OK, if I set this up and when both establish connection the messages
> > will
> > flow from one router to another, that's ok.
> > But what if the connection is closed?
> > Will it be reopened only when there is something to transfer from one
> > router to another?
> > Who is responsible for opening connections?
> >
> > If I have a routers SERVER and CLIENT and CLIENT has a routing listener
> > and
> > SERVER has a connection to CLIENT under connectors.
> > Will they be able to reopen the connection if it is closed, by an ISDN
> > router, ... ?
> > If SERVER has something to transfer to CLIENT it will be able to open
> > the
> > connection to CLIENT, because it has the connection defined, right?
> > But what if a CLIENT wants to transfer something to SERVER and the
> > connection is not up? Will it be able to open it, because it does not
> > have
> > a connection to SERVER defined ?
> >
> > Best regards,
> > Kovi
> >
> > At 12:00 25.5.01 +0200, you wrote:
> > >You define it only for the routing listener. It is handed over to the
> > >connector during the connect prologue phase.
> > >
> > >--
> > >Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
> > >SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
> > >
> > >
> > >-----Original Message-----
> > >From: Gregor Kovač <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Date: Fri, 25 May 2001 12:02:34 +0200
> > >Subject: [developers] Keep-alive time
> > >
> > > > OK.. This is my final (I hope) question on this topic. :))
> > > >
> > > > Just to make it clear:
> > > > I have to set that property only on the router where I have
> > connectors
> > > > defined or on both ends?
> > > >
> > > > Best regards,
> > > > Kovi
> > > >
> > > > At 11:50 25.5.01 +0200, you wrote:
> > > > > > Hmm...
> > > > > >
> > > > > > OK.. So if a routing connection on a dial-up lines is not
> > > > recommended,
> > > > > > how
> > > > > > can I connect the two routers together ?
> > > > > > Or is
> > > > > > setting
> > > > swiftlet.sys$routing.listeners.plainsocket.keepalive.interval
> > > > > > to 0
> > > > > > enough ?
> > > > >
> > > > >Sure, you can switch it simply off (sometimes I'm blind, thinking
> > of
> > > > >half-open socket issues etc. instead of the simplest solutions).
> > > > >
> > > > >--
> > > > >Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
> > > > >SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
> > > > >
> > > > >
> > > > >------------------------------------------------------
> > > > >SwiftMQ developers mailing list * http://www.swiftmq.com
> > > > >To unsubscribe from this list, send an eMail to
> > > > >[EMAIL PROTECTED] and write in the body of your message:
> > > > >UNSUBSCRIBE developers <your-email-address>
> > > > >Archive: http://www.mail-archive.com/developers@mail.iit.de/
> > > >
> > > >
> > > > ------------------------------------------------------
> > > > SwiftMQ developers mailing list * http://www.swiftmq.com
> > > > To unsubscribe from this list, send an eMail to
> > > > [EMAIL PROTECTED] and write in the body of your message:
> > > > UNSUBSCRIBE developers <your-email-address>
> > > > Archive: http://www.mail-archive.com/developers@mail.iit.de/
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >------------------------------------------------------
> > >SwiftMQ developers mailing list * http://www.swiftmq.com
> > >To unsubscribe from this list, send an eMail to
> > >[EMAIL PROTECTED] and write in the body of your message:
> > >UNSUBSCRIBE developers <your-email-address>
> > >Archive: http://www.mail-archive.com/developers@mail.iit.de/
> >
> >
> > ------------------------------------------------------
> > SwiftMQ developers mailing list * http://www.swiftmq.com
> > To unsubscribe from this list, send an eMail to
> > [EMAIL PROTECTED] and write in the body of your message:
> > UNSUBSCRIBE developers <your-email-address>
> > Archive: http://www.mail-archive.com/developers@mail.iit.de/
> >
> >
> >
> >
>
>
>------------------------------------------------------
>SwiftMQ developers mailing list * http://www.swiftmq.com
>To unsubscribe from this list, send an eMail to
>[EMAIL PROTECTED] and write in the body of your message:
>UNSUBSCRIBE developers <your-email-address>
>Archive: http://www.mail-archive.com/developers@mail.iit.de/
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
