4 Replies Latest reply on Nov 25, 2003 10:33 AM by ccricklin

    How to configure a persistent topic?

    ccricklin

      Hi,
      I've configured a JMS topic in JBoss 3.2.2 and used a simple client to publish some PERSISTENT messages to it. I also wrote a MDB to consume those messages. So far, everything was working fine.

      To test if the published messages could be "persistently" stored in a datasource (I've configured a MySQL database for this purpose), I took out the MDB and tried again. However, I didn't see any published messages had been inserted into jms_transactions table.

      I am not sure where went wrong. Do I have the wrong idea about this "persistent topic" concept?

      Please help,
      Thanks,
      Rick

        • 1. Re: How to configure a persistent topic?
          pvamstel

          If messages are consumed they are gone.

          They are only persisten as long as not all listeners have recieved the messages.

          • 2. Re: How to configure a persistent topic?
            ccricklin

            Thank you,
            But, I did take out the MDB, which is my only listener, and tried. I still didn't see the published messages been stored into the database.

            Thanks,

            • 3. Re: How to configure a persistent topic?
              pvamstel

              You have to add a ???-service.xml in the $jboss/server/default/deploy/jms

              And the file is something like

              <?xml version="1.0" encoding="UTF-8"?>


              <!-- Destination without a configured SecurityManager or without a
              a SecurityConf will default to role guest with read=true, write=true,
              create=false.
              -->

              <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
              <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager









              • 4. Re: How to configure a persistent topic?
                ccricklin

                Yes, I do have jbossmq-destinations-service.xml in $JBOSS/server/default/deploy/jms. And, the file has:

                ...

                ...

                <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
                <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager









                ...