[infinispan-dev] test fine, but network exceptions are logged

[Galder Zamarreno]

On 10/08/2009 02:20 AM, Sanne Grinovero wrote:
> Hello,
> I'd appreciate some advice to understand if my tests are wrong, or if
> my environment is screwed.
>
> Having ported some of Łukasz's tests for the Lucene Directory, I have 6 tests:
> one test fails and others appear to work, but in all logs I see this
> kind of errors:
>
> 2009-10-08 00:55:37,493 ERROR [org.jgroups.protocols.UDP]
> (Timer-1,bluestar.tana-50817) failed sending message to null (138
> bytes)
> java.lang.Exception: dest=/228.10.10.10:45588 (141 bytes)
> 	at org.jgroups.protocols.UDP._send(UDP.java:213)
>
> when running "mvn clean test"

What's the root cause? Could you please show the entire stacktrace? It 
appears that there's some multicast issue. I don't think it would have 
much impact cos the issue is to do with JGroups diagnostics and you're 
running the tests with tcp.

Try putting enable_diagnostics="false" in 
core/src/main/resources/stacks/tcp.xml in the TCP protocol.

>
> I get environment info:
> ~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~
> bind.address = 127.0.0.1
> java.runtime.version = 1.6.0_16-b01
> java.runtime.name =Java(TM) SE Runtime Environment
> java.vm.version = 14.2-b01
> java.vm.vendor = Sun Microsystems Inc.
> os.name = Linux
> os.version = 2.6.30.8-64.fc11.x86_64
> sun.arch.data.model = 64
> sun.cpu.endian = little
> protocol.stack = tcp
> infinispan.marshaller.class = ${marshaller.class}
> java.net.preferIPv4Stack = true
> java.net.preferIPv6Stack = null
> MAVEN_OPTS = null
> ~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> So it appears the parent pom.xml is picked up correctly (as IPV4
> preference and bind-address properties are defined there)
>
> But if I run:
> mvn clean test -Djava.net.preferIPv4Stack=true -Dbind.address=127.0.0.1
>
> I get the same environment info but the tests behave differently: the
> mentioned exceptions are not being logged any more,
> but I get other kind of failures.

Hmmm, such as?

> Also disabling the parallel execution of tests solves this, but
> introduces other problems.
>
> I can't understand the effect of setting these parameters on
> infinispan/core, as many tests are failing already and have different
> errors each time I relaunch the testsuite.
> I really hate not being able to reproduce the errors, as they change
> often, so it doesn't make much sense to post some stacktrace.
> Is there any problem you might recognize in my environment?
>
> Are tests in trunk having some known problem?
>
> thanks in advance,
> Sanne
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

-- 
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache