-
1. Re: EJB SLSB remote-invocation timeout configuration
jaikiran Mar 14, 2012 12:15 PM (in response to sumitsu)1 of 1 people found this helpfulThe default-access-timeout is not meant for what you are trying to achieve. That configuration is the default value to be used in the absence of any @javax.ejb.AccessTimeout for stateful beans.
As for the invocation timeout for remote invocations - it's a feature request here https://issues.jboss.org/browse/AS7-3811
-
2. Re: EJB SLSB remote-invocation timeout configuration
sumitsu Mar 14, 2012 2:13 PM (in response to jaikiran)Thanks, Jaikiran. Do you have any expectation as to when (or which JBoss AS version) that feature might be available?
Since I see that there is some debate as to the necessity of this feature on the JIRA page, I'd like to weigh in that in our environment, it is absolutely crucial that it be possible to cap the amount of time a client might wait for an EJB invocation to complete. In theory, certainly, it would be preferable to resolve the root problem causing the server-side logic to stall, but in the event of an unanticipated failure causing said logic to stall out, the timeout is imperative as a fail-safe to prevent the hanging failure from cascading back to the client application/system. It is much more doable, on the client side, to build logic to handle failures due to timeouts than it is to build logic to recover from a synchronous invocation which never terminates at all.
Thanks again.
-
3. Re: EJB SLSB remote-invocation timeout configuration
jaikiran Mar 15, 2012 1:47 AM (in response to sumitsu)Branden Smith wrote:
Thanks, Jaikiran. Do you have any expectation as to when (or which JBoss AS version) that feature might be available?
There are a couple of possible ways that have been mentioned in terms of how this is implemented. But apart from the implementation details, I think this should be available in the next release of AS7. Infact, you most likely won't even need to wait for the AS7 release and might just use the new EJB client API release containing this fix, if we end up fixing this without any server interaction (one of the suggested approaches for the timeout is to ping the server to check for the invocation status).