July 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11286) compute(...) is not working without any error message if expiration parameter is used

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11286?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-11286: -------------------------------------- Assignee: Will Burns > compute(...) is not working without any error message if expiration parameter is used > ------------------------------------------------------------------------------------- > > Key: ISPN-11286 > URL: https://issues.redhat.com/browse/ISPN-11286 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > Attachments: Book.java, LibraryManager.java > > > If the compute operation is used with expiration parameters the value is not applied without any error message! > compute() without expiration or a put() with expiration will work correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11336) Infinispan BOM should only have dependency management

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11336?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11336: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Infinispan BOM should only have dependency management > ----------------------------------------------------- > > Key: ISPN-11336 > URL: https://issues.redhat.com/browse/ISPN-11336 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.1.2.Final > Reporter: Stéphane Nicoll > Assignee: Pedro Ruivo > Priority: Major > Fix For: 12.0.0.Dev01 > > > The BOM has a {{pluginManagement}} section that's a bit misleading since Maven isn't going to do anything with it. > It is also invalid at the moment per the following: > {code:xml} > <plugin> > <groupId>org.infinispan.maven-plugins</groupId> > <artifactId>protocol-parser-generator</artifactId> > <version>${version.infinispan.maven-plugins}</version> > </plugin> > {code} > This artifact does not seem to be published anymore. Using the BOM with resolution leads to > {noformat} > [WARNING] The POM for org.infinispan:infinispan-protocol-parser-generator-maven-plugin:jar:10.1.1.Final is missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for org.infinispan:infinispan-protocol-parser-generator-maven-plugin:10.1.1.Final: Plugin org.infinispan:infinispan-protocol-parser-generator-maven-plugin:10.1.1.Final or one of its dependencies could not be resolved: Failure to find org.infinispan:infinispan-protocol-parser-generator-maven-plugin:jar:10.1.1.Final in https://repo.spring.io/milestone was cached in the local repository, resolution will not be reattempted until the update interval of spring-milestones has elapsed or updates are forced > {noformat} -- 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: ------------------------------------- I created job https://ci.infinispan.org/job/InfinispanAlternateBuilds/job/InfinispanTcp/ > 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

[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 updated ISPN-12109: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8551 > 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

[JBoss JIRA] (ISPN-12114) Server defaults and embeddedd defaults should be the same

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12114?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12114: -------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: (was: https://github.com/infinispan/infinispan/pull/8551) > Server defaults and embeddedd defaults should be the same > --------------------------------------------------------- > > Key: ISPN-12114 > URL: https://issues.redhat.com/browse/ISPN-12114 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final > > > The server has an {{infinispan-defaults.xml}} file with some configuration templates that are available by default in the server and are automatically applied to all the caches defined in the server configuration XML. > These configuration templates change e.g. the lock acquisition timeout and state transfer timeout to match the old WildFly server's defaults, but these default values are not documented. > {{EmbeddedCacheManagerAdmin}} and {{RemoteCacheManagerAdmin}} also mention "the configuration marked as default on the container/server", but we don't really have that any more, as the default cache's configuration is no longer used as a template. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12114) Server defaults and embeddedd defaults should be the same

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12114?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12114: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8551 > Server defaults and embeddedd defaults should be the same > --------------------------------------------------------- > > Key: ISPN-12114 > URL: https://issues.redhat.com/browse/ISPN-12114 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final > > > The server has an {{infinispan-defaults.xml}} file with some configuration templates that are available by default in the server and are automatically applied to all the caches defined in the server configuration XML. > These configuration templates change e.g. the lock acquisition timeout and state transfer timeout to match the old WildFly server's defaults, but these default values are not documented. > {{EmbeddedCacheManagerAdmin}} and {{RemoteCacheManagerAdmin}} also mention "the configuration marked as default on the container/server", but we don't really have that any more, as the default cache's configuration is no longer used as a template. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12114) Server defaults and embeddedd defaults should be the same

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-12114?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-12114: -------------------------------- Status: Open (was: New) > Server defaults and embeddedd defaults should be the same > --------------------------------------------------------- > > Key: ISPN-12114 > URL: https://issues.redhat.com/browse/ISPN-12114 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 12.0.0.Final > > > The server has an {{infinispan-defaults.xml}} file with some configuration templates that are available by default in the server and are automatically applied to all the caches defined in the server configuration XML. > These configuration templates change e.g. the lock acquisition timeout and state transfer timeout to match the old WildFly server's defaults, but these default values are not documented. > {{EmbeddedCacheManagerAdmin}} and {{RemoteCacheManagerAdmin}} also mention "the configuration marked as default on the container/server", but we don't really have that any more, as the default cache's configuration is no longer used as a template. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12121) Deprecate custom objects to JSON automatic conversion

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12121?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12121: ------------------------------------- Description: This is problematic for the native server as there is no way of knowing ahead the user types. Two options here: * Redirect users to protostream, that supports JSON natively * Provide a way to plug custom serializers to JSON was: This is problematic for the native server as there is no way of knowing ahead the user types. Two options here: * Redirect users to protostream, that support JSON natively * Provide a way to plug custom serializers to JSON > Deprecate custom objects to JSON automatic conversion > ----------------------------------------------------- > > Key: ISPN-12121 > URL: https://issues.redhat.com/browse/ISPN-12121 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 11.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 12.0.0.Final > > > This is problematic for the native server as there is no way of knowing ahead the user types. > Two options here: > * Redirect users to protostream, that supports JSON natively > * Provide a way to plug custom serializers to JSON -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12121) Deprecate custom objects to JSON automatic conversion

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-12121: ---------------------------------------- Summary: Deprecate custom objects to JSON automatic conversion Key: ISPN-12121 URL: https://issues.redhat.com/browse/ISPN-12121 Project: Infinispan Issue Type: Task Components: Server Affects Versions: 11.0.1.Final Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Fix For: 12.0.0.Final This is problematic for the native server as there is no way of knowing ahead the user types. Two options here: * Redirect users to protostream, that support JSON natively * Provide a way to plug custom serializers to JSON -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12111) Upgrade Hibernate Core/Search to 5.3.17.Final/5.10.7.Final

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-12111?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-12111: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade Hibernate Core/Search to 5.3.17.Final/5.10.7.Final > ---------------------------------------------------------- > > Key: ISPN-12111 > URL: https://issues.redhat.com/browse/ISPN-12111 > 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 > > > hibernate core =5.3.17.Final > hibernate search=5.10.7.Final > hibernate common=5.0.5.Final > hibernate hibernate-validator=6.0.20.Final -- 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