[
http://jira.jboss.com/jira/browse/JBMESSAGING-1381?page=comments#action_1... ]
Clebert Suconic commented on JBMESSAGING-1381:
----------------------------------------------
The correct procedure to enable MySQL persistence on EAP should be:
1. Install JBossAS
2. Deploy a MessagingDS pointing to the MySQL server. Database can be empty, JBM will
create tables on startup.
3. Delete deploy/jboss-messaging.sar/clustered-hsqldb-persistence-service.xml
3. Copy the mysql-persistence-service.xml from the /examples/jms (******..... not from the
release ******)
4. Edit persistence service to use MessagingDS.
5. Edit conf/login-config.xml to use MessagingDS for messaging.
6. Deploy mysql-connector-java-5.0.7-bin.jar in server lib.
I'm validating the procedure now, but I won't validate the install from the
Release. It should be the same but i can't guarantee you would get the right version
of the XML.
JBM SP3 CP02 with MySQL persistence not working
-----------------------------------------------
Key: JBMESSAGING-1381
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1381
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP3.CP02
Environment: kernel-2.6.25.4-10.fc8
4.3.0-2.GA_CP01.ep1.7.el4
jboss-messaging-1.4.0-1.SP3_CP02.0jpp.ep1.6.el4
Reporter: Naveen Malik
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP04
Attachments: login-config.xml, messaging-ds.xml, mysql-persistence-service.xml
Recently switched from JBM SP3 CP01 to CP02. I am using MySQL for persistence and am
unable to send a message to a queue successfully. The app server starts up without error,
but fails when attempting to send a message to a queue. JBM is creating the tables on
startup.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira