Incomplete QueueConnectionFactory through admin-console
rafaelri Sep 11, 2009 8:50 AMHi all,
I am doing some tests on JBoss 5.1 in order to begin a new project.
Recently I've been playing with application clients after following Wolfgang tips documented on:
http://www.jboss.org/community/wiki/HowtouseanapplicationclientinJBoss-5
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=143595
http://www.cs.hs-rm.de/~knauf/KomponentenArchitekturen2008/mdb/index.html
My problems started when I wanted to have the QueueConnectionFactory and Queue configured as Global configuration suggested in the last url.
I tried to configure it using the new JBoss Admin Console but everytime I tried switching from the builtin JMS "ConnectionFactory" I got exceptions complaining that my connection factory wasn't bound.
After some research I found that the issue was related to a missing tag (or a complete file) with the following contents for the connection factory that I had just created:
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory" name="jboss.messaging.connectionfactory:service=conexaoFilaTeste" xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml"> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends> <depends>jboss.messaging:service=PostOffice</depends> <attribute name="JNDIBindings"> <bindings> <binding>/conexaoFilaTeste</binding> <binding>java:/conexaoFilaTeste</binding> </bindings> </attribute> </mbean>
Everytime I created a ConnectionFactory using Admin Console JBoss was only creating a "-ds.xml" file with the following contents:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <connection-factories> <tx-connection-factory> <jndi-name>conexaoFilaTeste</jndi-name> <rar-name>jms-ra.rar</rar-name> <use-java-context>true</use-java-context> <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> <jmx-invoker-name>jboss:service=invoker,type=jrmp</jmx-invoker-name> <min-pool-size>0</min-pool-size> <max-pool-size>10</max-pool-size> <blocking-timeout-millis>30000</blocking-timeout-millis> <idle-timeout-minutes>30</idle-timeout-minutes> <prefill>false</prefill> <background-validation>false</background-validation> <background-validation-millis>0</background-validation-millis> <validate-on-match>true</validate-on-match> <statistics-formatter>org.jboss.resource.statistic.pool.JBossDefaultSubPoolStatisticFormatter</statistics-formatter> <isSameRM-override-value>false</isSameRM-override-value> <allocation-retry>0</allocation-retry> <allocation-retry-wait-millis>5000</allocation-retry-wait-millis> <application-managed-security xsi:type="securityMetaData" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> <metadata/> <xa-resource-timeout>0</xa-resource-timeout> </tx-connection-factory> </connection-factories>
Is it the expected behaviour or Admin Console is skipping an important part of the connection factory creation?
best regards,
Rafael Ribeiro
P.S.: I had originally posted this into JBoss AS forum http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4254652