>As for locking, the reason for a lock is to prevent multiple threads from
>working on the same message simultaneously. A thread obtains a lock on a
>message while it current works on it.... It doesn't make sense to write
>this locking to disk because if the JVM dies, the thread dies, so the lock
>is irrelevant. If you had multiple JVMs working against a single queue,
>then locking on the disk (or database) would be required.
I guess the confusion that I have (and it is undoubtedly my fault) is why
*all* the messages in the database have to be checked for their *locked*
status if that information is not in the database. It seems inefficient.
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]