3 Replies Latest reply on Apr 4, 2018 11:16 AM by Wolfgang Mayer

    oracle-jdbc2-service.xml in JBoss4.2.3 to Wildfly

    Nagaraju Chitimilla Newbie

      Hi All,

       

      We have the following oracle-jdbc2-service.xml file in jboss how can we migrate this file  to the wildfly. I couldn't find any document any this topic. Requesting some help on this.

       

       

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

      <!-- $Id: oracle-jdbc2-service.xml 57445 2006-10-05 13:20:43Z adrian@jboss.org $ -->

      <server>

         <!-- ==================================================================== -->

         <!-- Persistence and caching using Oracle                                 -->

         <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml                           -->

         <!-- ==================================================================== -->

         <!--

           | The destination manager is the core service within JBossMQ

        -->

         <mbean code="org.jboss.mq.server.jmx.DestinationManager" name="jboss.mq:service=DestinationManager">

            <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache</depends>

            <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager</depends>

            <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager</depends>

         </mbean>

         <!--

           | The MessageCache decides where to put JBossMQ message that

           | are sitting around waiting to be consumed by a client.

           |

           | The memory marks are in Megabytes.  Once the JVM memory usage hits

           | the high memory mark, the old messages in the cache will start getting

           | stored in the DataDirectory.  As memory usage gets closer to the

           | Max memory mark, the amount of message kept in the memory cache aproaches 0.

        -->

         <mbean code="org.jboss.mq.server.MessageCache" name="jboss.mq:service=MessageCache">

            <attribute name="HighMemoryMark">50</attribute>

            <attribute name="MaxMemoryMark">60</attribute>

            <attribute name="CacheStore">jboss.mq:service=PersistenceManager</attribute>

         </mbean>

         <!-- The PersistenceManager is used to store messages to disk. -->

         <!--

           | The jdbc2 PersistenceManager is the new improved JDBC implementation.

           | This implementation allows you to control how messages are stored in

           | the database.

           |

           | This jdbc2 PM configuration has been tested against Oracle

           |

           | Use the OracleThinPeristenceManager if you have the 4K limit problem for blobs

           | this uses the INSERT_EMPTY_BLOB and LOCK_EMPTY_BLOB before updating the row

           | with the real blob data to workaround that limit.

         -->

         <!--mbean code="org.jboss.mq.pm.jdbc2.OracleThinPersistenceManager" -->

         <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager" name="jboss.mq:service=PersistenceManager">

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

            <attribute name="SqlProperties">INSERT_EMPTY_BLOB = INSERT INTO JMS_MESSAGES (MESSAGEID, DESTINATION, MESSAGEBLOB, TXID, TXOP) VALUES(?,?,EMPTY_BLOB(),?,?)

            LOCK_EMPTY_BLOB = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID = ? AND DESTINATION = ? FOR UPDATE

            BLOB_TYPE=BINARYSTREAM_BLOB

            INSERT_TX = INSERT INTO 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 JMS_MESSAGES WHERE DESTINATION=?

            SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID FROM JMS_MESSAGES WHERE DESTINATION=?

            SELECT_MESSAGE = SELECT MESSAGEID, MESSAGEBLOB FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?

            MARK_MESSAGE = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE MESSAGEID=? AND DESTINATION=?

            UPDATE_MESSAGE = UPDATE JMS_MESSAGES SET MESSAGEBLOB=? WHERE MESSAGEID=? AND DESTINATION=?

            UPDATE_MARKED_MESSAGES = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=?

            UPDATE_MARKED_MESSAGES_WITH_TX = UPDATE JMS_MESSAGES SET TXID=?, TXOP=? WHERE TXOP=? AND TXID=?

            DELETE_MARKED_MESSAGES_WITH_TX = DELETE FROM JMS_MESSAGES MESS WHERE TXOP=? AND EXISTS (SELECT TXID FROM JMS_TRANSACTIONS TX WHERE TX.TXID = MESS.TXID)

            DELETE_TX = DELETE FROM JMS_TRANSACTIONS WHERE TXID = ?

            DELETE_MARKED_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXID=? AND TXOP=?

            DELETE_TEMPORARY_MESSAGES = DELETE FROM JMS_MESSAGES WHERE TXOP='T'

            DELETE_MESSAGE = DELETE FROM JMS_MESSAGES WHERE MESSAGEID=? AND DESTINATION=?

            CREATE_MESSAGE_TABLE = CREATE TABLE 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 JMS_MESSAGES (TXOP, TXID)

            CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX JMS_MESSAGES_DESTINATION ON JMS_MESSAGES (DESTINATION)

            CREATE_TX_TABLE = CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER, PRIMARY KEY (TXID) )

            CREATE_TABLES_ON_STARTUP = TRUE</attribute>

            <!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->

            <!--attribute name="RecoveryTimeout">0</attribute-->

            <!-- The number of blobs to load at once during message recovery -->

            <attribute name="RecoverMessagesChunk">0</attribute>

         </mbean>

      </server>

       

       

      Thanks  in advance

      Nagaraju