August 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (IPROTO-105) Accept annotated 'getters' that are not named according to the javabeans standard

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/IPROTO-105?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated IPROTO-105: ----------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #31) > Accept annotated 'getters' that are not named according to the javabeans standard > --------------------------------------------------------------------------------- > > Key: IPROTO-105 > URL: https://issues.jboss.org/browse/IPROTO-105 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9, 4.3.0.Final > > > While 'getLifespan()' is an accepted getter for 'lifespan' property, 'lifespan()' is not, but it would be very useful to add support for this case, also for such setter. > See infinispan's EmbeddedLifespanExpirableMetadata -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10161) ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10161?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10161: ----------------------------------- Sprint: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #30, DataGrid Sprint #31) > ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports > ------------------------------------------------------------------------------ > > Key: ISPN-10161 > URL: https://issues.jboss.org/browse/ISPN-10161 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.12.Final, 10.0.0.Final > Reporter: Diego Lovison > Assignee: Dan Berindei > Priority: Critical > > When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running. > From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae` > After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you will see no reports there. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9801) ClusterTopologyManagerImpl hangs when restarting a node with FORK

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9801?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9801: ---------------------------------- Sprint: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > ClusterTopologyManagerImpl hangs when restarting a node with FORK > ----------------------------------------------------------------- > > Key: ISPN-9801 > URL: https://issues.jboss.org/browse/ISPN-9801 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha1, 9.4.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > When a server is restarted with `kill -9` or similar, both the old node and the new one can be in the JGroups view for a while. Normally this shouldn't be a problem, but sometimes the new node doesn't receive the {{HeartBeatCommand}} and the coordinator cannot process any new view updates. > {noformat} > 14:29:19,981 INFO (jgroups-12,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [ClusterTopologyManagerImpl] Updating cluster members for all the caches. New list is [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [JGroupsTransport] Test-NodeA sending request 9 to all: org.infinispan.topology.HeartBeatCommand@1163beb6 > 14:29:19,986 TRACE (jgroups-6,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeC: SuccessfulResponse(null) > 14:29:19,987 TRACE (jgroups-9,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeD: SuccessfulResponse(null) > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [TCP_NIO2] Test-NodeE: received message batch of 1 messages from Test-NodeA > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: message Test-NodeA::39 was added to queue (not yet server) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: received Test-NodeA#38 > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: delivering Test-NodeA#38 > # not actually delivered :) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [MFC] Test-NodeA used 5 credits, 1999995 remaining > 14:29:20,149 INFO (ForkThread-1,ForkChannelRestartTest:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:21,119 DEBUG (testng-Test-1:[]) [ForkChannelRestartTest] Stopping channel Test-NodeB > 14:29:23,319 INFO (VERIFY_SUSPECT.TimerThread-32,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|5] (4) [Test-NodeA, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:23,320 TRACE (remote-thread-Test-NodeA-p2-t1:[]) [MultiTargetRequest] Target Test-NodeB of request 9 left the cluster view > {noformat} > So far, it looks like it's a JGroups bug similar to JGRP-2294, but we need to investigate further. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9828) Server defaults missing for UFC_NB and MFC_NB

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9828?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9828: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Server defaults missing for UFC_NB and MFC_NB > --------------------------------------------- > > Key: ISPN-9828 > URL: https://issues.jboss.org/browse/ISPN-9828 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.4.4.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Alpha3, 9.4.5.Final > > > JGroups' defaults are {{max_credits=500k}}, and Infinispan's server defaults ({{jgroups-defaults.xml}}) for the blocking UFC/MFC are {{max_credits=2m}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9808) Cluster executor commands don't end in Command

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9808?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9808: ---------------------------------- Sprint: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Cluster executor commands don't end in Command > ---------------------------------------------- > > Key: ISPN-9808 > URL: https://issues.jboss.org/browse/ISPN-9808 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.4.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Trivial > Fix For: 10.0.0.Alpha3 > > > Because they don't follow the naming convention of ending in {{Command}}, the {{bin/list_command_ids.py}} doesn't show cluster executor commands. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9835) Jenkinsfile snapshot deployment fails

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9835?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9835: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Jenkinsfile snapshot deployment fails > ------------------------------------- > > Key: ISPN-9835 > URL: https://issues.jboss.org/browse/ISPN-9835 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1 > > > {noformat} > 11:16:21.413 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project infinispan-checkstyle: The packaging for this project did not assign a file to the build artifact -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project infinispan-checkstyle: The packaging for this project did not assign a file to the build artifact > {noformat} > https://ci.infinispan.org/job/Infinispan/job/master/1005 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9818) Upgrade tomcat dependency version

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9818?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9818: ---------------------------------- Sprint: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Upgrade tomcat dependency version > --------------------------------- > > Key: ISPN-9818 > URL: https://issues.jboss.org/browse/ISPN-9818 > Project: Infinispan > Issue Type: Task > Affects Versions: 10.0.0.Alpha1, 9.4.4.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9699) Cluster member owning no data

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9699: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Cluster member owning no data > ----------------------------- > > Key: ISPN-9699 > URL: https://issues.jboss.org/browse/ISPN-9699 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 9.4.1.Final > Reporter: Thomas Segismont > Assignee: Katia Aresti > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment. > If you want a node to own no data at all, you could set this property on all declared caches. But this wouldn't work for internal caches anyway (locks, counters). > It would be nice to have a global switch. > This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster: > * there would be no data loss > * the cluster would be back in healthy state faster as no data would be moved around. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9863) Testsuite leaks threads

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9863?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9863: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Testsuite leaks threads > ----------------------- > > Key: ISPN-9863 > URL: https://issues.jboss.org/browse/ISPN-9863 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Alpha2, 9.4.5.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta3 > > > Some hotrod-client tests do not stop their {{RemoteCacheManager}} instances. This was fine before ISPN-8619, but the Netty-based client starts event loop threads and we need to stop them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9726) Document max clause property on boolean query

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9726?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9726: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Document max clause property on boolean query > --------------------------------------------- > > Key: ISPN-9726 > URL: https://issues.jboss.org/browse/ISPN-9726 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.0.Alpha1 > Reporter: Katia Aresti > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Final > > > Document the ability to override org.apache.lucene.search.BooleanQuery.maxClauseCount using infinispan.query.lucene.max-boolean-clauses JVM system property. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 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 August 2019