User: charles_chan
  Date: 01/11/13 12:29:15

  Modified:    src/etc/conf/cluster jbossmq-service.xml
  Log:
  - Incorporate old fixes from default/ to cluster/
  
  Revision  Changes    Path
  1.2       +33 -7     jbossmq/src/etc/conf/cluster/jbossmq-service.xml
  
  Index: jbossmq-service.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/cluster/jbossmq-service.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- jbossmq-service.xml       2001/11/12 03:23:56     1.1
  +++ jbossmq-service.xml       2001/11/13 20:29:15     1.2
  @@ -7,7 +7,7 @@
   <!--                                                                       -->
   <!-- ===================================================================== -->
   
  -<!-- $Id: jbossmq-service.xml,v 1.1 2001/11/12 03:23:56 chirino Exp $ -->
  +<!-- $Id: jbossmq-service.xml,v 1.2 2001/11/13 20:29:15 charles_chan Exp $ -->
   
   <!--
      |  This contains the cluster configuration of jbossmq
  @@ -63,20 +63,46 @@
       <attribute name="DataDirectory">db/jbossmq/file/</attribute>
       <mbean-ref name="MessageCache">JBossMQ:service=MessageCache</mbean-ref>
     </mbean>
  +
     <!--
     A JDBC PersistenceManager.
     The "DataSource" reference should refer to your datasource
  -  configuration name. Check your <datasource>-service.xml for the details
  +  configuration name. The datasource should have autocommit ON for the
  +  JDBC PM to work properly. The supplied Hypersonic SQL datasource
  +  NoTransDS is configured with that in mind. (See
  +  hsqldb-default-service.xml for details)
  +
  +  The two attributes, TransactionTableName and MessageTableName, are
  +  optional. Their default values are "jms_transaction" and
  +  "jms_messages" respectively. There is no need to create these tables
  +  manually, they will be created automatically for you if they are not
  +  found. If that doesn't work for you, you can try the following SQL
  +  setup script (HypersonicSQL):
  +
  +  CREATE TABLE JMS_MESSAGES
  +  (
  +    MESSAGEID CHAR(32) NOT NULL,
  +    DESTINATION VARCHAR(32) NOT NULL,
  +    MESSAGEBLOB OBJECT,
  +    PRIMARY KEY (MESSAGEID, DESTINATION)
  +  );
  +  CREATE INDEX JMS_MESSAGES_DEST ON JMS_MESSAGES(DESTINATION);
  +
  +  CREATE TABLE JMS_TRANSACTIONS
  +  (
  +    ID CHAR(32)
  +  )
     -->
  -<!--
  +
  +  <!--
     <mbean code="org.jboss.mq.pm.jdbc.PersistenceManager"
         name="JBossMQ:service=PersistenceManager">
  -    <mbean-ref 
name="DataSource">JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=DefaultDS</mbean-ref>
  +    <mbean-ref 
name="DataSource">JBossMQ:service=ConnectionFactoryLoader,name=NoTransDS</mbean-ref>
       <mbean-ref name="MessageCache">JBossMQ:service=MessageCache</mbean-ref>
  -    <attribute name="TransactionTableName">jms_transaction2</attribute>
  -    <attribute name="MessageTableName">jms_messages2</attribute>
  +    <attribute name="TransactionTableName">jms_transaction</attribute>
  +    <attribute name="MessageTableName">jms_messages</attribute>
     </mbean>
  --->
  +  -->
   
     <!--
        | InvocationLayers are the different transport methods that can
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to