[jboss-jira] [JBoss JIRA] (JGRP-1698) Bypass on FLUSH

[shen kim (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804931#comment-12804931 ] 

shen kim commented on JGRP-1698:
--------------------------------

I used the this config:
<config xmlns="urn:org:jgroups" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/JGroups-3.3.xsd">
<UDP />
<PING />
<MERGE2 />
<FD_SOCK />
<FD_ALL />
<VERIFY_SUSPECT />
<pbcast.NAKACK2 />
<UNICAST3 />
<pbcast.STABLE />
<pbcast.GMS />
<UFC />
<MFC />
<FRAG2 />
<pbcast.STATE_TRANSFER />
<pbcast.FLUSH bypass="true"/>
</config>

And simple start two thread like this:
public class Receiver extends ReceiverAdapter {

	private JChannel channel;

	private void start() throws Exception {
		this.channel = new JChannel("flush-udp.xml");
		this.channel.setReceiver(this);
		this.channel.connect("ChatCluster");
	}

	public static void main(String[] args) throws Exception {
		for (int i = 0; i < 2; i++) {
			new Thread(new Runnable() {
				public void run() {
					try {
						new Receiver().start();
					} catch (Exception e) {
						e.printStackTrace();
					}
				}
			}).start();
		}
	}

	public void receive(Message msg) {
		System.out.println(msg.getObject());
	}

	public void viewAccepted(View view) {
		System.out.println(view);
	}
}
Two members can not found each other, and the thread which start secondary likely be locked.
                
> Bypass on FLUSH
> ---------------
>
>                 Key: JGRP-1698
>                 URL: https://issues.jboss.org/browse/JGRP-1698
>             Project: JGroups
>          Issue Type: Bug
>         Environment: 3.4.0.Alpha2
>            Reporter: shen kim
>            Assignee: Bela Ban
>             Fix For: 3.5
>
>
> When I used 
> <pbcast.FLUSH bypass="true"/>
> start cluster, all of members would receive null Message periodical.

--
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