My remote-jms-ds.xml in the deploy/jms directory is very similar to what you suggest adding to jms-ds.xml, though I used the improved ProviderAdapterClass mentioned on the Wiki page.
<?xml version="1.0" encoding="UTF-8"?> | <!-- Provides a link to the remote JNDI service provider. --> | <server> | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.mq:service=JMSProviderLoader,name=RemoteJMSProvider,server=localhost"> | <!-- ProviderName specifies the default JNDI lookup name. --> | <attribute name="ProviderName">MyOutsideJMSProvider</attribute> | <attribute name="ProviderAdapterClass"> | org.jboss.jms.jndi.JNDIProviderAdapter | </attribute> | <attribute name="FactoryRef">java:/XAConnectionFactory</attribute> | <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute> | <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute> | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jnp.interfaces | java.naming.provider.url=localhost:1099 | </attribute> | </mbean> | </server> The snippet that I added to standardjboss.xml is: <invoker-proxy-binding> | <name>my-outside-mdb-invoker</name> | <invoker-mbean>does-not-matter</invoker-mbean> | <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> | <proxy-factory-config> | <JMSProviderAdapterJNDI>MyOutsideJMSProvider</JMSProviderAdapterJNDI> | <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> | <MinimumSize>1</MinimumSize> | <KeepAliveMillis>30000</KeepAliveMillis> | <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> The Wiki page is useful, and I actually followed it to get up and running initially. The strange part (to me, at least) is that this works as long as the MDB is deployed by itself, but not when it is in an EAR. Thanks again, Keith View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3901785#3901785 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3901785 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
