Here's a new one I just looked into.  Every time I try to trash more than one mail item at a time (select a bunch of mails in TBird and hit 'Delete') I get a failure.  The logs have a huge dump which I can attach if necessary.  But the key lines are:

Caused by: <openjpa-3.0.0-r422266:1833209 fatal store error> org.apache.openjpa.persistence.RollbackException: Optimistic locking errors were detected when flushing to the data store.  The following objects may have been concurrently modified in another transaction: [org.apache.james.mailbox.jpa.mail.model.JPAUserFlag-1530940342]

Caused by: <openjpa-3.0.0-r422266:1833209 nonfatal store error> org.apache.openjpa.persistence.OptimisticLockException: An optimistic lock violation was detected when flushing object instance "org.apache.james.mailbox.jpa.mail.model.JPAUserFlag-1530940342" to the data store.  This indicates that the object was concurrently modified in another transaction.

I understand locking, etc.  I googled 'optimistic lock' but I'd have to dig deeper to understand how it's used in JPA.  In any case, apparently these locks are fighting with each other when more than one update is attempted on a mailbox.

This is very reproducible.  So far, I have never been able to delete more than one item at a time.

I guess my current version is in the ballpark of 3.4+.  It was a clone of the master branch right after 3.4 went live.

Give me some pointers, and I'll do a little debug and analysis. But at this point, no idea where to start.  Suggestions?

Jerry


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org

Reply via email to