Do you use EJB2?
The it might be a solution of 'clustered-stateless-unified-invoker', see standardjboss.xml configuration.
Here a SingleRetryInterceptor is in the chain. (RetryInterceptor is also available).
But I suppose you will not solve each gap, I found sporadicaly such Exceptions during shutdown a note from a cluster under load.
For me the problem is more strange because we use the TransactionStickyLB with UserTransactions, and here the gap is big because the SLSB from app is down but the UTx is available and the UTx.begin() will work but can not reach the SLSB.
We are using the clustered-stateless-unified-invoker that contains the SingleRetryInterceptor, but I don't think that is helping us since it is only triggered on ServiceUnavailableException which is not what we are getting.
1 of 1 people found this helpful
The I suppose you have to code yourselve if you would not accept the sporadical failure in case of shutdown one node.
But you have to keep in mind that it will only work if you don't use UserTransactions.
Ok, thanks for the clarification.