March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11430) Align microprofile metrics and config artifact versions with latest Wildfly

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11430?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11430: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Align microprofile metrics and config artifact versions with latest Wildfly > --------------------------------------------------------------------------- > > Key: ISPN-11430 > URL: https://issues.redhat.com/browse/ISPN-11430 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Affects Versions: 11.0.0.Alpha2 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev04 > > > Need to use the same versions used by Wildlfy latest for smooth integration: > microprofile-config-api: 1.4 > microprofile-metrics-api: 2.3 > smallrye-config: 1.6.2 > smallrye-metrics: 2.4.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11423) Dump information in panic scenarios

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11423?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11423: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Dump information in panic scenarios > ----------------------------------- > > Key: ISPN-11423 > URL: https://issues.redhat.com/browse/ISPN-11423 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Server > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev04 > > > When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. > The server should dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default. > These files can be sent to support via an SOS report. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11420) Drop OSGi testsuite

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11420?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11420: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Drop OSGi testsuite > ------------------- > > Key: ISPN-11420 > URL: https://issues.redhat.com/browse/ISPN-11420 > Project: Infinispan > Issue Type: Task > Components: Integration , Test Suite > Affects Versions: 11.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Dev04, 11.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11296) StateResponseOrderingTest uncaught IllegalArgumentException

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11296?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11296: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > StateResponseOrderingTest uncaught IllegalArgumentException > ----------------------------------------------------------- > > Key: ISPN-11296 > URL: https://issues.redhat.com/browse/ISPN-11296 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev04 > > > I think initially I wanted {{MatchCountMatcher}} to count from 1 and handle {{matchCount == 0}} as matching all invocations. All the callers now assume 0 is the first invocation, but the code kept working because the exception was not caught. > {noformat} > java.lang.IllegalStateException: State st:after_first_state_response exited twice > at org.infinispan.test.concurrent.StateSequencer.exit(StateSequencer.java:242) > at org.infinispan.test.concurrent.StateSequencer.advance(StateSequencer.java:316) > at org.infinispan.test.concurrent.StateSequencerUtil.advanceMultiple(StateSequencerUtil.java:103) > at org.infinispan.test.concurrent.InboundRpcSequencerAction$SequencerPerCacheInboundInvocationHandler.advance(InboundRpcSequencerAction.java:101) > at org.infinispan.test.concurrent.InboundRpcSequencerAction$SequencerPerCacheInboundInvocationHandler.lambda$handle$0(InboundRpcSequencerAction.java:82) > at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.invokedComplete(BaseBlockingRunnable.java:130) > at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.invoke(BaseBlockingRunnable.java:111) > at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.runAsync(BaseBlockingRunnable.java:72) > at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:41) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11395) Indexing configuration serialization broken

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11395?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11395: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Indexing configuration serialization broken > ------------------------------------------- > > Key: ISPN-11395 > URL: https://issues.redhat.com/browse/ISPN-11395 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 11.0.0.Alpha1, 10.1.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Dev04 > > > Some elements are not written to XML such as IndexedEntities and keytransformers -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11443) PersistenceManagerImpl thread checks need to be updated

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11443?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11443: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > PersistenceManagerImpl thread checks need to be updated > ------------------------------------------------------- > > Key: ISPN-11443 > URL: https://issues.redhat.com/browse/ISPN-11443 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > We added a NonBlockingThread interface that a non blocking thread implements in Infinispan. The checks need to be updated to the new thread pools. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11381) AdvancedCache.getGroup(key) may return incomplete results during state transfer

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11381?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11381: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > AdvancedCache.getGroup(key) may return incomplete results during state transfer > ------------------------------------------------------------------------------- > > Key: ISPN-11381 > URL: https://issues.redhat.com/browse/ISPN-11381 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev04 > > > {{AdvancedCache.getGroup(groupKey)}} returns all the keys that belong to a group. > If the originator is not an owner, the command is forwarded to the primary owner. If the originator is a primary or a backup owner for the group key, the command is executed locally. > During state transfer, a node may be a write owner for the group key but not a read owner. Currently {{GroupingInterceptor}} uses {{LocalizedCacheTopogy.isWriteOwner(groupKey)}} instead of {{isReadOwner(groupKey)}}, so it executes the command on the originator instead of forwarding it to the primary owner. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11300) Add internal metadata to cache entries

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11300?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11300: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Add internal metadata to cache entries > -------------------------------------- > > Key: ISPN-11300 > URL: https://issues.redhat.com/browse/ISPN-11300 > Project: Infinispan > Issue Type: Sub-task > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev04 > > > IRAC will need versioning to handle the async update correctly. This version is internal an it shouldn't be exposed to the user; so Metadata.version() can't be used. > Add internal metadata to cache entries. After this is fixed, the internal metadata will be added to the persistence and commands. > Also, optimistic transaction versions need to be moved here. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11295) InfinispanLock needs to block on a blocking thread but continue its operation on a non blocking thread

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11295?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11295: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > InfinispanLock needs to block on a blocking thread but continue its operation on a non blocking thread > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-11295 > URL: https://issues.redhat.com/browse/ISPN-11295 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > The InfinispanLock#toInvocationStage can block waiting for the lock. If this happens it needs to block on the blocking thread but then continue on a non blocking thread. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11450) SegmentedBoundedOffHeapDataContainer#ensureSize should be marked as okay to be blocking

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11450?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11450: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > SegmentedBoundedOffHeapDataContainer#ensureSize should be marked as okay to be blocking > --------------------------------------------------------------------------------------- > > Key: ISPN-11450 > URL: https://issues.redhat.com/browse/ISPN-11450 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > SegmentedBoundedOffHeapDataContainer uses the specific OffHeapDataContainer lock to check for eviction. This lock is short lived and thus can be marked as an exception for block hound. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020