1 Reply Latest reply on Nov 17, 2009 11:20 PM by Yong Hao Gao

    Clustered JMS not respecting FLUSH timeout setting

    Matthew Parrish Newbie

      Hi, I'm not sure if this or the JGroups forum is the right place to post this message, but I'll start here. Our jgroups channel for JMS (jbm-control) is configured to have a FLUSH timeout of 20000ms (which is the JBoss 5.1.0.GA default). One of our nodes is having issues connecting to the JMS cluster and on the coordinator node, I see messages that the flush is timing out after 2000msec. Why is it timing out after 2 seconds instead of 20 seconds?

      Coordinator:

      <pbcast.FLUSH timeout="20000"/>
      


      2009-11-17 11:06:40,415 DEBUG [org.jgroups.protocols.pbcast.FLUSH] At 10.29.22.11:46312 timed out waiting for flush responses after 2000 msec. Rejecting flush to participants [10.29.22.11:46312, 10.29.22.13:44210, 10.29.22.12:57461, 10.29.22.15:56032, 10.29.22.17:54387, 10.29.22.16:56138]
      


      Joiner:
      <pbcast.GMS print_local_addr="true" join_timeout="8000"
       shun="true"
       view_bundling="true"/>
      


      2009-11-17 10:31:49,534 WARN [org.jgroups.protocols.pbcast.GMS] join(10.29.22.14:54328) sent to 10.29.22.11:46312 timed out (after 8000 ms), retrying
      


      Thanks,
      Matt