Clientside timeouts for EJB-Calls (2.1 + 3.0)

bernd.koecke Jul 16, 2009 3:23 AM

Hello,
we have EJB 2.1 and 3.0 Beans on JBossAS 4.2.3 and EJB 2.1 on JBossAS 4.0.2. Now our clients would like to set timeouts for their RMI-EJB-Calls. I can set a timeout on the server side for all EJBs, but we have applications which are used by frontend and backend systems. The Backends can wait for the response, but the Frontends need a fast response or an exception.

Is there a possibility to set such timeouts on the client side?

I think setting the so-timeout on the client socket would be a solution. I found a solution for EJB 3, with a small additional interceptor and an optional properties file in the clients classpath. But this doesn't work for EJB 2.1 on JBossAS 4.2.3 and 4.0.2. It seems that I have to replace some classes at the interface between EJB-Container and JBossRemoting. Or do I miss a configuration alternative?

Thanks a lot,
Bernd

1. Re: Clientside timeouts for EJB-Calls (2.1 + 3.0)

rzd Jan 26, 2012 6:11 AM (in response to bernd.koecke)

Have you seen the TransactionTimeout stuff in the reference guide?
Actions
2. Re: Clientside timeouts for EJB-Calls (2.1 + 3.0)

wdfink Jan 26, 2012 7:20 AM (in response to bernd.koecke)

The transaction timeout will not give you a guarantee whether the call is interrupted or not, it is only to ensure that the transaction will not commit after that timeout.

The common way to have control for such timeouts is to handle it with a thread on client side. Other option might be to write your own client side interceptor that will handle this, but this may depend on the AS and its version.
Actions

Go to original post