[jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1780) When i change the default db schemas of jbm tables the DLQ - if it contains message - run in deadlock by the next server restart, because it wants to use the default schema instead of the modified db schema

[Karl Max (JIRA)]

When i change the default db schemas of jbm tables the DLQ - if it contains message -  run in deadlock by the next server restart, because it wants to use the default schema instead of the modified db schema 
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JBMESSAGING-1780
                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1780
             Project: JBoss Messaging
          Issue Type: Bug
         Environment: JBoss 5.1.GA+Seam 2.1.1.GA+mysql 5.1
            Reporter: Karl Max


At first, I modified the default schema of jbm tables in mysql-persistence-service.xml
so, I changed the sql properties  JBM_DUAL to  newSchema.JBM_DUAL and so on...
Everything works fine with the modified schema, until I add a posion message to the dead letter queue.
Then I want to restart the JBoss server, I get an exception to it run in dead lock, because didn't find the jbm_msg tables (but it would be newSchema.jbm_msg  )




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira