[
https://issues.apache.org/jira/browse/OPENEJB-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Blevins closed OPENEJB-1293.
----------------------------------
Resolution: Fixed
> Conditional Client Failover based on container or bean thrown Exception types
> -----------------------------------------------------------------------------
>
> Key: OPENEJB-1293
> URL: https://issues.apache.org/jira/browse/OPENEJB-1293
> Project: OpenEJB
> Issue Type: Improvement
> Components: server
> Reporter: David Blevins
> Assignee: David Blevins
> Fix For: 3.1.3
>
>
> Calling org.apache.openejb.client.Client.addRetryCondition(MyException.class)
> allows the addition of either standard or custom exception classes to be seen
> as failures which should result in failover and the request retried on a
> different server. A concrete example might be
> javax.ejb.ConcurrentAccessTimeoutException, which indicates the bean itself
> is busy and cannot be accessed. Or in the case of @Stateless beans indicates
> the pool itself is drained and all instances are in use.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
