July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12120) Upgrade Log4J to 2.13.2

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12120?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12120: ------------------------------- Status: Open (was: New) > Upgrade Log4J to 2.13.2 > ----------------------- > > Key: ISPN-12120 > URL: https://issues.redhat.com/browse/ISPN-12120 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.4.19.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.20.Final > > > org.apache.logging.log4j=2.13.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12120) Upgrade Log4J to 2.13.2

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-12120: ---------------------------------- Summary: Upgrade Log4J to 2.13.2 Key: ISPN-12120 URL: https://issues.redhat.com/browse/ISPN-12120 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 9.4.19.Final Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 9.4.20.Final org.apache.logging.log4j=2.13.2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12041) ServerRunMode.FORKED mode doesn't work on Windows

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/ISPN-12041?page=com.atlassian.jira.plugi... ] Radoslav Husar commented on ISPN-12041: --------------------------------------- [~afield] Luckily, I haven't used it in a decade :) [~glira] [~dlovison] BTW Unrelated to Windows, we are also seeing a problem when a driver is used in subsequent tests and it looks like the locks are not cleared in time for the other test to start the Infinispan Server, e.g. {{Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/home/darranl/src/community/wildfly/testsuite/integration/clustering/target/infinispan-server-10.1.8.Final/server/data/___global.lck' for persistent global state}} which is currently tracked as WFLY-13664 – does that ring any bells? If I can come up with a simple reproducer I will share. > ServerRunMode.FORKED mode doesn't work on Windows > ------------------------------------------------- > > Key: ISPN-12041 > URL: https://issues.redhat.com/browse/ISPN-12041 > Project: Infinispan > Issue Type: Task > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Gustavo Lira Silva > Priority: Major > > Says it all: > > [https://github.com/infinispan/infinispan/blob/master/server/testdriver/co...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12119) Upgrade Jetty to 9.4.11.v20180605

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12119?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12119: ------------------------------- Status: Open (was: New) > Upgrade Jetty to 9.4.11.v20180605 > --------------------------------- > > Key: ISPN-12119 > URL: https://issues.redhat.com/browse/ISPN-12119 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.4.19.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.20.Final > > > org.eclipse.jetty=9.4.11.v20180605 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12119) Upgrade Jetty to 9.4.11.v20180605

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12119?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12119: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8548 > Upgrade Jetty to 9.4.11.v20180605 > --------------------------------- > > Key: ISPN-12119 > URL: https://issues.redhat.com/browse/ISPN-12119 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.4.19.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.20.Final > > > org.eclipse.jetty=9.4.11.v20180605 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12119) Upgrade Jetty to 9.4.11.v20180605

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-12119: ---------------------------------- Summary: Upgrade Jetty to 9.4.11.v20180605 Key: ISPN-12119 URL: https://issues.redhat.com/browse/ISPN-12119 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 9.4.19.Final Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 9.4.20.Final org.eclipse.jetty=9.4.11.v20180605 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12118) Upgrade Netty to 4.1.46.Final

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12118?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12118: ------------------------------- Status: Open (was: New) > Upgrade Netty to 4.1.46.Final > ----------------------------- > > Key: ISPN-12118 > URL: https://issues.redhat.com/browse/ISPN-12118 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.4.19.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.20.Final > > > io.netty=4.1.46.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12118) Upgrade Netty to 4.1.46.Final

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-12118?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-12118: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8547 > Upgrade Netty to 4.1.46.Final > ----------------------------- > > Key: ISPN-12118 > URL: https://issues.redhat.com/browse/ISPN-12118 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.4.19.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.20.Final > > > io.netty=4.1.46.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12118) Upgrade Netty to 4.1.46.Final

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-12118: ---------------------------------- Summary: Upgrade Netty to 4.1.46.Final Key: ISPN-12118 URL: https://issues.redhat.com/browse/ISPN-12118 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 9.4.19.Final Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 9.4.20.Final io.netty=4.1.46.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12109?page=com.atlassian.jira.plugi... ] 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/InfinispanUns... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2020