Hi Jan,
        What you are seeing is the JCA AdminObjects being created and bound 
into the JBoss JNDI tree. When you actually deploy an application with either a 
producer or a consumer (MDB, Servlet) etc, you will see the destinations being 
created on the Broker. Note, a good place to start is the JCA example code in 
the source tree. 

Regards,

Weston
On Sep 18, 2012, at 5:12 AM, Jan Bares <[email protected]> wrote:

> Hi,
> 
> When I place the following DS configuration to JBoss/ESB deploy folder, will 
> it automatically create the qpid queues? Even for clustered qpid? I am using 
> QPID 0.14.
> 
> Thanks, Jan
> 
> I can see that the JCA adapter was deployed
> ==================================
> 
> 2012-09-17 11:42:32,722 INFO  [org.apache.qpid.ra.QpidResourceAdapter] (main) 
> Qpid resource adapter started
> 
> And that the object were bound
> =========================
> 
> 2012-09-17 17:15:28,976 INFO  [org.jboss.resource.deployment.AdminObject] 
> (HDScanner) Bound admin object 
> 'org.apache.qpid.ra.admin.QpidDestinationProxy' at 'HelloQueue'
> 2012-09-17 17:15:28,992 INFO  
> [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] 
> (HDScanner) Bound ConnectionManager 
> 'jboss.jca:service=ConnectionFactoryBinding,name=QpidJMSXA' to JNDI name 
> 'java:QpidJMSXA'
> 2012-09-17 17:15:29,007 INFO  
> [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] 
> (HDScanner) Bound ConnectionManager 
> 'jboss.jca:service=ConnectionFactoryBinding,name=QpidJMS' to JNDI name 
> 'java:QpidJMS'
> 
> But qpid-stat does not show the queue
> ===============================
> 
> root@prgesb001 ~ # qpid-stat -q cluster/cluster@prgesb001
> Queues
>  queue                         dur  autoDel  excl  msg   msgIn  msgOut  bytes 
>  bytesIn  bytesOut  cons  bind
>  
> =============================================================================================================
>  reply-prgesb001.19721.1            Y        Y        0    61     61       0  
>  24.9k    24.9k        1     2
>  qmfc-v2-prgesb001.19721.1          Y        Y        0    11     11       0  
>  8.86k    8.86k        1     2
>  qmfc-v2-ui-prgesb001.19721.1       Y        Y        0     0      0       0  
>     0        0         1     1
>  topic-prgesb001.19721.1            Y        Y        0     0      0       0  
>     0        0         1     4
>  qmfc-v2-hb-prgesb001.19721.1       Y        Y        0     0      0       0  
>     0        0         1     2
> 
> Here is my qpid-jca-ds.xml
> ====================
> <?xml version="1.0" encoding="UTF-8"?>
> <!--
> Qpid JCA Resource Adapter: 
> https://svn.apache.org/repos/asf/qpid/trunk/qpid/java/jca/README-JBOSS.txt
> -->
> <connection-factories>
>  <!-- XA Connection Factory -->
>  <tx-connection-factory>
>    <jndi-name>QpidJMSXA</jndi-name>
>    <xa-transaction />
>    <rar-name>qpid-ra-0.14.rar</rar-name>
>    
> <connection-definition>org.apache.qpid.ra.QpidRAConnectionFactory</connection-definition>
>    <config-property 
> name="connectionURL">amqp://jboss:jboss@/jboss?brokerlist='tcp://prgesbclu:5672?sasl_mechs='PLAIN''</config-property>
>    <config-property name="SessionDefaultType" 
> type="java.lang.String">javax.jms.Queue</config-property>
>    <max-pool-size>20</max-pool-size>
>  </tx-connection-factory>
> 
>  <!-- Local Connection Factory -->
>  <tx-connection-factory>
>    <jndi-name>QpidJMS</jndi-name>
>    <rar-name>qpid-ra-0.14.rar</rar-name>
>    
> <connection-definition>org.apache.qpid.ra.QpidRAConnectionFactory</connection-definition>
>    <local-transaction/>
>    <config-property name="useLocalTx" 
> type="java.lang.Boolean">true</config-property>
>    <config-property 
> name="connectionURL">amqp://jboss:jboss@/jboss?brokerlist='tcp://prgesbclu:5672?sasl_mechs='PLAIN''</config-property>
>    <config-property name="SessionDefaultType" 
> type="java.lang.String">javax.jms.Queue</config-property>
>    <max-pool-size>20</max-pool-size>
>  </tx-connection-factory>
> 
>  <!-- ConnectionFactory that can be used outside of JBoss. Bound into global 
> JNDI namespace -->
>  <mbean code="org.jboss.resource.deployment.AdminObject" 
> name="qpid.jca:name=QpidConnectionFactory">
>    <attribute name="JNDIName">QpidConnectionFactory</attribute>
>    <depends 
> optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='qpid-ra-0.14.rar'</depends>
>    <attribute name="Type">javax.jms.ConnectionFactory</attribute>
>    <attribute name="Properties">
>        
> connectionURL=amqp://jboss:jboss@/jboss?brokerlist='tcp://prgesbclu:5672?sasl_mechs='PLAIN''
>    </attribute>
>  </mbean>
>       
>  <mbean code="org.jboss.resource.deployment.AdminObject" 
> name="qpid.jca:name=HelloQueue">
>     <attribute name="JNDIName">HelloQueue</attribute>
>     <depends 
> optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name='qpid-ra-0.14.rar'</depends>
>     <attribute name="Type">javax.jms.Destination</attribute>
>     <attribute name="Properties">
>        destinationType=QUEUE
>        destinationAddress=hello;{create:always, node:{type:queue, 
> x-declare:{auto-delete:true}}}
>     </attribute>
>  </mbean>
> </connection-factories>
> 
> 
> 
> 
> DISCLAIMER
> WOOD & Company Financial Services, a.s. and its branches are authorized and 
> regulated by the CNB as Home State regulator and in Poland by the KNF, in 
> Romania by the CNVM, in Slovakia by the NBS and in the UK by the FSA as Host 
> State regulators.  For further information about WOOD & Co., its investment 
> services, financial instruments and associated risks, safeguard client assets 
> (incl. compensation schemes) and contractual relationship please see our 
> website at www.wood.cz under section Corporate Governance. 
> 
> Unless otherwise stated, this transmission is neither an offer nor the 
> solicitation of an offer to sell or purchase any investment. All estimates, 
> opinions and other information contained herein are subject to change without 
> notice and are provided in good faith but without legal responsibility or 
> liability. Opinion may be personal to the author and may not reflect the 
> opinions of WOOD & Co. Communications from sales persons, sales traders or 
> traders should not be regarded as investment research and may contain 
> opinions or trading ideas which are different from WOOD & Co. investment  
> research opinions. 
> 
> This e-mail and any attachments are confidential and may be privileged or 
> otherwise protected from disclosure. If you are not a named addressee you 
> must not use, disclose, distribute, copy, print or rely on this e-mail and 
> any of its attachments. Please notify the sender that you have received this 
> email by mistake by replying to the email, and then delete the email and any 
> copies of it. Although WOOD & Co. routinely screens e-mails for viruses, 
> addressees should scan this e-mail and any attachments for viruses. WOOD & 
> Co. makes no representation or warranty as to the absence of viruses in this 
> e-mail or any attachments. Please note that to ensure regulatory compliance 
> and for the protection of our clients and business, we may monitor and read 
> e-mails sent to and from our server(s).
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to