Thanks for the help. I was able to successfully get everything on the server side running by using the settings below. Hopefully this will help someone else out who reads this post. Now I'm hitting another issue. We use Maven 2 to perform our builds, and my dependencies are no longer valid now that we've migrated to 4.2.2. I'm trying to use the maven 2jboss repository http://repository.jboss.com/maven2/ but I can't seem to find the messaging dependencies with the correct version. I'm using this doc http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/... as a guide on what dependencies I need. Do I need to deploy the artifacts from my application server and the linked URLS to my local repository, or can I find the version somewhere on the repository? Thanks, Todd Steps to migrate DefaultDS to MySQL and set up messaging. | * Download the latest MySQL client jar and put it in server/lib | * Set up the following in a mysql-ds.xml file, and remove the hsqldb-ds.xml file | | | | | <datasources> | | <local-tx-datasource> | | <jndi-name>DefaultDS</jndi-name> | | <connection-url> | | jdbc:mysql://localhost:3306/jboss | | </connection-url> | | <driver-class>com.mysql.jdbc.Driver</driver-class> | | <user-name>jboss</user-name> | | <password>password</password> | | <exception-sorter-class-name> | | org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter | | </exception-sorter-class-name> | | <metadata> | | <type-mapping>mySQL</type-mapping> | | </metadata> | | <!-- Required for Messaging to work correctly --> | | <transaction-isolation> | | TRANSACTION_READ_COMMITTED | | </transaction-isolation> | | </local-tx-datasource> | | | | </datasources> | | | | * Download the messaging distribution that has the same version as the one in your application server. For the JEMS 1.2.1.CR4 installer, I installed messaging version 1.4.0.SP3 (build: CVSTag=JBossMessaging_1_4_0_ | SP3 date=200712131418) | | * Copy mysql-persistence-service.xml from examples/config of your messaging download to server/deploy/jboss-messaging.sar, and either delete or rename hsqldb-persistence-service.xml.bak | | * Restart the server, and everything should work! | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144671#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...