Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABzHfVnspmqv8UdKpbg00usPAX1zV+JnPhnEujLYs8hnv2X57w@mail.gmail.com>
References: <20110928094821.78CC314DDDA@vmgump.apache.org>
	<CABzHfVnspmqv8UdKpbg00usPAX1zV+JnPhnEujLYs8hnv2X57w@mail.gmail.com>
Date: Wed, 28 Sep 2011 23:52:48 +0400
Message-ID: 
 <CABzHfV=6x68qX1Gci=jj04UM+SSLJPy9TAZ6psGegaF46+AR7A@mail.gmail.com>
Subject: Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-test (in module
 tomcat-7.0.x) failed
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2011/9/28 Konstantin Kolinko <knst.kolinko@gmail.com>:
> 2011/9/28 Bill Barker <billbarker@apache.org>:
>> To whom it may engage...
>>
>> This is an automated request, but not an unsolicited one. For
>> more information please visit http://gump.apache.org/nagged.html,
>> and/or contact the folk at general@gump.apache.org.
>>
>> Project tomcat-tc7.0.x-test has an issue affecting its community integra=
tion.
>> This issue affects 1 projects,
>> =A0and has been outstanding for 8 runs.
>> The current state of this project is 'Failed', with reason 'Build Failed=
'.
>> For reference only, the following projects are affected by this:
>> =A0 =A0- tomcat-tc7.0.x-test : =A0Tomcat 7.x, a web server implementing =
Java Servlet 3.0,
>> =A0 =A0...
>>
>>
>> Full details are available at:
>> =A0 =A0http://vmgump.apache.org/gump/public/tomcat-7.0.x/tomcat-tc7.0.x-=
test/index.html
>
> Test org.apache.catalina.tribes.group.TestGroupChannelMemberArrival FAILE=
D
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> TEST-org.apache.catalina.tribes.group.TestGroupChannelMemberArrival.BIO.t=
xt
> Testcase: testMemberArrival took 4.38 sec
> =A0 =A0 =A0 =A0FAILED
> Checking member arrival length expected:<9> but was:<11>
> junit.framework.AssertionFailedError: Checking member arrival length
> expected:<9> but was:<11>
> =A0 =A0 =A0 =A0at org.apache.catalina.tribes.group.TestGroupChannelMember=
Arrival.testMemberArrival(TestGroupChannelMemberArrival.java:77)
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> The same failure as was observed by Gump in trunk yesterday.
> Again BIO fails, but NIO runs OK.
>
>> Checking member arrival length expected:<9> but was:<11>
>
> In failed trunk test it was
>> Checking member arrival length expected:<9> but was:<19>
>
> So, it received more data than were expected?
>

Huh. I found the cause. The test itself is broken.

The test has nested class TestMbrListener implements
MembershipListener that is used to handle notifications about added
and disappeared members.

Those notifications arrive asynchronously. Such as this one:
(org.apache.catalina.tribes.membership.McastServiceImpl :

            t =3D new Runnable() {
                @Override
                public void run() {
                    String name =3D Thread.currentThread().getName();
                    try {

Thread.currentThread().setName("Membership-MemberAdded.");
                        service.memberAdded(m);
                    }finally {
                        Thread.currentThread().setName(name);
                    }
                }
            };

            executor.execute(t);
)

The TestMbrListener stores its data in ArrayList. The error here is
that access to this ArrayList is not synchronized, but several
notifications can invoke the listener concurrently at the same time.

Thus ArrayList becomes corrupted and reports wrong value for its size().


Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org