You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (Created) (JIRA)" <ji...@apache.org> on 2011/12/21 23:41:30 UTC
[jira] [Created] (OPENEJB-1729) Reliability of Multipoint remove
event when last peer disappears
Reliability of Multipoint remove event when last peer disappears
----------------------------------------------------------------
Key: OPENEJB-1729
URL: https://issues.apache.org/jira/browse/OPENEJB-1729
Project: OpenEJB
Issue Type: Bug
Components: server
Affects Versions: 3.1.4, 3.1.3, 3.1.2, 3.1.1, 3.1, 4.0-beta-1
Reporter: David Blevins
Assignee: David Blevins
Fix For: 4.0-beta-2
The approach to checking for the vitality of connected peers was driven by other peers. This worked perfectly fine in scenarios with at least two nodes. When the number of nodes dropped to 1, the discovery process stopped.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENEJB-1729) Reliability of Multipoint remove
event when last peer disappears
Posted by "David Blevins (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191041#comment-13191041 ]
David Blevins commented on OPENEJB-1729:
----------------------------------------
2011-12-21 - http://svn.apache.org/viewvc?view=revision&revision=1221924 - dblevins
2011-12-21 - http://svn.apache.org/viewvc?view=revision&revision=1221929 - dblevins
2011-12-22 - http://svn.apache.org/viewvc?view=revision&revision=1222090 - jlmonteiro
> Reliability of Multipoint remove event when last peer disappears
> ----------------------------------------------------------------
>
> Key: OPENEJB-1729
> URL: https://issues.apache.org/jira/browse/OPENEJB-1729
> Project: OpenEJB
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 4.0-beta-1
> Reporter: David Blevins
> Assignee: David Blevins
> Fix For: 4.0.0-beta-2
>
>
> The approach to checking for the vitality of connected peers was driven by other peers. This worked perfectly fine in scenarios with at least two nodes. When the number of nodes dropped to 1, the discovery process stopped.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENEJB-1729) Reliability of Multipoint remove
event when last peer disappears
Posted by "David Blevins (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed OPENEJB-1729.
----------------------------------
Resolution: Fixed
> Reliability of Multipoint remove event when last peer disappears
> ----------------------------------------------------------------
>
> Key: OPENEJB-1729
> URL: https://issues.apache.org/jira/browse/OPENEJB-1729
> Project: OpenEJB
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 4.0-beta-1
> Reporter: David Blevins
> Assignee: David Blevins
> Fix For: 4.0.0-beta-2
>
>
> The approach to checking for the vitality of connected peers was driven by other peers. This worked perfectly fine in scenarios with at least two nodes. When the number of nodes dropped to 1, the discovery process stopped.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira