Hello once again, i just wan to bring additional information about my configuration and settings.
I have no error when sending some messages to the client. Every think works well. No JDBC connectivity errors. The connection with the DataBase via the datasource is successfull (Following tables are created: ms_messages, jms_roles, jms_subcriptions, jms_transactions, jms_users, timer ) The only think i'm expecting is some entries in the JMS_MESSAGES table. Hier is my mysql-ds.xml file: <?xml version="1.0" encoding="UTF-8"?> | <!-- $Id: mysql-ds.xml,v 1.3.2.1 2004/12/01 11:46:00 schrouf Exp $ --> | <!-- Datasource config for MySQL using 3.0.9 available from: | http://www.mysql.com/downloads/api-jdbc-stable.html | --> | <datasources> | <local-tx-datasource> | <jndi-name>MySqlDS</jndi-name> | <connection-url>jdbc:mysql://localhost/jbpmjmsdb</connection-url> | <driver-class>com.mysql.jdbc.Driver</driver-class> | <user-name>jbpmuser</user-name> | <password>jbpmuser</password> | <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name> | <!-- sql to call when connection is created | <new-connection-sql>some arbitrary sql</new-connection-sql> | --> | <!-- sql to call on an existing pooled connection when it is obtained from pool | <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql> | --> | <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) --> | <metadata> | <type-mapping>mySQL</type-mapping> | </metadata> | </local-tx-datasource> | </datasources> | | and the mysql-jdbc2-service file : <?xml version="1.0" encoding="UTF-8"?> | | <!-- $Id: mysql-jdbc2-service.xml,v 1.8.2.4 2005/08/13 20:47:52 adrian Exp $ --> | | <server> | | <!-- ==================================================================== --> | <!-- Persistence and caching using MySQL --> | <!-- 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 was supplied by Stephane Nicoll in the forums as an example for MySQL | --> | <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager" | name="jboss.mq:service=PersistenceManager"> | <!--depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends--> | <depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=MySqlDS</depends> | | <!-- Changed: SELECT_MAX_TX = SELECT MAX(TXID) FROM (SELECT MAX(TXID) AS TXID FROM JMS_TRANSACTIONS UNION SELECT MAX(TXID) AS TXID FROM JMS_MESSAGES) AS TR_TABLE--> | <attribute name="SqlProperties"> | BLOB_TYPE=BYTES_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) AS TR_TABLE | DELETE_ALL_TX = DELETE FROM JMS_TRANSACTIONS | SELECT_MESSAGES_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB 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=? | 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 JMS_MESSAGES FROM JMS_MESSAGES, JMS_TRANSACTIONS WHERE JMS_MESSAGES.TXID = JMS_TRANSACTIONS.TXID AND JMS_MESSAGES.TXOP=? | 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(150) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB LONGBLOB, 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--> | </mbean> | </server> | . Is there some one who already configure this successfully and can tell me what is wrong in my configuration ? Please let me know If you need additional information like server log-file. Thank once again Bertrand N. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946488#3946488 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946488 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
