Re: TransactionContextInterceptor Keeps Releasing My Lock

Would you happen to call the method annotated with @DB from within the same class? If so, you would directly go to the method, instead of using the proxy which applies AOP. Regards, Frank On 26 Oct 2015 12:53, "Jeff Hair" wrote: > I have narrowed it down to multithreading

Re: TransactionContextInterceptor Keeps Releasing My Lock

My experience is this: - If I call the method directly from within the class, @DB seems to apply and the lock in the op_lock table stays active as long as it is needed. - If I call the method on another thread (internal class implementing Runnable), @DB does not apply and I have to wrap the

Re: TransactionContextInterceptor Keeps Releasing My Lock

I have narrowed it down to multithreading being the cause. I have a set of workers running through an executor service, and it seems cglib is not respecting the @DB annotation on the method being called by the thread. I can force the lock to be acquired if the entire method is executed in a

TransactionContextInterceptor Keeps Releasing My Lock

I'm using the DAO API to create a lock in the lock table as per https://cwiki.apache.org/confluence/display/CLOUDSTACK/Data+Access+Layer. However, the lock seems to mysteriously vanish after acquireInLockTable or lockInLockTable method returns. Looking at the code, I've discovered that