RE: [JBoss-user] How to access remote JMS queues???

[Adrian B. <ad...@jb...>]

Answers in line,

Regards,
Adrian

> -----Original Message-----
> From: jbo...@li... 
> [mailto:jbo...@li...] On Behalf Of 
> dav...@bt...
> Sent: 09 May 2003 15:11
> To: jbo...@li...
> Subject: [JBoss-user] How to access remote JMS queues???
> 
> 
> 
> Hi,
> 
> We have a JMS/MQ problem - We want client components (EJBs 
> and others) in
> JBoss server X to send JMS messages to a queue 'hosted' on 
> JBoss server Y.
> 
> Surely, our components on server X don't have to lookup the  
> queue on server
> Y by JNDI and call on it remotely? 

It is possible to bring part of Y's JNDI into X
using the external context mbean.

> 
> Surely JMS can distribute the queue to server X such that the queue
> *appears* to the components on server X to be available  
> locally, 'running'
> on server X. I imagine that you configure the queue such that 
>  JMS 'extends'
> the queue out from server Y to server X such that components 
> on server X can
> access it 'locally'. Furthermore, I would expect the server X 
> JMS queue
> support components to handle persistence etc. so that messages can be
> dropped to the queue even when server Y is down.
>  
> Am I right in this? I've looked in two books and several web 
> sites (Sun,
> JBoss) and can't find any solid evidence of this, let along  
> how to set it
> up.

First the queue/destination you talk to, depends upon
the connection factory and the destination.
The queue and topic objects are just names.
To do real work you must tie them together
using a sender or receiver.

JBossMQ does not support what you are trying to
achieve. 

It would be possible to write something (an Mbean in jboss) that
receives from a queue on Y and sends to a queue
on X. 
This would require two connections/sessions to the different
machines.
Make sure you are using two phase commit (XA) and the
sessions' XAResources are enlisted in the same
tranaction.

You can use ExceptionListener(s) to handle connection
failures and retries. 
This would make it difficult to write as an MDB,
potentially you have two connections that can fail,
one is under the control of the MDB's container.

>  
> I'm hoping JMS will just take away all these 'distribution' 
> problems. Or
> does the JNDI lookup download a topic object that actually 
> does do all that
> stuff invisibly??

See above, the destination objects are just identifiers.

> 
> Any help much appreciated,
> Cheers,
> Dave
> 
> 
> ----------------------------
> Dave Roxburgh
> BTexact Technologies
> 
> e-mail: dav...@bt...
> tel: +44(0) 1473 647119
> B54/125B, Adastral Park, Martlesham, Ipswich IP5 3RE, UK
> 
> BTexact Technologies is a trademark of British 
> Telecommunications plc |
> Registered office: 81 Newgate Street London EC1A 7AJ | 
> Registered in England
> no. 1800000 | This electronic message contains information 
> from British
> Telecommunications plc which may be privileged or confidential. The
> information is intended to be for the use of the 
> individual(s) or entity
> named above. If you are not the intended recipient be aware that any
> disclosure, copying, distribution or use of the contents of 
> this information
> is prohibited. If you have received this electronic message 
> in error, please
> notify us by telephone or email (to the numbers or address above)
> immediately.
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux 
> enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> JBoss-user mailing list
> JBo...@li...
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>