Re: JDBC Master/Slave question

Think of it as a restart. Anything persisted will be available. It is similar to a broker restart as a slave broker start is stalled pending getting an exclusive lock on the persistent store. It can only proceed with its start when the master dies. On 12 February 2010 17:48, cmoulliard wrote: >

Re: JDBC Master Slave Question

I got to try out the scenario I described above (ie) physically remove the network cable from the Master. Basically the database did not realize that the client had disconnected abruptly, and there was still a lock on the database table, (which was now an invalid stale lock), and would never ge

Re: JDBC Master Slave Question

You have got to ask the JDBC driver or database documentation. I imagine there is a lock expiry option that can be tweaked. 2009/6/29 colonelx > > Hi, > > I have 2 brokers setup in a JDBC Master Slave Configuration. > > Each broker is on a different machine. BoxA and BoxB > The database is also

Re: JDBC Master Slave Question

I know that I could test this by plugging in and out the physical network connections, but I'm not really in a position to do this on any of the above boxes. If you are on Windows you can use TCPView to kill connections without having to physically disconnect the network: