1 Reply Latest reply on Aug 21, 2006 1:33 PM by Ovidiu Feodorov

    RC3 stable? which jdk? ad on: mssql-persistence-service.xml

    Josef Newbie

      hello,

      we are using
      jboss-4.0.4.GA
      win xp sp2
      Microsoft SQL Server 2000 - 8.00.760
      jboss-messaging-1.0.1.CR3 and it works fine for us.

      now the questions:

      1.
      we run jboss-4.0.4.GA (install: jboss-4.0.4.GA-Patch1-installer.jar default)
      under jdk1.5.0_07 (jdk-1_5_0_07-windows-i586-p.exe; build 1.5.0._07-b03)
      is this the right jdk?

      2.
      is it a good idea to use jboss-messaging-1.0.1.CR3 in a production environment?

      3.
      what content will have the destinations-service.xml in a production environment?

      4.
      when will the first jboss-messaging-x.y production release be available?

      5.
      some benefit: following, is my "mssql-persistence-service.xml"; all tests passed :-)
      please check the file and reply when there are things wrong!


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



      <mbean code="org.jboss.messaging.core.plugin.JDBCPersistenceManager"
      name="jboss.messaging:service=PersistenceManager"
      xmbean-dd="xmdesc/JDBCPersistenceManager-xmbean.xml">
      jboss.jca:service=DataSourceBinding,name=LPDS
      <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager
      <depends optional-attribute-name="ChannelMapper">jboss.messaging:service=ChannelMapper
      java:/LPDS
      true
      true
      <![CDATA[
      CREATE_MESSAGE_REF=CREATE TABLE JMS_MESSAGE_REFERENCE (CHANNELID BIGINT, MESSAGEID BIGINT, TRANSACTIONID BIGINT, STATE CHAR(1), ORD BIGINT, DELIVERYCOUNT BIGINT, RELIABLE CHAR(1), LOADED CHAR(1), PRIMARY KEY(CHANNELID, MESSAGEID))
      CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JMS_MESSAGE_REF_TX ON JMS_MESSAGE_REFERENCE (TRANSACTIONID)
      CREATE_IDX_MESSAGE_REF_ORD=CREATE INDEX JMS_MESSAGE_REF_ORD ON JMS_MESSAGE_REFERENCE (ORD)
      CREATE_IDX_MESSAGE_REF_MESSAGEID=CREATE INDEX JMS_MESSAGE_REF_MESSAGEID ON JMS_MESSAGE_REFERENCE (MESSAGEID)
      CREATE_IDX_MESSAGE_REF_LOADED=CREATE INDEX JMS_MESSAGE_REF_LOADED ON JMS_MESSAGE_REFERENCE (LOADED)
      CREATE_IDX_MESSAGE_REF_RELIABLE=CREATE INDEX JMS_MESSAGE_REF_RELIABLE ON JMS_MESSAGE_REFERENCE (RELIABLE)
      INSERT_MESSAGE_REF=INSERT INTO JMS_MESSAGE_REFERENCE (CHANNELID, MESSAGEID, TRANSACTIONID, STATE, ORD, DELIVERYCOUNT, RELIABLE, LOADED) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
      DELETE_MESSAGE_REF=DELETE FROM JMS_MESSAGE_REFERENCE WHERE MESSAGEID=? AND CHANNELID=? AND STATE='C'
      UPDATE_MESSAGE_REF=UPDATE JMS_MESSAGE_REFERENCE SET TRANSACTIONID=?, STATE='-' WHERE MESSAGEID=? AND CHANNELID=? AND STATE='C'
      UPDATE_MESSAGE_REF_NOT_LOADED=UPDATE JMS_MESSAGE_REFERENCE SET LOADED='N' WHERE MESSAGEID=? AND CHANNELID=?
      COMMIT_MESSAGE_REF1=UPDATE JMS_MESSAGE_REFERENCE SET STATE='C', TRANSACTIONID = NULL WHERE TRANSACTIONID=? AND STATE='+'
      COMMIT_MESSAGE_REF2=DELETE FROM JMS_MESSAGE_REFERENCE WHERE TRANSACTIONID=? AND STATE='-'
      ROLLBACK_MESSAGE_REF1=DELETE FROM JMS_MESSAGE_REFERENCE WHERE TRANSACTIONID=? AND STATE='+'
      ROLLBACK_MESSAGE_REF2=UPDATE JMS_MESSAGE_REFERENCE SET STATE='C', TRANSACTIONID = NULL WHERE TRANSACTIONID=? AND STATE='-'
      LOAD_REF_INFO=SELECT MESSAGEID, ORD, DELIVERYCOUNT FROM JMS_MESSAGE_REFERENCE WHERE CHANNELID=? AND STATE <> '+' AND LOADED = 'N' AND ORD BETWEEN ? AND ? ORDER BY ORD
      SELECT_COUNT_REFS=SELECT COUNT(MESSAGEID) FROM JMS_MESSAGE_REFERENCE WHERE CHANNELID=? AND STATE <> '+' AND LOADED='N'
      UPDATE_RELIABLE_REFS=UPDATE JMS_MESSAGE_REFERENCE SET LOADED='Y' WHERE ORD BETWEEN ? AND ? AND CHANNELID=? AND RELIABLE='Y' AND STATE <> '+'
      DELETE_CHANNEL_MESSAGE_REFS=DELETE FROM JMS_MESSAGE_REFERENCE WHERE CHANNELID=?
      REMOVE_ALL_NONRELIABLE_REFS=DELETE FROM JMS_MESSAGE_REFERENCE WHERE RELIABLE='N'
      UPDATE_ALL_RELIABLE_REFS=UPDATE JMS_MESSAGE_REFERENCE SET LOADED='N'
      SELECT_MIN_ORDERING=SELECT MIN(ORD) FROM JMS_MESSAGE_REFERENCE WHERE CHANNELID=? AND STATE <> '+' AND LOADED = 'N'
      DELETE_NON_DURABLE=DELETE FROM JMS_MESSAGE_REFERENCE WHERE CHANNELID NOT IN (SELECT ID FROM JMS_CHANNEL_MAPPING)
      CREATE_MESSAGE=CREATE TABLE JMS_MESSAGE (MESSAGEID BIGINT, RELIABLE CHAR(1), EXPIRATION BIGINT, TIMESTAMP BIGINT, PRIORITY BIGINT, COREHEADERS IMAGE, PAYLOAD IMAGE, CHANNELCOUNT BIGINT, TYPE BIGINT, JMSTYPE NVARCHAR(255), CORRELATIONID NVARCHAR(255), CORRELATIONID_BYTES VARBINARY(254), DESTINATION_ID BIGINT, REPLYTO_ID BIGINT, JMSPROPERTIES IMAGE, PRIMARY KEY (MESSAGEID))
      LOAD_MESSAGES=SELECT MESSAGEID, RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, COREHEADERS, PAYLOAD, CHANNELCOUNT, TYPE, JMSTYPE, CORRELATIONID, CORRELATIONID_BYTES, DESTINATION_ID, REPLYTO_ID, JMSPROPERTIES FROM JMS_MESSAGE
      INSERT_MESSAGE=INSERT INTO JMS_MESSAGE (MESSAGEID, RELIABLE, EXPIRATION, TIMESTAMP, PRIORITY, COREHEADERS, PAYLOAD, CHANNELCOUNT, TYPE, JMSTYPE, CORRELATIONID, CORRELATIONID_BYTES, DESTINATION_ID, REPLYTO_ID, JMSPROPERTIES) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
      UPDATE_MESSAGE_CHANNEL_COUNT=UPDATE JMS_MESSAGE SET CHANNELCOUNT=? WHERE MESSAGEID=?
      DELETE_MESSAGE=DELETE FROM JMS_MESSAGE WHERE MESSAGEID=?
      MESSAGE_ID_COLUMN=MESSAGEID
      REMOVE_ALL_NONRELIABLE_MSGS=DELETE FROM JMS_MESSAGE WHERE RELIABLE='N'
      DELETE_ALL_MESSAGES=DELETE FROM JMS_MESSAGE
      CREATE_TRANSACTION=CREATE TABLE JMS_TRANSACTION (TRANSACTIONID BIGINT, BRANCH_QUAL VARBINARY(254), FORMAT_ID BIGINT, GLOBAL_TXID VARBINARY(254), PRIMARY KEY (TRANSACTIONID))
      INSERT_TRANSACTION=INSERT INTO JMS_TRANSACTION (TRANSACTIONID, BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID) VALUES(?, ?, ?, ?)
      DELETE_TRANSACTION=DELETE FROM JMS_TRANSACTION WHERE TRANSACTIONID = ?
      SELECT_PREPARED_TRANSACTIONS=SELECT TRANSACTIONID, BRANCH_QUAL, FORMAT_ID, GLOBAL_TXID FROM JMS_TRANSACTION
      DELETE_ALL_TRANSACTIONS=DELETE FROM JMS_TRANSACTION
      CREATE_COUNTER=CREATE TABLE JMS_COUNTER (NAME NVARCHAR(255), NEXT_ID BIGINT, PRIMARY KEY(NAME))
      UPDATE_COUNTER=UPDATE JMS_COUNTER SET NEXT_ID = ? WHERE NAME=?
      SELECT_COUNTER=SELECT NEXT_ID FROM JMS_COUNTER WHERE NAME=?
      INSERT_COUNTER=INSERT INTO JMS_COUNTER (NAME, NEXT_ID) VALUES (?, ?)
      DELETE_ALL_COUNTERS=DELETE FROM JMS_COUNTER
      ]]>
      500


      <mbean code="org.jboss.jms.server.plugin.JDBCChannelMapper"
      name="jboss.messaging:service=ChannelMapper"
      xmbean-dd="xmdesc/JDBCChannelMapper-xmbean.xml">
      jboss.jca:service=DataSourceBinding,name=LPDS
      <depends optional-attribute-name="TransactionManager">jboss:service=TransactionManager
      java:/LPDS
      <![CDATA[
      CREATE_USER_TABLE=CREATE TABLE JMS_USER (USERID NVARCHAR(32) NOT NULL, PASSWD NVARCHAR(32) NOT NULL, CLIENTID NVARCHAR(128), PRIMARY KEY(USERID))
      CREATE_ROLE_TABLE=CREATE TABLE JMS_ROLE (ROLEID NVARCHAR(32) NOT NULL, USERID NVARCHAR(32) NOT NULL, PRIMARY KEY(USERID, ROLEID))
      SELECT_PRECONF_CLIENTID=SELECT CLIENTID FROM JMS_USER WHERE USERID=?
      CREATE_MAPPING_TABLE=CREATE TABLE JMS_CHANNEL_MAPPING (ID BIGINT, TYPE CHAR(1), JMS_DEST_NAME NVARCHAR(1024), JMS_SUB_NAME NVARCHAR(1024), CLIENT_ID NVARCHAR(128), SELECTOR NVARCHAR(1024), NO_LOCAL CHAR(1), PRIMARY KEY(ID))
      INSERT_MAPPING=INSERT INTO JMS_CHANNEL_MAPPING (ID, TYPE, JMS_DEST_NAME, JMS_SUB_NAME, CLIENT_ID, SELECTOR, NO_LOCAL) VALUES (?, ?, ?, ?, ?, ?, ?)
      DELETE_MAPPING=DELETE FROM JMS_CHANNEL_MAPPING WHERE ID = ?
      SELECT_ID_FOR_DESTINATION=SELECT ID FROM JMS_CHANNEL_MAPPING WHERE TYPE=? AND JMS_DEST_NAME=?
      SELECT_DURABLE_SUB=SELECT JMS_DEST_NAME, ID, SELECTOR, NO_LOCAL FROM JMS_CHANNEL_MAPPING WHERE CLIENT_ID=? AND JMS_SUB_NAME=?
      SELECT_SUBSCRIPTIONS_FOR_TOPIC=SELECT ID, CLIENT_ID, JMS_SUB_NAME, SELECTOR, NO_LOCAL FROM JMS_CHANNEL_MAPPING WHERE TYPE='D' AND JMS_DEST_NAME=?
      ]]>


        • 1. Re: RC3 stable? which jdk? ad on: mssql-persistence-service.
          Ovidiu Feodorov Master

           

          Josef@logistikpur.com wrote:

          1.
          we run jboss-4.0.4.GA (install: jboss-4.0.4.GA-Patch1-installer.jar default) under jdk1.5.0_07 (jdk-1_5_0_07-windows-i586-p.exe; build 1.5.0._07-b03) . is this the right jdk?


          We test both with JDK 1.4 and JDK 1.5, so you should be fine with jdk 1.5, at least as far as Messaging is concerned.

          Josef@logistikpur.com wrote:

          2.
          is it a good idea to use jboss-messaging-1.0.1.CR3 in a production environment?


          I would advise waiting until 1.0.1.GA is out. If everything goes fine, we should release CR5 by the end of the week, and then wait for another week for feedback, and then release the GA, if no issues are reported. We try to keep JIRA up-to-date, it's a good resource to use if you want to find out what's going on: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.plugin.system.project:roadmap-panel

          Josef@logistikpur.com wrote:

          3.
          what content will have the destinations-service.xml in a production environment?


          Currently it contains some tests destinations and the DLQ. It should stay the same. You can add your own destinations there, but you can also use a different deployment descriptor for those.

          Josef@logistikpur.com wrote:

          4.
          when will the first jboss-messaging-x.y production release be available?


          That would be 1.0.0.GA. It was released in March. If you mean next production release, see the answer to 2. above.