September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10558) ServerNG: add database rules

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10558: -------------------------------------- Summary: ServerNG: add database rules Key: ISPN-10558 URL: https://issues.jboss.org/browse/ISPN-10558 Project: Infinispan Issue Type: Enhancement Components: Server, Test Suite - Server Affects Versions: 10.0.0.CR1 Reporter: Tristan Tarrant We need a JDBC database rules for server tests which would be responsible for setting up a database server. There should be three modes of operation: * embedded databases (such as H2) * containerized databases (usually the open source ones) * externally managed databases The rules should ensure that the necessary JDBC driver are copied to the $SERVER_HOME/server/lib directory and that the server is started with an appropriate Agroal configuration -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10557) extended-statistics org.infinispan.stats package overlaps with core

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10557?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10557: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7266 > extended-statistics org.infinispan.stats package overlaps with core > ------------------------------------------------------------------- > > Key: ISPN-10557 > URL: https://issues.jboss.org/browse/ISPN-10557 > Project: Infinispan > Issue Type: Bug > Components: Build, Core > Affects Versions: 10.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR2 > > > The org.infinispan.stats package is used both within infinispan-core and infinispan-extended-statistics. This shold be fixed in the extended statistics module -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10557) extended-statistics org.infinispan.stats package overlaps with core

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10557?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10557: ----------------------------------- Status: Open (was: New) > extended-statistics org.infinispan.stats package overlaps with core > ------------------------------------------------------------------- > > Key: ISPN-10557 > URL: https://issues.jboss.org/browse/ISPN-10557 > Project: Infinispan > Issue Type: Bug > Components: Build, Core > Affects Versions: 10.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR2 > > > The org.infinispan.stats package is used both within infinispan-core and infinispan-extended-statistics. This shold be fixed in the extended statistics module -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10557) extended-statistics org.infinispan.stats package overlaps with core

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10557: -------------------------------------- Summary: extended-statistics org.infinispan.stats package overlaps with core Key: ISPN-10557 URL: https://issues.jboss.org/browse/ISPN-10557 Project: Infinispan Issue Type: Bug Components: Build, Core Affects Versions: 10.0.0.CR1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR2 The org.infinispan.stats package is used both within infinispan-core and infinispan-extended-statistics. This shold be fixed in the extended statistics module -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10556) Javadoc errors

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10556?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10556: ----------------------------------- Status: Open (was: New) > Javadoc errors > -------------- > > Key: ISPN-10556 > URL: https://issues.jboss.org/browse/ISPN-10556 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Query > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR2 > > > The build is failing at the javadoc phase: > [ERROR] /home_local/workspace/regression-build-infinispan/infinispan/object-filter/src/main/java/org/infinispan/objectfilter/impl/ql/QueryRendererDelegate.java:20: error: package org.antlr.runtime.tree does not exist -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10556) Javadoc errors

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10556: -------------------------------------- Summary: Javadoc errors Key: ISPN-10556 URL: https://issues.jboss.org/browse/ISPN-10556 Project: Infinispan Issue Type: Bug Components: Documentation-Query Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR2 The build is failing at the javadoc phase: [ERROR] /home_local/workspace/regression-build-infinispan/infinispan/object-filter/src/main/java/org/infinispan/objectfilter/impl/ql/QueryRendererDelegate.java:20: error: package org.antlr.runtime.tree does not exist -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10554) Operator Docs: Modularization Standards

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10554?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10554: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/142, https://github.com/infinispan/infinispan-operator/pull/141 > Operator Docs: Modularization Standards > --------------------------------------- > > Key: ISPN-10554 > URL: https://issues.jboss.org/browse/ISPN-10554 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Adjust Operator docs as modular to align with the rest of the Infinispan doc set. -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10367) Possible loss of (pessimistic) lock if a transaction will reach timeout and/or is removed

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10367?page=com.atlassian.jira.plugin... ] Dan Berindei commented on ISPN-10367: ------------------------------------- [~pruivo] just to clarify, {{FD_SOCK}} does **not** prevent view changes while the socket is open. It doesn not suspect nodes itself while the socket is open, but if {{FD_ALL}} doesn't receive a heartbeat it will suspect the node, and only {{VERIFY_SUSPECT}} receiving an ack from the node can prevent it from being removed from the view. > Possible loss of (pessimistic) lock if a transaction will reach timeout and/or is removed > ----------------------------------------------------------------------------------------- > > Key: ISPN-10367 > URL: https://issues.jboss.org/browse/ISPN-10367 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.Beta3, 9.4.15.Final > Environment: Infinispan with pessimistic locking enabled > Reporter: Wolf-Dieter Fink > Assignee: Pedro Ruivo > Priority: Critical > Attachments: StressApp.zip > > > If entries are locked, no matter whether it was done by FORCE_WRITE_LOCK flag or getAdvancedCache().lock(key), and the lock is hold longer than the current Tx timeout setting (.completedTxTimeout(...) ) the transacaction might be removed > - if the node is blocked and expelled from the cluster (and join back later) > - the thread processing the lock will take longer than the Tx-timeout setting > This force to remove the Tx and free the lock. > An indicator is the Exception below which will be shown if the Tx is timing out, it is not a (remote) access timout. > If the originator is back after this this (ongoing) Tx is assumed new and it will continue by accident without lock. > This can cause unexpected inconsistency! > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (EJB timer - 13) ISPN000136: Error executing command LockControlCommand, writing keys []: org.infinispan.util.concurrent.TimeoutException: Replication timeout for lt-33828 > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:803) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$1(JGroupsTransport.java:641) > at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) > at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ERROR [org.jboss.as.ejb3.timer] (EJB timer - 13) WFLYEJB0020: Error invoking timeout for timer: [id=8a53d2c3-190d-4c74-9327-8e7554e1df2c timedObjectId=embeddedStressTest-ejb.embeddedStressTest-ejb.CacheAccessSingletonBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@72c41b07 initialExpiration=Fri Jun 28 10:56:16 CEST 2019 intervalDuration(in milli sec)=1 nextExpiration=Fri Jun 28 10:56:43 CEST 2019 timerState=IN_TIMEOUT info=org.infinispan.wfink.stress.TimerInfo@47ae2053]: javax.ejb.EJBException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for lt-33828 > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:146) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > at org.jboss.as.ejb3.component.singleton.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:106) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:99) > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:109) > at org.jboss.as.ejb3.timerservice.TimerTask.invokeBeanMethod(TimerTask.java:189) > at org.jboss.as.ejb3.timerservice.TimerTask.callTimeout(TimerTask.java:185) > at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:159) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1304) > at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:494) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: org.infinispan.util.concurrent.TimeoutException: Replication timeout for lt-33828 > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:803) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$1(JGroupsTransport.java:641) > at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) > at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10555) Passivating an entry puts the wrong created time.

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10555?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10555: ------------------------------ Fix Version/s: 10.0.0.Beta5 > Passivating an entry puts the wrong created time. > ------------------------------------------------- > > Key: ISPN-10555 > URL: https://issues.jboss.org/browse/ISPN-10555 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Beta5 > > > Passivating an entry accidentally puts the expirty time instead of the created time when passivating. This can cause the entry to expire at the incorrect time. > https://github.com/infinispan/infinispan/blob/0301f662e4c5a81bc08fb572772... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10555) Passivating an entry puts the wrong created time.

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10555?page=com.atlassian.jira.plugin... ] Will Burns commented on ISPN-10555: ----------------------------------- This has been fixed on master in https://github.com/infinispan/infinispan/commit/bd580e6254c1fc7c6cda4e43e... > Passivating an entry puts the wrong created time. > ------------------------------------------------- > > Key: ISPN-10555 > URL: https://issues.jboss.org/browse/ISPN-10555 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Beta5 > > > Passivating an entry accidentally puts the expirty time instead of the created time when passivating. This can cause the entry to expire at the incorrect time. > https://github.com/infinispan/infinispan/blob/0301f662e4c5a81bc08fb572772... -- This message was sent by Atlassian Jira (v7.13.5#713005)

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2019