Naming test timeout was Re: [jboss-dev] PUSH

[Brian Stansberry]

Adrian Brock wrote:
> On Thu, 2008-06-26 at 14:30 +0200, Sacha Labourey wrote:
>> In case you usually don't look at the result of the AS testsuite, here 
>> is the list of the 39 remaining failing tests:
>>
>>
>>     * org.jboss.test.naming.test.SimpleUnitTestCase.unknown
> 
> This test passes for me locally, so there's obviously something
> happening different on the test machine.
> 
> When I look at the log around the time of this test
> http://hudson.jboss.org/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/lastBuild/artifact/trunk/build/output/jboss-5.0.0.CR1/server/all/log/server.log
> 
> I see some warnings from the TM and some errors from jgroups:
> 
> 1) end of previous test
> 
> 2008-06-26 04:05:00,541 DEBUG
> [org.jboss.deployers.plugins.deployers.DeployersImpl] (RMI TCP
> Connection(487)-10.18.94.175) Fully Undeployed
> vfszip:/qa/services/hudson/
> hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/naming-pooled.sar
> 
> 2) TM Warnings (these are repeated)
> 

<snip/>

> 
> 3) JGroups error (there are repeated)
> 
> 2008-06-26 04:06:02,959 ERROR [org.jgroups.protocols.MPING]
> (ReceiverThread) failed receiving packet (from /10.18.0.232:45567)
> java.io.IOException: length has to be 4 or 16 bytes (was 10 bytes)
>         at org.jgroups.stack.IpAddress.readFrom(IpAddress.java:306)
>         at org.jgroups.Message.readFrom(Message.java:737)
>         at org.jgroups.protocols.MPING.run(MPING.java:355)
>         at java.lang.Thread.run(Thread.java:595)
> 

This is logged from the MPING multicast discovery protocol used by JBM's 
data channel. Means something else in the cluster is multicasting on 
port 45567 (probably other non-MPING JGroups traffic from a UDP 
protocol.) MPING just recognizes it doesn't understand the incoming 
packet, logs an error and drops it.  Should have no meaningful impact on 
this server.

These were occuring occasionally throughout the course of the test run. 
Seeing more of them during the 5 minute lag here is just a continuation 
of what had been happening all along.

> 4) Start of next test (5 minutes after step 1)
> 
> 2008-06-26 04:10:06,294 WARN  [org.jboss.deployment.MainDeployer] (RMI
> TCP Connection(491)-10.18.94.175) undeploy
> 'file:/qa/services/hudson/hudson_workspace/workspace/
> JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/probe.jar' :
> package not deployed
> 2008-06-26 04:10:06,294 INFO  [org.jboss.deployment.MainDeployer] (RMI
> TCP Connection(491)-10.18.94.175) deploy,
> url=file:/qa/services/hudson/hudson_workspace/workspac
> e/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib/probe.jar
> 

-- 
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry at redhat.com