Looks like the broker is not starting. Do you see any exceptions in the Jboss log? A while ago, (see: https://issues.apache.org/activemq/browse/AMQ-2212) there was a fix for a classloading issue with the 5.2 resource adapter. It was found when using Websphere but it might affect Jboss as well.
-Gio On Wed, May 20, 2009 at 4:46 AM, flippo <[email protected]> wrote: > > A few months ago i integrated Apache ActiveMQ 4.1.2 with JBoss 4.0.5GA > which > worked fine for me. > My application could send messages to the queue's by using the > tcp://localhost:61616. > Now when I use almost the same configuration with the combination ActiveMQ > 5.2.0 and JBoss 5.0.1. GA > I can't connect to tcp://localhost:61616 anymore does anybody know the > problem? > > in the ra.xml : > > <config-property-name>ServerUrl</config-property-name> > <config-property-type>java.lang.String</config-property-type> > > > <!--<config-property-value><![CDATA[vm://localhost?create=false&async=false]]></config-property-value>--> > > <config-property-value>tcp://localhost:61616</config-property-value> > </config-property> > > borker.xml: > > <transportConnectors> > <transportConnector name="MT.broker" uri="tcp://localhost:61616" > discoveryUri="multicast://default"/> > > </transportConnectors> > > regards > -- > View this message in context: > http://www.nabble.com/Connecting-to-ActiveMQ-5.2.0-integrated-JBoss-5.0.1.-GA-tp23631384p23631384.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
