The mbean definition of the remote provider can
go where you like in either a -service.xml or a -ds.xml,
the important thing is making the mbean name unique and
specifying the relevent url for the remote jnp naming.
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=Server1MQProvider">
<attribute name="ProviderName">Server1JMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JBossMQProvider
</attribute>
<attribute name="ProviderUrl">jnp://server1:1099</attribute>
<attribute
name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
<attribute
name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
</mbean>
You reference it on an invoker proxy binding in jboss.xml,
this delivers messages to the mdb:
<invoker-proxy-binding>
<name>server1-message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>Server1JMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
<message-driven>
<ejb-name>MyMessageBean</ejb-name>
<destination-jndi-name>queue/whatever</destination-jndi-name>
<invoker-bindings>
<invoker>
<invoker-proxy-binding-name>server1-message-driven-bean</invoker-proxy-binding-name>
</invoker>
</invoker-bindings>
</message-driven>
Regards,
Adrian
On Wed, 2003-12-10 at 23:41, Bruce Slawson wrote:
> On Dec 9, 2003, at 7:39 AM, Adrian Brock wrote:
>
>
> snip
>
>
> <excerpt>Completely separate from HA, it is possible to configure
>
> jboss's mdb to listen to multiple servers.
>
> You do this configuring multiple jms providers and then
>
> attaching an invoker proxy binding for each provider to
>
> the mdb.
>
> That way clients can send to any machine and the mdb will
>
> retrieve it. But this does not provide failover.
>
> e.g. If the client sends a message to a server that dies before
>
> the mdb retrieves it, you will have to wait until the server
>
> recovers before the mdb processes it.
>
>
> </excerpt>
>
> <color><param>0000,0000,0000</param>Adrian,
>
>
> This sounds like it might work for me in the short term. I have
> looked through the xml and have some confusion on how to do this.
>
>
> I know how to define invoker-proxy-bindings and specify them for the
> MDB in jboss.xml. I have always left the
> <<JMSProviderAdapterJNDI>DefaultJMSProvider<</JMSProviderAdapterJNDI>
> alone but I assume I need to specify it differently for the remote
> queue. I see in jms-ds.xml that <<attribute
> name="ProviderName">DefaultJMSProvider<</attribute> is defined. Do I
> need to create another jms-ds.xml that has a different ProviderName
> that somehow refers to the other server? Can you give me and example?
>
>
> Thanks,
>
> Bruce
>
> </color>
--
xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
