Thanks Peter for the information. I think I'm getting closer, but I'm not
quite there yet.
I have this stanza in the jms-service.xml:
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=RemoteJBossMQProvider">
<attribute name="ProviderName">RemoteJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JBossMQProvider
</attribute>
<attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
<attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
<attribute name="ProviderUrl">remote.com:1099</attribute>
</mbean>
I have this is my jboss.xml for the MDB:
<?xml version="1.0"?>
<jboss>
<enterprise-beans>
<message-driven>
<ejb-name>TextQueueMDB</ejb-name>
<destination-jndi-name>queue/testQueue</destination-jndi-name>
<container-invoker-conf>
<JMSProviderAdapterJNDI>RemoteJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<Optimized>True</Optimized>
</container-invoker-conf>
</message-driven>
</enterprise-beans>
</jboss>
The MDB deploys just fine and I see the RemoteJMSProvider in the java:/
namespace, but no message is triggered in the MDB when I post a message to
the remote queue. So, I still am missing a piece to this puzzle somewhere.
Dustin
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 16, 2002 3:50 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] 3.2.x config for JBoss based remote JMS
> queues/t opics and MDB?
>
>
> You have to do advanced MDB configuration and include the complete
> cotainer config, in wich this is a part:
>
> <container-invoker-conf>
>
> <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
>
> <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFac
> toryJNDI>
> <MaximumSize>15</MaximumSize>
> <MaxMessages>1</MaxMessages>
> <Optimized>True</Optimized>
> </container-invoker-conf>
>
> Change Default... to your remote one.
>
> I do guess there other ways now to. I think I saw someone in the forum
> explain who he used the a JNDI helper class that's in JBoss to bind in
> an external context into the local JNDI. But you will have to
> configura
> either the default provider or a new one to get at the names of the
> factory.
>
> //Peter
-------------------------------------------------------
Sponsored by: AMD - Your access to the experts on Hammer Technology!
Open Source & Linux Developers, register now for the AMD Developer
Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
