1 Reply Latest reply on Mar 21, 2007 11:02 AM by mskonda

    Queue configuration for application or for JBoss?

    Ziggy Stardust 995 Newbie

      This post has been deleted by the user. No longer applicable.

        • 1. Re: Queue configuration for application or for JBoss?
          mskonda Apprentice

          1.create a *-destination-service.xml file and deploy it under deploy directory with the followign example contents:

          <server>
           <loader-repository>
           jboss.messaging:loader=ScopedLoaderRepository
           <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
           </loader-repository>
          
           <!-- submit topic -->
          <mbean code="org.jboss.jms.server.destination.TopicService"
           name="jboss.messaging.destination:service=Topic,name=myTopic"
           xmbean-dd="xmdesc/Topic-xmbean.xml">
           <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
           <depends>jboss.messaging:service=PostOffice</depends>
           </mbean>
          </server>
          
          NOTE: if you want to deploy (or hot deploy) your destinations in deploy directory rather than deploy/jboss-messaging.sar directory, add the above scoping attribute <loader-repository>..</loader-repository>
          
          2. AFAIK, they are available for all applications, however, you can secure them. Team may give you an appropriate answer regarding this,
          
          3. Yes, you need to have a database for JMS persistence - default database that is bundled with JBoss and JBM is hypersonic which MUST be thrown away in non-dev environments. It's qutie easy to setup (replace Hypersonic). Remove hypersonic-persistence.xml and add one that suits you. Look for examples/config/*persistence.xml for few configs
          
          Thanks
          MAdhu