[JBoss JIRA] (JGRP-1805) OverlappingMergeTest testMergeWithDifferentPartitions fails to create correct merged view
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1805?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on JGRP-1805:
-------------------------------------------
An example of this failure of testMergeWithDifferentPartitions with the additional logging: (one failing copy run in the QA lab, one passing copy run on my local machine)
passing test:
{noformat}
------------- testMergeWithDifferentPartitions -----------
-------------------------------------------------------------------
GMS: address=D, cluster=OverlappingMergeTest, physical address=127.0.0.1:48135
-------------------------------------------------------------------
69904 [TRACE] GMS: - D: initial_mbrs are A
69904 [DEBUG] GMS: - election results: {A=1}
69904 [DEBUG] GMS: - sending JOIN(D) to A
69982 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
69982 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
==== Injecting view [A|4] [A, C, B] into A, B and C ====
69983 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
69984 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
69984 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
==== Injecting view [B|4] [B, A, C, D] into D ====
69985 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
A: [A|4] [A, C, B]
B: [A|4] [A, C, B]
C: [A|4] [A, C, B]
D: [B|4] [B, A, C, D]
==== Injecting a merge event into A, B, C and D====
Enabling TRACE debugging for GMS, MERGE2 and Discovery
70012 [DEBUG] GMS: - D: installing view MergeView::[A|5] [A, D, C, B], subgroups=[A|4] [A, C, B], [A|4] [A, C, B], [B|4] [D]
70013 [TRACE] GMS: - D: mcasting view MergeView::[A|5] [A, D, C, B], subgroups=[A|4] [A, C, B], [A|4] [A, C, B], [B|4] [D] (4 mbrs)
70043 [TRACE] GMS: - D: received all 4 ACKs from members for view [A|5]
Disabling TRACE debugging for GMS, MERGE2 and Discovery
A: [A|5] [A, D, C, B] (coord=true)
B: [A|5] [A, D, C, B] (coord=false)
C: [A|5] [A, D, C, B] (coord=false)
D: [A|5] [A, D, C, B] (coord=false)
{noformat}
failing test:
{noformat}
------------- testMergeWithDifferentPartitions -----------
-------------------------------------------------------------------
GMS: address=D, cluster=OverlappingMergeTest, physical address=10.16.92.187:27202
-------------------------------------------------------------------
182881 [TRACE] GMS: - D: initial_mbrs are C A
182882 [DEBUG] GMS: - election results: {A=2}
182882 [DEBUG] GMS: - sending JOIN(D) to A
182986 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
182986 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
==== Injecting view [A|4] [A, C, B] into A, B and C ====
182986 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
182987 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
182988 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
==== Injecting view [B|4] [B, A, C, D] into D ====
182989 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
A: [A|4] [A, C, B]
B: [A|4] [A, C, B]
C: [A|4] [A, C, B]
D: [B|4] [B, A, C, D]
==== Injecting a merge event into A, B, C and D====
Enabling TRACE debugging for GMS, MERGE2 and Discovery
Disabling TRACE debugging for GMS, MERGE2 and Discovery
A: [A|5] [A, B, C] (coord=true)
B: [A|5] [A, B, C] (coord=false)
C: [A|5] [A, B, C] (coord=false)
D: [B|4] [B, A, C, D] (coord=false)
{noformat}
It appears that there is no activity after the merge even is injected in the failing case, as there are no TRACE messages appearing.
> OverlappingMergeTest testMergeWithDifferentPartitions fails to create correct merged view
> -----------------------------------------------------------------------------------------
>
> Key: JGRP-1805
> URL: https://issues.jboss.org/browse/JGRP-1805
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test does the following:
> - creates four channels a,b,c,d
> - injects views A: {A,C,B}, B:{A,C,B}, C:{A,C,B} and D: {B,A,C,D}
> - injects a merge event in each of channels A,B,C,D representing these four views
> - checks that all channels have the final view of size 4
> The test fails intermittently on RHEL, with the same failure each time:
> {noformat}
> 181595 [DEBUG] GMS: - A: installing view [A|2] [A]
> [testng] 181596 [TRACE] GMS: - A: received all 1 ACKs from members for view [A|2]
> [testng] 181866 [TRACE] GMS: - view [A|3] [] is empty: will not multicast it (last view)
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=A, cluster=OverlappingMergeTest, physical address=10.16.94.42:27199
> [testng] -------------------------------------------------------------------
> [testng] 184954 [TRACE] GMS: - A: no initial members discovered: creating group as first member
> [testng] 184954 [DEBUG] GMS: - A: installing view [A|0] [A]
> [testng] 184955 [DEBUG] GMS: - created group (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=B, cluster=OverlappingMergeTest, physical address=10.16.94.42:27200
> [testng] -------------------------------------------------------------------
> [testng] 184961 [TRACE] GMS: - B: initial_mbrs are A
> [testng] 184961 [DEBUG] GMS: - election results: {A=1}
> [testng] 184961 [DEBUG] GMS: - sending JOIN(B) to A
> [testng] 185013 [TRACE] GMS: - A: new members=[B], suspected=[], leaving=[], new view: [A|1] [A, B]
> [testng] 185014 [TRACE] GMS: - A: mcasting view [A|1] [A, B] (2 mbrs)
> [testng]
> [testng] 185025 [DEBUG] GMS: - A: installing view [A|1] [A, B]
> [testng] 185026 [TRACE] GMS: - A: received all 1 ACKs from members for view [A|1]
> [testng] 185055 [TRACE] GMS: - B: JOIN-RSP=[A|1] [A, B] [size=2]
> [testng]
> [testng]
> [testng] 185055 [DEBUG] GMS: - B: installing view [A|1] [A, B]
> [testng] 185057 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|1]
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=C, cluster=OverlappingMergeTest, physical address=10.16.94.42:27201
> [testng] -------------------------------------------------------------------
> [testng] 185064 [TRACE] GMS: - C: initial_mbrs are B A
> [testng] 185064 [DEBUG] GMS: - election results: {A=2}
> [testng] 185064 [DEBUG] GMS: - sending JOIN(C) to A
> [testng] 185108 [TRACE] GMS: - A: new members=[C], suspected=[], leaving=[], new view: [A|2] [A, B, C]
> [testng] 185108 [TRACE] GMS: - A: mcasting view [A|2] [A, B, C] (3 mbrs)
> [testng]
> [testng] 185117 [DEBUG] GMS: - A: installing view [A|2] [A, B, C]
> [testng] 185118 [DEBUG] GMS: - B: installing view [A|2] [A, B, C]
> [testng] 185119 [TRACE] GMS: - A: received all 2 ACKs from members for view [A|2]
> [testng] 185148 [TRACE] GMS: - C: JOIN-RSP=[A|2] [A, B, C] [size=3]
> [testng]
> [testng]
> [testng] 185149 [DEBUG] GMS: - C: installing view [A|2] [A, B, C]
> [testng] 185151 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|2]
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=D, cluster=OverlappingMergeTest, physical address=10.16.94.42:27202
> [testng] -------------------------------------------------------------------
> [testng] 185164 [TRACE] GMS: - D: initial_mbrs are B C A
> [testng] 185164 [DEBUG] GMS: - election results: {A=3}
> [testng] 185164 [DEBUG] GMS: - sending JOIN(D) to A
> [testng] 185203 [TRACE] GMS: - A: new members=[D], suspected=[], leaving=[], new view: [A|3] [A, B, C, D]
> [testng] 185203 [TRACE] GMS: - A: mcasting view [A|3] [A, B, C, D] (4 mbrs)
> [testng]
> [testng] 185210 [DEBUG] GMS: - A: installing view [A|3] [A, B, C, D]
> [testng] 185211 [DEBUG] GMS: - B: installing view [A|3] [A, B, C, D]
> [testng] 185211 [DEBUG] GMS: - C: installing view [A|3] [A, B, C, D]
> [testng] 185213 [TRACE] GMS: - A: received all 3 ACKs from members for view [A|3]
> [testng] 185242 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
> [testng]
> [testng]
> [testng] 185242 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
> [testng] 185242 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|3]
> [testng]
> [testng] ==== Injecting view [A|4] [A, C, B] into A, B and C ====
> [testng] 185243 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
> [testng] 185243 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
> [testng] 185244 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
> [testng]
> [testng] ==== Injecting view [B|4] [B, A, C, D] into D ====
> [testng]
> [testng] 185245 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
> [testng] A: [A|4] [A, C, B]
> [testng] B: [A|4] [A, C, B]
> [testng] C: [A|4] [A, C, B]
> [testng] D: [B|4] [B, A, C, D]
> [testng]
> [testng] ==== Injecting a merge event into A, B, C and D====
> [testng] 185251 [TRACE] GMS: - A: got merge response from A, merge_id=A::3, merge data is sender=A, view=[A|4] [A, C, B], digest=C: [0 (0)], B: [0 (0)], A: [4 (4)]
> [testng] 185253 [TRACE] GMS: - B: queue is suspended; request MERGE(4 views) is discarded
> [testng] 185255 [TRACE] GMS: - C: queue is suspended; request MERGE(4 views) is discarded
> [testng] 185255 [TRACE] GMS: - A: got merge response from B, merge_id=A::3, merge data is sender=B, view=[A|4] [A, C, B], digest=C: [0 (0)], B: [0 (1)], A: [4 (4)]
> [testng] 190286 [TRACE] GMS: - A: mcasting view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] (3 mbrs)
> [testng]
> [testng] 190286 [TRACE] GMS: - B: mcasting view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] (3 mbrs)
> [testng]
> [testng] 190317 [DEBUG] GMS: - A: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B]
> [testng] 190318 [DEBUG] GMS: - B: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B]
> [testng] 190318 [DEBUG] GMS: - C: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B]
> [testng] 190320 [TRACE] GMS: - A: received all 3 ACKs from members for view [A|5]
> [testng] 190320 [TRACE] GMS: - B: received all 3 ACKs from members for view [A|5]
> [testng] A: [A|5] [A, B, C] (coord=true)
> [testng] B: [A|5] [A, B, C] (coord=false)
> [testng] C: [A|5] [A, B, C] (coord=false)
> [testng] D: [B|4] [B, A, C, D] (coord=false)
> [testng] 195277 [DEBUG] GMS: - D: sending LEAVE request to B
> [testng] FAIL: [1] org.jgroups.tests.OverlappingMergeTest.testMergeWithDifferentPartitions()
> {noformat}
> Whenever this test fails, I see that the queues are suspended on the initial merge attempt.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1805) OverlappingMergeTest testMergeWithDifferentPartitions fails to create correct merged view
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1805?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-1805 at 3/24/14 1:25 PM:
--------------------------------------------------------------------
An example of this failure of testMergeWithDifferentPartitions with the additional logging: (one failing copy run in the QA lab, one passing copy run on my local machine)
passing test:
{noformat}
------------- testMergeWithDifferentPartitions -----------
-------------------------------------------------------------------
GMS: address=D, cluster=OverlappingMergeTest, physical address=127.0.0.1:48135
-------------------------------------------------------------------
69904 [TRACE] GMS: - D: initial_mbrs are A
69904 [DEBUG] GMS: - election results: {A=1}
69904 [DEBUG] GMS: - sending JOIN(D) to A
69982 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
69982 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
==== Injecting view [A|4] [A, C, B] into A, B and C ====
69983 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
69984 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
69984 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
==== Injecting view [B|4] [B, A, C, D] into D ====
69985 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
A: [A|4] [A, C, B]
B: [A|4] [A, C, B]
C: [A|4] [A, C, B]
D: [B|4] [B, A, C, D]
==== Injecting a merge event into A, B, C and D====
Enabling TRACE debugging for GMS, MERGE2 and Discovery
70012 [DEBUG] GMS: - D: installing view MergeView::[A|5] [A, D, C, B], subgroups=[A|4] [A, C, B], [A|4] [A, C, B], [B|4] [D]
70013 [TRACE] GMS: - D: mcasting view MergeView::[A|5] [A, D, C, B], subgroups=[A|4] [A, C, B], [A|4] [A, C, B], [B|4] [D] (4 mbrs)
70043 [TRACE] GMS: - D: received all 4 ACKs from members for view [A|5]
Disabling TRACE debugging for GMS, MERGE2 and Discovery
A: [A|5] [A, D, C, B] (coord=true)
B: [A|5] [A, D, C, B] (coord=false)
C: [A|5] [A, D, C, B] (coord=false)
D: [A|5] [A, D, C, B] (coord=false)
{noformat}
failing test:
{noformat}
------------- testMergeWithDifferentPartitions -----------
-------------------------------------------------------------------
GMS: address=D, cluster=OverlappingMergeTest, physical address=10.16.92.187:27202
-------------------------------------------------------------------
182881 [TRACE] GMS: - D: initial_mbrs are C A
182882 [DEBUG] GMS: - election results: {A=2}
182882 [DEBUG] GMS: - sending JOIN(D) to A
182986 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
182986 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
==== Injecting view [A|4] [A, C, B] into A, B and C ====
182986 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
182987 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
182988 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
==== Injecting view [B|4] [B, A, C, D] into D ====
182989 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
A: [A|4] [A, C, B]
B: [A|4] [A, C, B]
C: [A|4] [A, C, B]
D: [B|4] [B, A, C, D]
==== Injecting a merge event into A, B, C and D====
Enabling TRACE debugging for GMS, MERGE2 and Discovery
Disabling TRACE debugging for GMS, MERGE2 and Discovery
A: [A|5] [A, B, C] (coord=true)
B: [A|5] [A, B, C] (coord=false)
C: [A|5] [A, B, C] (coord=false)
D: [B|4] [B, A, C, D] (coord=false)
{noformat}
It appears that there is no activity after the merge event is injected in the failing case, as there are no TRACE messages appearing.
was (Author: rachmato):
An example of this failure of testMergeWithDifferentPartitions with the additional logging: (one failing copy run in the QA lab, one passing copy run on my local machine)
passing test:
{noformat}
------------- testMergeWithDifferentPartitions -----------
-------------------------------------------------------------------
GMS: address=D, cluster=OverlappingMergeTest, physical address=127.0.0.1:48135
-------------------------------------------------------------------
69904 [TRACE] GMS: - D: initial_mbrs are A
69904 [DEBUG] GMS: - election results: {A=1}
69904 [DEBUG] GMS: - sending JOIN(D) to A
69982 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
69982 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
==== Injecting view [A|4] [A, C, B] into A, B and C ====
69983 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
69984 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
69984 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
==== Injecting view [B|4] [B, A, C, D] into D ====
69985 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
A: [A|4] [A, C, B]
B: [A|4] [A, C, B]
C: [A|4] [A, C, B]
D: [B|4] [B, A, C, D]
==== Injecting a merge event into A, B, C and D====
Enabling TRACE debugging for GMS, MERGE2 and Discovery
70012 [DEBUG] GMS: - D: installing view MergeView::[A|5] [A, D, C, B], subgroups=[A|4] [A, C, B], [A|4] [A, C, B], [B|4] [D]
70013 [TRACE] GMS: - D: mcasting view MergeView::[A|5] [A, D, C, B], subgroups=[A|4] [A, C, B], [A|4] [A, C, B], [B|4] [D] (4 mbrs)
70043 [TRACE] GMS: - D: received all 4 ACKs from members for view [A|5]
Disabling TRACE debugging for GMS, MERGE2 and Discovery
A: [A|5] [A, D, C, B] (coord=true)
B: [A|5] [A, D, C, B] (coord=false)
C: [A|5] [A, D, C, B] (coord=false)
D: [A|5] [A, D, C, B] (coord=false)
{noformat}
failing test:
{noformat}
------------- testMergeWithDifferentPartitions -----------
-------------------------------------------------------------------
GMS: address=D, cluster=OverlappingMergeTest, physical address=10.16.92.187:27202
-------------------------------------------------------------------
182881 [TRACE] GMS: - D: initial_mbrs are C A
182882 [DEBUG] GMS: - election results: {A=2}
182882 [DEBUG] GMS: - sending JOIN(D) to A
182986 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
182986 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
==== Injecting view [A|4] [A, C, B] into A, B and C ====
182986 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
182987 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
182988 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
==== Injecting view [B|4] [B, A, C, D] into D ====
182989 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
A: [A|4] [A, C, B]
B: [A|4] [A, C, B]
C: [A|4] [A, C, B]
D: [B|4] [B, A, C, D]
==== Injecting a merge event into A, B, C and D====
Enabling TRACE debugging for GMS, MERGE2 and Discovery
Disabling TRACE debugging for GMS, MERGE2 and Discovery
A: [A|5] [A, B, C] (coord=true)
B: [A|5] [A, B, C] (coord=false)
C: [A|5] [A, B, C] (coord=false)
D: [B|4] [B, A, C, D] (coord=false)
{noformat}
It appears that there is no activity after the merge even is injected in the failing case, as there are no TRACE messages appearing.
> OverlappingMergeTest testMergeWithDifferentPartitions fails to create correct merged view
> -----------------------------------------------------------------------------------------
>
> Key: JGRP-1805
> URL: https://issues.jboss.org/browse/JGRP-1805
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13
> Environment: RHEL
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Fix For: 3.2.13
>
>
> This test does the following:
> - creates four channels a,b,c,d
> - injects views A: {A,C,B}, B:{A,C,B}, C:{A,C,B} and D: {B,A,C,D}
> - injects a merge event in each of channels A,B,C,D representing these four views
> - checks that all channels have the final view of size 4
> The test fails intermittently on RHEL, with the same failure each time:
> {noformat}
> 181595 [DEBUG] GMS: - A: installing view [A|2] [A]
> [testng] 181596 [TRACE] GMS: - A: received all 1 ACKs from members for view [A|2]
> [testng] 181866 [TRACE] GMS: - view [A|3] [] is empty: will not multicast it (last view)
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=A, cluster=OverlappingMergeTest, physical address=10.16.94.42:27199
> [testng] -------------------------------------------------------------------
> [testng] 184954 [TRACE] GMS: - A: no initial members discovered: creating group as first member
> [testng] 184954 [DEBUG] GMS: - A: installing view [A|0] [A]
> [testng] 184955 [DEBUG] GMS: - created group (first member). My view is [A|0], impl is org.jgroups.protocols.pbcast.CoordGmsImpl
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=B, cluster=OverlappingMergeTest, physical address=10.16.94.42:27200
> [testng] -------------------------------------------------------------------
> [testng] 184961 [TRACE] GMS: - B: initial_mbrs are A
> [testng] 184961 [DEBUG] GMS: - election results: {A=1}
> [testng] 184961 [DEBUG] GMS: - sending JOIN(B) to A
> [testng] 185013 [TRACE] GMS: - A: new members=[B], suspected=[], leaving=[], new view: [A|1] [A, B]
> [testng] 185014 [TRACE] GMS: - A: mcasting view [A|1] [A, B] (2 mbrs)
> [testng]
> [testng] 185025 [DEBUG] GMS: - A: installing view [A|1] [A, B]
> [testng] 185026 [TRACE] GMS: - A: received all 1 ACKs from members for view [A|1]
> [testng] 185055 [TRACE] GMS: - B: JOIN-RSP=[A|1] [A, B] [size=2]
> [testng]
> [testng]
> [testng] 185055 [DEBUG] GMS: - B: installing view [A|1] [A, B]
> [testng] 185057 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|1]
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=C, cluster=OverlappingMergeTest, physical address=10.16.94.42:27201
> [testng] -------------------------------------------------------------------
> [testng] 185064 [TRACE] GMS: - C: initial_mbrs are B A
> [testng] 185064 [DEBUG] GMS: - election results: {A=2}
> [testng] 185064 [DEBUG] GMS: - sending JOIN(C) to A
> [testng] 185108 [TRACE] GMS: - A: new members=[C], suspected=[], leaving=[], new view: [A|2] [A, B, C]
> [testng] 185108 [TRACE] GMS: - A: mcasting view [A|2] [A, B, C] (3 mbrs)
> [testng]
> [testng] 185117 [DEBUG] GMS: - A: installing view [A|2] [A, B, C]
> [testng] 185118 [DEBUG] GMS: - B: installing view [A|2] [A, B, C]
> [testng] 185119 [TRACE] GMS: - A: received all 2 ACKs from members for view [A|2]
> [testng] 185148 [TRACE] GMS: - C: JOIN-RSP=[A|2] [A, B, C] [size=3]
> [testng]
> [testng]
> [testng] 185149 [DEBUG] GMS: - C: installing view [A|2] [A, B, C]
> [testng] 185151 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|2]
> [testng]
> [testng] -------------------------------------------------------------------
> [testng] GMS: address=D, cluster=OverlappingMergeTest, physical address=10.16.94.42:27202
> [testng] -------------------------------------------------------------------
> [testng] 185164 [TRACE] GMS: - D: initial_mbrs are B C A
> [testng] 185164 [DEBUG] GMS: - election results: {A=3}
> [testng] 185164 [DEBUG] GMS: - sending JOIN(D) to A
> [testng] 185203 [TRACE] GMS: - A: new members=[D], suspected=[], leaving=[], new view: [A|3] [A, B, C, D]
> [testng] 185203 [TRACE] GMS: - A: mcasting view [A|3] [A, B, C, D] (4 mbrs)
> [testng]
> [testng] 185210 [DEBUG] GMS: - A: installing view [A|3] [A, B, C, D]
> [testng] 185211 [DEBUG] GMS: - B: installing view [A|3] [A, B, C, D]
> [testng] 185211 [DEBUG] GMS: - C: installing view [A|3] [A, B, C, D]
> [testng] 185213 [TRACE] GMS: - A: received all 3 ACKs from members for view [A|3]
> [testng] 185242 [TRACE] GMS: - D: JOIN-RSP=[A|3] [A, B, C, D] [size=4]
> [testng]
> [testng]
> [testng] 185242 [DEBUG] GMS: - D: installing view [A|3] [A, B, C, D]
> [testng] 185242 [TRACE] GMS: - A: received all ACKs (1) from joiners for view [A|3]
> [testng]
> [testng] ==== Injecting view [A|4] [A, C, B] into A, B and C ====
> [testng] 185243 [DEBUG] GMS: - A: installing view [A|4] [A, C, B]
> [testng] 185243 [DEBUG] GMS: - B: installing view [A|4] [A, C, B]
> [testng] 185244 [DEBUG] GMS: - C: installing view [A|4] [A, C, B]
> [testng]
> [testng] ==== Injecting view [B|4] [B, A, C, D] into D ====
> [testng]
> [testng] 185245 [DEBUG] GMS: - D: installing view [B|4] [B, A, C, D]
> [testng] A: [A|4] [A, C, B]
> [testng] B: [A|4] [A, C, B]
> [testng] C: [A|4] [A, C, B]
> [testng] D: [B|4] [B, A, C, D]
> [testng]
> [testng] ==== Injecting a merge event into A, B, C and D====
> [testng] 185251 [TRACE] GMS: - A: got merge response from A, merge_id=A::3, merge data is sender=A, view=[A|4] [A, C, B], digest=C: [0 (0)], B: [0 (0)], A: [4 (4)]
> [testng] 185253 [TRACE] GMS: - B: queue is suspended; request MERGE(4 views) is discarded
> [testng] 185255 [TRACE] GMS: - C: queue is suspended; request MERGE(4 views) is discarded
> [testng] 185255 [TRACE] GMS: - A: got merge response from B, merge_id=A::3, merge data is sender=B, view=[A|4] [A, C, B], digest=C: [0 (0)], B: [0 (1)], A: [4 (4)]
> [testng] 190286 [TRACE] GMS: - A: mcasting view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] (3 mbrs)
> [testng]
> [testng] 190286 [TRACE] GMS: - B: mcasting view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B] (3 mbrs)
> [testng]
> [testng] 190317 [DEBUG] GMS: - A: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B]
> [testng] 190318 [DEBUG] GMS: - B: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B]
> [testng] 190318 [DEBUG] GMS: - C: installing view MergeView::[A|5] [A, B, C], subgroups=[A|4] [A, C, B], [A|4] [A, C, B]
> [testng] 190320 [TRACE] GMS: - A: received all 3 ACKs from members for view [A|5]
> [testng] 190320 [TRACE] GMS: - B: received all 3 ACKs from members for view [A|5]
> [testng] A: [A|5] [A, B, C] (coord=true)
> [testng] B: [A|5] [A, B, C] (coord=false)
> [testng] C: [A|5] [A, B, C] (coord=false)
> [testng] D: [B|4] [B, A, C, D] (coord=false)
> [testng] 195277 [DEBUG] GMS: - D: sending LEAVE request to B
> [testng] FAIL: [1] org.jgroups.tests.OverlappingMergeTest.testMergeWithDifferentPartitions()
> {noformat}
> Whenever this test fails, I see that the queues are suspended on the initial merge attempt.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1810:
--------------------------------
Sorry, I looked in the wrong branch... Fixed now
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.4
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1810:
--------------------------------
It already is {{%d}} at least on the 3.4 branch. Where did you see {{(%)}} ?
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.4
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Chris LeCompte (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Chris LeCompte commented on JGRP-1810:
--------------------------------------
Shouldn't the my_highest_received(%) be changed to my_highest_received(%d) as well?
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.4
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1810:
---------------------------
Fix Version/s: 3.4.4
(was: 3.5)
The issue doesn't occur in 3.2 because we're not using format strings and in 3.5 because it has been fixed there, only in 3.4.x.
Fixed in 3.4.4
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.4
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1810.
----------------------------
Resolution: Done
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.4
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-1810 at 3/24/14 12:17 PM:
----------------------------------------------------------
You meant replace {{%d}} (not {{%%}}) didn't you ?
was (Author: belaban):
You meant replace {{%s}} (not {{%%}}) didn't you ?
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1810) Illegal format string in trace message in NAKACK2 protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1810?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1810:
--------------------------------
You meant replace {{%s}} (not {{%%}}) didn't you ?
> Illegal format string in trace message in NAKACK2 protocol
> ----------------------------------------------------------
>
> Key: JGRP-1810
> URL: https://issues.jboss.org/browse/JGRP-1810
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.4.3
> Reporter: Chris LeCompte
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> The NAKACK2 protocol has an invalid format string in one of its trace logging outputs:
> log.trace("%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s",
> local_addr, my_hr, hr, member + "#" + hr);
> This results in an error in the log:
> ERROR - Illegal format string "%s: my_highest_rcvd (%) < stability_highest_rcvd (%): requesting retransmission of %s"
> The % should be changed to %% to avoid the error. The arguments are in fact printed alongside the message however anything with ERROR in the text makes QA nervous.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JGRP-1811) Arithmetic Exception in MPerf when sending less than 10 messages
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1811?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1811.
----------------------------
Resolution: Done
> Arithmetic Exception in MPerf when sending less than 10 messages
> ----------------------------------------------------------------
>
> Key: JGRP-1811
> URL: https://issues.jboss.org/browse/JGRP-1811
> Project: JGroups
> Issue Type: Bug
> Reporter: Andrei Palade
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> Not sure if this is intended to be like this, but in MPerf when the user tries to set the num_msg to 1 and start sending the messages, MPerf throws
> Mar 22, 2014 4:02:25 PM org.jgroups.logging.JDKLogImpl error
> SEVERE: failure unmarshalling buffer
> java.lang.ArithmeticException: / by zero
> at org.jgroups.tests.perf.MPerf.handleData(MPerf.java:418)
> at org.jgroups.tests.perf.MPerf.receive(MPerf.java:280)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:890)
> at org.jgroups.JChannel.up(JChannel.java:746)
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:146)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> at org.jgroups.protocols.SEQUENCER.deliver(SEQUENCER.java:606)
> at org.jgroups.protocols.SEQUENCER.unwrapAndDeliver(SEQUENCER.java:573)
> at org.jgroups.protocols.SEQUENCER.up(SEQUENCER.java:279)
> at org.jgroups.protocols.SEQUENCER.up(SEQUENCER.java:308)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:434)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:434)
> at org.jgroups.stack.Protocol.up(Protocol.java:409)
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:520)
> at org.jgroups.protocols.pbcast.NAKACK2.deliverBatch(NAKACK2.java:927)
> at org.jgroups.protocols.pbcast.NAKACK2.removeAndPassUp(NAKACK2.java:857)
> at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:792)
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:573)
> at org.jgroups.protocols.BARRIER.up(BARRIER.java:152)
> at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:147)
> at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:199)
> at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:296)
> at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
> at org.jgroups.protocols.Discovery.up(Discovery.java:379)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1532)
> at org.jgroups.protocols.TP$3.run(TP.java:1466)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months