Nope, that's what I checked first. The point I'm at now, if I shutdown AS5 and replace the two libraries with the originals, the bridge will work (sending messages to a machine on a different subnet). If I then change to the libraries I built I get a host of errors which you can see in my previous posts.
Here'e my JMS-ds.xml (The IP Address of the machine this is deployed on is 172.16.66.230): | <?xml version="1.0" encoding="UTF-8"?> | | <connection-factories> | | <!-- ==================================================================== --> | <!-- JMS Stuff --> | <!-- ==================================================================== --> | | <!-- | The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to | be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available. | See http://jira.jboss.org/jira/browse/JBMESSAGING-843. | --> | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider"> | <attribute name="ProviderName">DefaultJMSProvider</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> | </mbean> | | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider"> | <attribute name="ProviderName">RemoteJMSProvider</attribute> | <attribute name="ProviderAdapterClass"> | org.jboss.jms.jndi.JNDIProviderAdapter | </attribute> | <attribute name="FactoryRef">/XAConnectionFactory</attribute> | <attribute name="QueueFactoryRef">/XAConnectionFactory</attribute> | <attribute name="TopicFactoryRef">/XAConnectionFactory</attribute> | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=jnp://172.16.8.52:1099 | </attribute> | </mbean> | | <!-- JMS XA Resource adapter, use this to get transacted JMS in beans --> | <tx-connection-factory> | <jndi-name>JmsXA</jndi-name> | <xa-transaction/> | <rar-name>jms-ra.rar</rar-name> | <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> | <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> | <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property> | <max-pool-size>20</max-pool-size> | <security-domain-and-application>JmsXARealm</security-domain-and-application> | <depends>jboss.messaging:service=ServerPeer</depends> | </tx-connection-factory> | | </connection-factories> | The only thing I can be sure of at the moment is that the new libraries I built do not work. Although I should point out that I have left the remote instance using the new libraries. It would be fairer to say that the new libraries do not work with bridges to remote locations. Another question if I might, why is jboss-messaging not tested against AS5? I will investigate this further tomorrow and supply anything further I find out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4207965#4207965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4207965 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
