[
https://issues.apache.org/jira/browse/GERONIMO-5376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877737#action_12877737
]
Ivan commented on GERONIMO-5376:
--------------------------------
1. I opened a JIRA OpenEJB-1297, and David has kindly fixed the issue in the
trunk, it should be ported to 3.1.3 branch soon.
2. openejb.client.requestretry system property is need to configured on the
client side, or we could get an exception in the first call after the last
server is down
3. The configuration in the description is not correctly, you might refer to
the https://cwiki.apache.org/OPENEJBx30/failover.html.
> OpenEJB failover failed
> ------------------------
>
> Key: GERONIMO-5376
> URL: https://issues.apache.org/jira/browse/GERONIMO-5376
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenEJB
> Affects Versions: 2.2.1
> Environment: windows 2003, suse10 sp2, redhat 5.3
> jdk: sun 1.6.10
> Reporter: viola.lu
> Assignee: Ivan
> Fix For: 2.2.1
>
> Attachments: loadbean.zip
>
>
> Server 1: window 2003, viola-dev
> Server 2: suse 10 sp2, suse10sp268
> Server 3: redhat 5.3, rhel53x86
> 1. Add MultipointServers=suse10sp268:4212 to server 1
> 2. Add MultipointServers=rhel53x86:4212 to server 2
> 3. Add MultipointServers=rhel53x86:4212 to server 3
> 4.Deploy loadbean interface to server 1. deploy loadbean implementation to
> server 2, server 3
> Deploy a openejb client servlet to server 1 which call server 2. server 3
>
> p.setProperty(Context.PROVIDER_URL,"failover:ejbd://suse10sp2:4201,ejbd://rhel53x86:4201");
> 5.Shutdown server 2, it should failover to server 3, but failed, server 1
> reported errors:
> Invalid response from server -1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
