1 Reply Latest reply on Nov 1, 2006 5:21 AM by jarvis

    whether can config two types Queue in one JBoss?

    jarvis

      Whether can config two types queue in per JBoss instence? One queue type is cache, the other is persistence into DB. if it can, can you give us some advices? thanks

        • 1. Re: whether can config two types Queue in one JBoss?
          jarvis

          reply myself:
          this only chages two files---jbossmq-destinations-service.xml as


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

          and null-persistence-service.xml as add these codes


          <!-- An optional delegate for real persistence of some destinations e.g. jdbc2 -->
          <depends optional-attribute-name="DelegatePM">jboss.mq:service=SomePersistenceManager



          <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DefaultDB

          BLOB_TYPE=BINARYSTREAM_BLOB
          INSERT_TX = INSERT INTO ALLHOTDB.JMS_TRANSACTIONS (TXID) values(?)
          INSERT_MESSAGE = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,?,?,?)
          SELECT_ALL_UNCOMMITED_TXS = SELECT TXID FROM JMS_TRANSACTIONS
          SELECT_MAX_TX = SELECT MAX(TXID) FROM (SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM JMS_MESSAGES)
          DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS
          SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB FROM ALLHOTDB.JMS_MESSAGES WHERE DESTINATION=?
          SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM ALLHOTDB.JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
          MARK_MESSAGE = UPDATE ALLHOTDB.JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?
          UPDATE_MESSAGE = UPDATE ALLHOTDB.JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?
          UPDATE_MARKED_MESSAGES = UPDATE ALLHOTDB.JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?
          UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE ALLHOTDB.JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?
          DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM ALLHOTDB.JMS_MESSAGES MESS WHERE TXOP=:1 AND EXISTS (SELECT TXID FROM ALLHOTDB.JMS_TRANSACTIONS TX WHERE TX.TXID = MESS.TXID)
          DELETE_TX = DELETE FROM ALLHOTDB.JMS_TRANSACTIONS WHERE TXID = ?
          DELETE_MARKED_MESSAGES = DELETE FROM ALLHOTDB.JMS_MESSAGES WHERE TXID=? AND TXOP=?
          DELETE_TEMPORARY_MESSAGES = DELETE FROM ALLHOTDB.JMS_MESSAGES WHERE TXOP='T'
          DELETE_MESSAGE = DELETE FROM ALLHOTDB.JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?
          CREATE_MESSAGE_TABLE = CREATE TABLE ALLHOTDB.JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \
          DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \
          MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) )
          CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX JMS_MESSAGES_TXOP_TXID ON ALLHOTDB.JMS_MESSAGES (TXOP, TXID)
          CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON ALLHOTDB.JMS_MESSAGES (DESTINATION)
          CREATE_TX_TABLE = CREATE TABLE ALLHOTDB.JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )
          CREATE_TABLES_ON_STARTUP = FALSE

          <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
          <!--attribute name="RecoveryTimeout">0</attribute-->