Hi
We had the same problem with NFS, I think it's an NFS/Java issue since
there also seem to be problems with other applications.
But someone told me they've it running successful with NFS, so I
suppose it's NFS-implementation/version specific whether locking works
or not (he ran a JVM 1.5.0_08 and
You can specify your own jdbc adapter class (see
http://activemq.apache.org/jdbc-support.html).
What I'd do is write a mysql adapter (extend the mysql one) and
override the locking statements. You can also rename the mysql adapter
for AMQ 5 (or svn revision 518161/518164) into
MySqlPropertLockingAd
to further respond to my own posts,
just tried to get mysql masterslave going and ran into this bug:
http://www.nabble.com/Master-Slave-locking-with-MYSQL-is-not-working-with-4.1.1-tf3399897s2354.html#a9475786
is there any way to get redundancy working with 4.1.1??
jdemic wrote:
>
> To furt
To further complicate this, I just tested failover and the following
happened:
- i kill -9'd activemq on the master server.
- on the slave server, activemq was still spinning on the filesystem lock as
per my last email.
- when i started up the master again, it started spinning on the filesystem
l
