Hi deadlock lovers, I just did a deadlock-retry-interceptor, which was more easy than I thought. There is a serverside variant and a client interceptor.
The interesting (i.e. non-perfect) points are: - how to configure retry strategy (quite simple now) - where to place the serverside thing in the chain (should be _outside_ of the transaction which just rolled back due to the deadlock; this probably implies that it could have to be done inside the TxInterceptor when entering a new tx. When _not_ doing "RequiresNew" the interceptor works fine between the SecutiyInterceptor and the TxInterceptor (I tried this with SLSB). - what to do with MDB (they are supposed to catch everything, so nothing gets through to the interceptor. My best guess is to use a UserTX inside the MDB, do the retry "manually" (w/o interceptor) and put all this in an AbstractDeadlockRetryMDB (I did this, it worked fine). Is there any interest to put this into Branch_3_2? Enjoy, Michael ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
