> From: Gregor Kovač [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 09, 2001 11:37 PM
>
> The docs on JNDI remote queues say:"Optional property that specifies a
list
> of remote queue names. Every queue name has to be fully qualified with the
> remote routername as <queue>@<router>. In the case the specific remote
> router is disconnected, the local JNDI Swiftlet will return a Queue object
> on a JNDI lookup request of a client if that queue is defined in this
property."
> So it might be that your remote router is disconnected and then JNDI does
> not work, since JNDI lookups go to swiftmq.jndi topic and thus to all
> connected routers.
The real situation I am looking at is when the routers ARE connected. For
my primary queues, I have remote queues and aliases defined, so that things
will work even when the routers are not connected. But I also was trying to
have some simple queues and topics setup for testing (i.e. making sure the
router network is working properly). These queues are just for admins, and
the queue and router names will be known. Also, the routers will be
connected -- if they are not, I want things to fail so that it is clear the
routers are not connected.
But I think the JNDI is not my problem. After looking at the JNDI notes, I
(again) noted that the JNDI is implemented via topics. So I did a bit of
testing.
What I find is that my topic messages are not being sent between my two
routers. I have the same topic defined on both routers. Messages published
to the topic on one router are only received by subscribers on the same
router. This probably means that the JNDI messages (sent via topic
swiftmq.jndi) are not being sent between the routers, so the lookups are
only being seen by the local router. This would explain why I can't lookup
remote queues, even though the routers are connected.
Is there any known reasons the topics might not work between two routers,
even when the queues are working?
> But if you already know the full name of a queue(queue1@router1), why do
> you do a JNDI lookup, just use queueSession.createQueue("queue1@router1")
> to get a queue address..
Well, the JMS docs say that createQueue() should be avoided because it is
not portable...
> I hope this helps.
>
> Best regards,
> Kovi
>
> At 16:54 9.8.01 +0200, you wrote:
> >I don't know if I have my configuration wrong, or if things
> are working they
> >way they are suppose to.
> >
> >I have two routers, apps1 and pair (pair is an acronym --
> don't ask). Pair
> >has a connector to apps1, as well as a static route. Pair
> also has a JNDI
> >alias and remote queue setup for a queue on apps1 named orderCheck
> >(orderCheck@apps1).
>
> >When I send a message from pair to orderCheck@apps1,
> everything works fine.
> >But I cannot do a JNDI lookup on any other apps1 queues from
> pair (without
> >explicitly defining them as JNDI remote queues on pair).
> >
> >I thought that I would be able to do JNDI lookups for all
> remote queues,
> >without having to define them as remote queues, as long as
> their was an
> >active connection between the routers. Is this correct or not?
> >
> >Thanks for any insight anyone can provide.
> >
> >Geoffrey A. Lowney
------------------------------------------------------
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/
