You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "daniel mueller (JIRA)" <ji...@apache.org> on 2007/03/20 22:01:34 UTC

[jira] Updated: (AMQ-1191) JDBC based Master/Slave not supported for TransactSQL based databases (SQL Server and Sybase)

     [ https://issues.apache.org/activemq/browse/AMQ-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

daniel mueller updated AMQ-1191:
--------------------------------

    Attachment: patchfile

This is a patch which should resolve the XLOCK problem in SQLServer.
the correct syntax seems to be 
  WITH (UPDLOCK, ROWLOCK)
(at least according to hibernate http://anonhibernate.labs.jboss.com/trunk/Hibernate3/src/org/hibernate/dialect/SQLServerDialect.java see #appendLockHint(..))

On a side note: I dont think that the the current way of handling driver specific syntax will work out in this case because it seems that sybase does use a different syntax and jtds supports both. see http://anonhibernate.labs.jboss.com/trunk/Hibernate3/src/org/hibernate/dialect/SybaseDialect.java

It might well be that the patch breaks currently working installations because of this..

> JDBC based Master/Slave not supported for TransactSQL based databases (SQL Server and Sybase)
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1191
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1191
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: james strachan
>         Assigned To: james strachan
>             Fix For: 4.2.0
>
>         Attachments: patchfile
>
>
> The main issue is figuring out the exclusive lock SQL syntax. I think the following is valid...
> SELECT * FROM TABLE WITH XLOCK

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.