Re: MS Sql server Master Slave problem

Hi, I was getting similar message with mssql server. But problem fixed for me after installing hotfix from microsoft for sql server 2012 cumulative update 3 https://support.microsoft.com/en-sg/help/2740957/fix-for-update-clause-allowed-only-for-declare-cursor-error-when-you-e

Re: MS Sql server Master Slave problem

Using jTDS JDBC driver instead of sqljdbc(4).jar seems sloved the problem. Works fine so far .. cobrien wrote: > > Each instance will try to run "SELECT FOR UPDATE" to > acquire a lock. > > I would first check if the "SELECT FOR UPDATE" syntax is supported by > your version of SQL Ser

Re: MS Sql server Master Slave problem

Each instance will try to run "SELECT FOR UPDATE" to acquire a lock. I would first check if the "SELECT FOR UPDATE" syntax is supported by your version of SQL Server. I think at one time this syntax was not supported. See http://www.informit.com/articles/article.aspx?p=327394&seqNum=2.

Re: MS Sql server Master Slave problem

Thanks. However, change false to true will cause: 2010-07-13 10:52:14,515 [Thread-2 ] INFO ResourceXmlApplicationContext - Refreshing org.apache.xbean.spring.context.resourcexmlapplicationcont...@96b5c2: display name [org.apache.xbean.spring.context.resourcexmlapplicationcont...@96b5c2]

Re: MS Sql server Master Slave problem

Hi: Set useDatabaseLock=true. -Clark www.ttmsolutions.com ActiveMQ reference guide at http://bit.ly/AMQRefGuide test4john wrote: > > Client code start producing msg OK, but if stop broker A in the middle of > the loop (expect broker B will take over and continue to produce), > excepti