cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Maximus <frank.maxi...@nuagenetworks.net>
Subject Re: TransactionContextInterceptor Keeps Releasing My Lock
Date Wed, 28 Oct 2015 10:02:28 GMT
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" <jeff@greenqloud.com> wrote:

> 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
> transaction, or if I remove the producer-consumer BlockingQueue. Is there a
> way that makes sense besides one of these two options?
>
> On Wed, Oct 14, 2015 at 5:04 PM, Jeff Hair <jeff@greenqloud.com> wrote:
>
> > 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
> > TransactionContextInterceptor is closing the TransactionLegacy after the
> > method returns.
> >
> > I have @DB on the method calling acquireFromLockTable. What am I doing
> > wrong?
> >
>
>
>
> --
> *Jeff Hair*
> Technical Lead and Software Developer
>
> Tel: (+354) 415 0200
> jeff@greenqloud.com
> www.greenqloud.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message