2 Replies Latest reply on Nov 2, 2007 7:32 AM by Haagen Hasle

    Configuring JMS

    Haagen Hasle Novice

      I'm reading the Administration Guide, but I find it difficult to understand it all.. I'd like to edit my JMS-configuration.

      The documentation refers to the files "jbossesb-listener.xml" and "jbosseb-gateway.xml", that I can't find. I think I remember reading somewhere that these two files have been combined into jboss-esb.xml, is that correct?

      I would like to increase the size of the connection pool. The documentation refers to org.jboss.soa.esb.jms.connectionPool property in the transports section of the JBossESB configuration file. My jboss-esb.xml has no transport section that I am aware of.. Where is this supposed to be?

      I would also like to make my JMS queues non-persistent. I've found an attribute in the XSD for my jboss-esb.xml, that is meant to do this, the persistent="false" in the jms-message-filter tag. But when I try to use it, I get this:

      ERROR [XmlValidatorImpl] 2-ERROR-null-23:cvc-complex-type.3.2.2: Attribute 'persistent' is not allowed to appear in element 'jms-message-filter'.

      I tried to move it to the jms-bus tag, but that didn't help much either.. So how am I supposed to make mye JMS-queues non-persistent?

      Regards, Haagen

        • 1. Re: Configuring JMS
          Daniel Bevenius Master

          Hi Haagen,

          I've just tried this with the helloworld quickstart. I modified the jboss-esb.xml file to look like this:

          <jms-bus busid="quickstartGwChannel">
           <jms-message-filter
           dest-type="QUEUE"
           dest-name="queue/quickstart_helloworld_Request_gw"
           persistent="false"
           />
           </jms-bus>
           <jms-bus busid="quickstartEsbChannel">
           <jms-message-filter
           dest-type="QUEUE"
           dest-name="queue/quickstart_helloworld_Request_esb"
           persistent="false"
           />
           </jms-bus>
          


          If you run 'ant deploy' followed by 'ant runtest' and watch the servers console it should print out:
          11:05:08,353 INFO [STDOUT] [ message: [ JBOSS_XML ]
          header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/quickstart_helloworld_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : false/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-12294 RelatesTo: jms:correlationID#ID:JBM-13312 ]
          context: [ ]
          body: [ objects: {org.jboss.soa.esb.message.defaultEntry=Hello World, org.jboss.soa.esb.message.defaultEntry-set-stack=java.lang.Exception: setPayload stack trace for 'org.jboss.soa.esb.message.defaultEntry'.} ]
          fault: [ ]
          attachments: [ Named:{}, Unnamed:[] ]
          properties: [ {org.jboss.soa.esb.message.time.dod=Fri Nov 02 11:05:08 CET 2007, org.jboss.soa.esb.message.time.dob=Fri Nov 02 11:05:08 CET 2007, org.jboss.soa.esb.message.source=PortReference < jms://localhost/queue/quickstart_helloworld_Request_esb >, org.jboss.soa.esb.message.transport.type=JMS, org.jboss.soa.esb.gateway.original.queue.name=queue/quickstart_helloworld_Request_gw} ] ]
          


          I ran this with the esb server created by runnint 'ant dist' in the project folder of a checked out copy of the trunk. Could you try this?
          I might be the case that you have an older version of jbossesb-config-model.jar in you deploy/jbossesb.sar/lib directory.

          Regards,

          Daniel

          • 2. Re: Configuring JMS
            Haagen Hasle Novice

            It didn't work in 4.2GA, but I tried it again now, with 4.2.1GA, and it seems to work now! So that's great, one thing of my mind! :-)

            Thanks for your help!

            Regards, Haagen