[infinispan-issues] [JBoss JIRA] (ISPN-12109) TcpConnection.Receiver.run() blocking call

Dan Berindei (Jira) issues at jboss.org
Tue Jul 14 06:06:00 EDT 2020


    [ https://issues.redhat.com/browse/ISPN-12109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238632#comment-14238632 ] 

Dan Berindei commented on ISPN-12109:
-------------------------------------

By default tests (except for server tests) use the {{test-udp}} JGroups stack.

The {{test-unstable}} profile, along with all the other profiles in the parent {{pom.xml}}, use the {{tcp}} JGroups stack. That's why the blocking call only appears when running with one of these profiles.

We should remove the {{infinispan.cluster.stack}} property from all the profiles, and instead we should add an alternative job in Jenkins to run all the tests with TCP.

> TcpConnection.Receiver.run() blocking call
> ------------------------------------------
>
>                 Key: ISPN-12109
>                 URL: https://issues.redhat.com/browse/ISPN-12109
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core, Test Suite
>    Affects Versions: 11.0.1.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>            Priority: Major
>             Fix For: 12.0.0.Final, 11.0.2.Final
>
>
> {noformat}
> [TestSuiteProgress] Test failed: org.infinispan.distribution.rehash.WorkDuringJoinTest[DIST_SYNC, tx=false].BlockingChecker
> 22:28:37.967 [Connection.Receiver [127.0.0.1:34169 - 127.0.0.1:8001]-8,WorkDuringJoinTest-NodeC] ERROR org.infinispan.commons.test.TestSuiteProgress - Test failed: org.infinispan.distribution.rehash.WorkDuringJoinTest[DIST_SYNC, tx=false].BlockingChecker
> java.lang.AssertionError: Blocking call! java.net.SocketInputStream#socketRead0 on thread Thread[Connection.Receiver [127.0.0.1:34169 - 127.0.0.1:8001]-8,WorkDuringJoinTest-NodeC,5,ISPN-non-blocking-thread-group]
>         at org.infinispan.util.CoreTestBlockHoundIntegration.lambda$applyTo$0(CoreTestBlockHoundIntegration.java:45) ~[test-classes/:?]
>         at reactor.blockhound.BlockHound$Builder.lambda$install$8(BlockHound.java:383) ~[blockhound-1.0.3.RELEASE.jar:?]
>         at reactor.blockhound.BlockHoundRuntime.checkBlocking(BlockHoundRuntime.java:89) [?:?]
>         at java.net.SocketInputStream.socketRead0(SocketInputStream.java) [?:?]
>         at java.net.SocketInputStream.socketRead(SocketInputStream.java:115) [?:?]
>         at java.net.SocketInputStream.read(SocketInputStream.java:168) [?:?]
>         at java.net.SocketInputStream.read(SocketInputStream.java:140) [?:?]
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:252) [?:?]
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:271) [?:?]
>         at java.io.DataInputStream.readInt(DataInputStream.java:392) [?:?]
>         at org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:301) [jgroups-4.2.1.Final.jar:4.2.1.Final]
>         at java.lang.Thread.run(Thread.java:834) [?:?]
> {noformat}
> The blocking call doesn't always happen, but it appears to be more common in the unstable CI builds:
> https://ci.infinispan.org/job/InfinispanAlternateBuilds/job/InfinispanUnstable/130/#showFailuresLink



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the infinispan-issues mailing list