Huh, I've hit this independently sometime in the early spring and since then I have a comment about that in our configs :) But this is certainly not the issue now.

Radim

On 10/11/2013 03:54 PM, Dan Berindei wrote:
I changed the default config some time ago, but I forgot to close ISPN-3334.


On Fri, Oct 11, 2013 at 4:35 PM, Ray Tsang <saturn...@gmail.com <mailto:saturn...@gmail.com>> wrote:

    also, don't forget this one: https://issues.jboss.org/browse/ISPN-3334


    On Fri, Oct 11, 2013 at 9:22 AM, Erik Salter <an1...@hotmail.com
    <mailto:an1...@hotmail.com>> wrote:

        Hi Radim,

        If you're using VMs, this may be of use.  I actually
        experienced a JGroups
        lockup in production with FC in decrementCredits.  What
        happened in my case
        is that virtualization tools had actually screwed with the
        system clock --
        it was reported that JBoss took ~1 year to start.

        http://www.vmware.com/pdf/vmware_timekeeping.pdf

        The upshot is that I had to take FC out of my stack going forward.

        Erik

        -----Original Message-----
        From: infinispan-dev-boun...@lists.jboss.org
        <mailto:infinispan-dev-boun...@lists.jboss.org>
        [mailto:infinispan-dev-boun...@lists.jboss.org
        <mailto:infinispan-dev-boun...@lists.jboss.org>] On Behalf Of
        Radim Vansa
        Sent: Friday, October 11, 2013 8:41 AM
        To: infinispan-dev@lists.jboss.org
        <mailto:infinispan-dev@lists.jboss.org>
        Subject: [infinispan-dev] Is anyone else experiencing JGRP-1675

        Hi,

        since Infinispan moved to JGroups 3.4, we're experiencing
        occassional
        deadlocks in some tests - most of threads that send anything
        over JGroups
        are waiting in JGroups' FlowControl.decrementCredits. The
        problem sometimes
        goes away after several seconds, but it produces some ugly
        spikes in our
        througput/response time charts. Originally this affected just
        some RadarGun
        tests but this is appearing in some client-server tests as
        well (we've
        recently investigated an issue where this appeared in a
        regular soak test).
        I was looking into that [1] for some time but haven't really
        figured out the
        cause. The workaround is to set up MFC and UFC credits high
        enough (I use
        10M) and stuff works then. I was trying to reproduce that on
        pure JGroups,
        but unsuccessfully.
        I am not asking anyone to dig into that, but I wanted to know
        whether QA is
        alone experiencing that or if there are more of us.

        Radim

        [1] https://issues.jboss.org/browse/JGRP-1675

        --
        Radim Vansa <rva...@redhat.com <mailto:rva...@redhat.com>>
        JBoss DataGrid QA

        _______________________________________________
        infinispan-dev mailing list
        infinispan-dev@lists.jboss.org
        <mailto:infinispan-dev@lists.jboss.org>
        https://lists.jboss.org/mailman/listinfo/infinispan-dev

        _______________________________________________
        infinispan-dev mailing list
        infinispan-dev@lists.jboss.org
        <mailto:infinispan-dev@lists.jboss.org>
        https://lists.jboss.org/mailman/listinfo/infinispan-dev



    _______________________________________________
    infinispan-dev mailing list
    infinispan-dev@lists.jboss.org <mailto:infinispan-dev@lists.jboss.org>
    https://lists.jboss.org/mailman/listinfo/infinispan-dev




_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev


--
Radim Vansa <rva...@redhat.com>
JBoss DataGrid QA

_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev

Reply via email to