I'd suggest trying that, yes.. Tell me if how things went.
Best regards,
Kovi
At 08:54 23.5.01 +0200, you wrote:
>Just one message in unroutable@router2 (nothing to testqueue@router2).
>I am using 2.0.1.. do you think 2.1.0 would make a difference?
>thanks,
>Manjuka
>
>
>
>
>
>
>
>-----Original Message-----
>From: Gregor =?iso-8859-1?Q?Kova=E8?= [EMAIL PROTECTED]
>Sent: Wed, 23 May 2001 07:48:14 +0200
>To: [EMAIL PROTECTED]
>Subject: [developers] store and forward (continued..)
>
>
>Let me clear some things..
>
>You created a static route from router1 to router2.
>Then your client application connects to router1.
>You send ONE message to testqueue@router2.
>If router2 is up, you get that message from testqueue on router2.
>If router2 is not up you get TWO messages in roueter1's store.
>Now if you bring router2 up, do you get one message as expected and one in
>unroutable@rouer2 or just one message in unroutable@router2?
>
>Best regards,
> Kovi
>
>At 03:29 23.5.01 +0200, you wrote:
> >Hi,
> >Thanks for the responses.
> >I tried out the static router solution with the default setup. I created a
> >static route from router1 to router2,
> >and a test messages is sent to testqueue@router2 after connecting to
> router1.
> >As expected, everything works fine, and the message appears on
> >testqueue@router2, when both routers are up.
> >If I shut down router2 and try sending again, I don't get
> >the error anymore, and TWO messages appear in the rt$router2@router1
> >queue. But if I bring up router2 after that, the message doesn't go to
> >testqueue@router2. Instead,
> >it appears to go to unroutable@router2.
> >Can anyone tell me why that could happen?
> >thanks,
> >Manjuka
> >
> >
> >
> >-----Original Message-----
> >From: Gregor =?iso-8859-1?Q?Kova=E8?= [EMAIL PROTECTED]
> >Sent: Tue, 22 May 2001 09:18:39 +0200
> >To: [EMAIL PROTECTED]
> >Subject: [developers] store and forward (continued..)
> >
> >
> >Hi!
> >
> >In SwifMQ if you know that routers are going to get invisible to each other
> >it is good to define a static routes between them. That way you will not
> >get those errors.
> >I haven't used this, but I see in the API docs that you can create a
> >TopicSession that is transacted and thus you can use transactions with
> topics.
> >
> >Hope this helps.
> >Best regards,
> > Kovi
> >
> >
> >At 08:21 22.5.01 +0200, you wrote:
> > >Hi all,
> > >I am facing the same situation as someone else mentioned before. Having
> > >used MQSeries, I am familiar with the concept of a 'remote queue', which,
> > >in SwiftMQ parlance, is a queue in say router1 which 'represents' a queue
> > >(say testqueue2) in router2. So if you connect to router1 and send a
> > >message to that queue, it succeeds even if router2 is down at the time.
> > >The message stays in the remote queue, and gets forwarded.
> > >On the other hand, the send fails, with a 'No Such Queue' error.
> > >Just to confirm, is that feature getting any consideration of being
> > >implemented?
> > >Someone suggested to use Topics instead. But receiving messages from a
> > >Topic can not be done under transactional control (tell me if i am wrong).
> > >So, my question is, can SwiftMQ be used a robust, transactional messaging
> > >solution across an unreliable network (by which i mean routers can become
> > >invisible to eachother occasionally).
> > >thanks,
> > >Manjuka
> > >_______________________________________________________________________
> ____
> > >Visit http://www.visto.com/info, your free web-based communications
> center.
> > >Visto.com. Life on the Dot.
> > >
> > >
> > >------------------------------------------------------
> > >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/
> >
> >
> >
> >
> >
> >
> >
> >___________________________________________________________________________
> >Visit http://www.visto.com/info, your free web-based communications center.
> >Visto.com. Life on the Dot.
> >
> >
> >------------------------------------------------------
> >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/
>
>
>
>
>
>
>
>___________________________________________________________________________
>Visit http://www.visto.com/info, your free web-based communications center.
>Visto.com. Life on the Dot.
>
>
>------------------------------------------------------
>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/
