]
Bela Ban commented on JGRP-2128:
--------------------------------
Didn't you see the following warning?
{code:java}
if(internal_thread_pool_min_threads < 2)
log.warn("The internal thread pool was configured with only %d min_threads; this
might lead to problems " +
"when more than 1 thread is needed, e.g. when merging",
internal_thread_pool_min_threads);
{code}
OK, I'm closing this issue.
MERGE3: incorrect merge
-----------------------
Key: JGRP-2128
URL:
https://issues.jboss.org/browse/JGRP-2128
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Labels: CR3
Fix For: 3.6.12, 4.0
Attachments: BrokerPE-0.zip, SEM03VVM-201.zip, SEM03VVM-202.zip
The following merge is incorrect, investigate what the desired behavior should be.
Link:
http://stackoverflow.com/questions/40492204/incorrect-merge-views-with-in...
{noformat}
(Incoming-1,BrokerPE-0-28575) ISPN000094: Received new cluster view for channel ISPN:
[BrokerPE-0-28575|2] (3) [BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714]
ISPN000094: Received new cluster view for channel ISPN: [BrokerPE-0-28575|3] (2)
[BrokerPE-0-28575, SEM03VVM-202-33714] --> one node disconnected
ISPN000093: Received new, MERGED cluster view for channel ISPN:
MergeView::[BrokerPE-0-28575|4] (2) [BrokerPE-0-28575, SEM03VVM-201-59385], 2 subgroups:
[BrokerPE-0-28575|3] (2) [BrokerPE-0-28575, SEM03VVM-202-33714], [BrokerPE-0-28575|2] (3)
[BrokerPE-0-28575, SEM03VVM-201-59385, SEM03VVM-202-33714] --> incorrect merge
{noformat}