4 Replies Latest reply on Nov 22, 2012 10:32 AM by ümit köse

    JMS Bridge from jboss4.2.3 to jboss as7

    ümit köse Newbie

      In my project I need to send JMS messages  from jboss 4.2.3 to remote jboss as 7 queue.I succeed to make work hornetq on jboss 4.x but it's not possible to send jms message to jboss as 7 because of class conflicts.Here a https://community.jboss.org/wiki/BridgeJMSMessagesFromAS5ToAS7 solution is suggested for jboss 5.x but it's not working for jboss 4.x.In the example there is a bridge sample but it's not for remote queues.

      First I want to be sure that it is possible and some guide would be very helpful.

       

      Thanks in advance.

        • 1. Re: JMS Bridge from jboss4.2.3 to jboss as7
          Justin Bertram Master

          Here a https://community.jboss.org/wiki/BridgeJMSMessagesFromAS5ToAS7 solution is suggested for jboss 5.x but it's not working for jboss 4.x.

          Any explanation as to why the bridge won't work?

          • 2. Re: JMS Bridge from jboss4.2.3 to jboss as7
            ümit köse Newbie

            It throws class not found exception for org.jboss.jms.server.bridge.BridgeService class.The class  not available both the jars on jboss as7 or jboss 4.x classes I think it's only available on jboss 5.x.

            • 3. Re: JMS Bridge from jboss4.2.3 to jboss as7
              Justin Bertram Master

              What JMS implementation are you using in your JBoss AS 4.2.3 instance?  If you are using JBoss Messaging then you should have org.jboss.jms.server.bridge.BridgeService (in jboss-messaging.jar).  If you are using JBossMQ then I think you're out of luck as it doesn't have any kind of bridge functionality.  Your best bet would be to deploy the HornetQ JCA RA to your JBoss AS 4.2.3 instance and use that to send messages.

              • 4. Re: JMS Bridge from jboss4.2.3 to jboss as7
                ümit köse Newbie

                I have installed hornetq.2.2.5 version to jboss.4.2.3 with some effort I made it to work.As you explained we can not use BridgeService class.Also I configured hornetq JCA resource adapter.But I could only connect to remote connection factory  not the queue.I could not lookup the remote queue because of protocol changes from jnp to remote and factory class is not available on the class path.

                Is it possible to bind remote queue to local JNDI with resourse adapters.

                Here is my configuration in jms-ds.xml

                <tx-connection-factory>

                      <jndi-name>RemoteJmsXA</jndi-name>

                      <xa-transaction/>

                      <username>guest</username>

                      <rar-name>hornetq-ra.rar</rar-name>

                      <connection-definition>org.hornetq.ra.HornetQRAConnectionFactory

                        </connection-definition>

                      <config-property name="SessionDefaultType" type="String">javax.jms.Queue</config-property>

                      <config-property name="ConnectorClassName" type="String">org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</config-property>

                      <config-property name="ConnectionParameters" type="String">host=localhost; port=5445</config-property>

                      <config-property>

                        <description>The user name used to login to the JMS server</description>

                        <config-property-name>UserName</config-property-name>

                        <config-property-type>java.lang.String</config-property-type>

                        <config-property-value>guest</config-property-value>

                      </config-property>

                      <config-property>

                        <description>The password used to login to the JMS server</description>

                        <config-property-name>Password</config-property-name>

                        <config-property-type>java.lang.String</config-property-type>

                        <config-property-value>guest</config-property-value>

                      </config-property>

                      <max-pool-size>20</max-pool-size>

                </tx-connection-factory>