Configuring BlazeDS destinations for ActiveMQ topics in JBOSS


i'm having trouble setting blazeds destinations activemq topics inside jboss. have tested activemq (in jboss) settings blazeds in external tomcat server. setup works fine integrated jboss environment doesn't work. guess jndi references in messaging-config file incorrect, not able figure out right config. ideas appreciated. : )<br /><br />here snippet of activemq-jms-ds.xml file (in /<jboss home>/server/default/deploy/):<br />...<br /><connection-factories><br />   <tx-connection-factory><br />      <jndi-name>activemq/topicconnectionfactory</jndi-name><br />      <xa-transaction/><br />      <track-connection-by-tx/><br />      <rar-name>activemq-ra.rar</rar-name><br />      <use-java-context>false</use-java-context><br />      <connection-definition>javax.jms.topicconnectionfactory</connection-definition><br />      <serverurl>vm://localhost</serverurl><br />      <min-pool-size>1</min-pool-size><br />      <max-pool-size>200</max-pool-size><br />      <blocking-timeout-millis>30000</blocking-timeout-millis><br />      <idle-timeout-minutes>3</idle-timeout-minutes><br />   </tx-connection-factory><br /><br />   <mbean code="org.jboss.resource.deployment.adminobject" name="activemq.topic:name=testtopic"><br />      <attribute name="jndiname">jms/testtopic</attribute><br />      <depends optional-attribute-name="rarname">jboss.jca:service=rardeployment,name='activemq-ra.rar'< /depends><br />      <attribute name="type">javax.jms.topic</attribute><br />      <attribute name="properties">physicalname=from.screen.testtopic</attribute><br />   </mbean><br />    ...<br />--------------------------------------------------<br />messaging-config.xml file<br />       ...<br />      <adapters><br />        <adapter-definition id="actionscript" class="flex.messaging.services.messaging.adapters.actionscriptadapter" default="true" /><br />        <adapter-definition id="jms" class="flex.messaging.services.messaging.adapters.jmsadapter" /><br />    </adapters><br /><br />    <destination id="tosupervisorscreen"><br />        <adapter ref="jms"/><br />        <properties><br />            <jms><br />                <destination-type>topic</destination-type><br />                <message-type>javax.jms.objectmessage</message-type><br />                <connection-factory>activemq/topicconnectionfactory</connection-factory><br />                <destination-jndi-name>jms/testtopic</destination-jndi-name><br />                <delivery-mode>non_persistent</delivery-mode><br />                <message-priority>default_priority</message-priority><br />                <preserve-jms-headers>"true"</preserve-jms-headers><br />                <acknowledge-mode>auto_acknowledge</acknowledge-mode><br />                <max-producers>1</max-producers><br />            </jms><br />        </properties><br />    </destination><br />    ...<br /><br />-----------------------------------

i've been able resolve issue, although i'm not quite sure understand how fully!! nevertheless, start , have have blazeds working within jboss , able communicate activemq built jboss! post on jboss wiki able find solution:<br />http://wiki.jboss.org/wiki/whatdoesthemessagedoyourownhousekeepingmean<br /><br />basically, turned off connection close checking in (/server/default/deploy/)jbossjca-service.xml (by setting debug false):<br /><br />  <mbean code="org.jboss.resource.connectionmanager.cachedconnectionmanager" <br />         name="jboss.jca:service=cachedconnectionmanager"><br />    <depends optional-attribute-name="transactionmanagerservicename">jboss:service=transactionmanager< /depends><br /><br />    <!-- enable connection close debug monitoring --><br />    <attribute name="debug">false</attribute><br /><br />not quite sure if bug in blazeds: there kind of connection leak that's not being caught, parhaps?


More discussions in Configuration and Getting Started


adobe

Comments

Popular posts from this blog

invalid use of void expresion in FlexiTimer2 library

error: a function-definition is not allowed here before '{' token

LED Strip Code