[Red Hat JIRA] (ISPN-12716) Hot Rod iteration shouldn't require ADMIN permission
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-12716?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-12716:
------------------------------
Fix Version/s: 13.0.0.Final
Resolution: Done
Status: Resolved (was: Pull Request Sent)
> Hot Rod iteration shouldn't require ADMIN permission
> ----------------------------------------------------
>
> Key: ISPN-12716
> URL: https://issues.redhat.com/browse/ISPN-12716
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, Security
> Affects Versions: 11.0.9.Final, 12.0.0.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 13.0.0.Final, 12.0.1.Final, 12.1.0.Dev01
>
>
> When try to iterate over keys/valis via Hot Rod client ({{RemoteCache}}), it fails with the following error:
> {noformat}
> org.infinispan.client.hotrod.exceptions.HotRodClientException: java.lang.SecurityException: ISPN000287: Unauthorized access: subject '<subject>' lacks 'ADMIN' permission
> {noformat}
> Debugging the server, it shows that {{DefaultIterationManager.start()}} retrieves the {{EncoderRegistry}} from {{GlobalComponentRegistry}}, which requires admin permissions. The retrieval shouldn't ask for admin (in this case).
> Original issue, from StackOverflow: https://stackoverflow.com/questions/66091661/infinispan-11-cannot-retriev...
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 4 months
[Red Hat JIRA] (ISPN-12630) SIFS does not set the seqId when loading index from disk
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-12630?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-12630:
------------------------------
Fix Version/s: 13.0.0.Final
12.1.0.Dev01
(was: 12.1.0.Final)
Resolution: Done
Status: Resolved (was: Pull Request Sent)
> SIFS does not set the seqId when loading index from disk
> --------------------------------------------------------
>
> Key: ISPN-12630
> URL: https://issues.redhat.com/browse/ISPN-12630
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 12.0.0.CR1
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 13.0.0.Final, 12.1.0.Dev01
>
>
> {{seqId}} is used to find which key's value is the most recent in the file. However, if the index is loaded from the disk, it is never set and the new entries are stored from {{seqId=1}}.
> Reads/Writes aren't affected but iteration relies on this to discard old values. It has the side effect of (possibly) returning multiple values for the same key.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 4 months
[Red Hat JIRA] (ISPN-12468) Prevent from unnecessary WARN messages ISPN000299 to acquire a lock for expiration handling
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12468?page=com.atlassian.jira.plugi... ]
Dan Berindei commented on ISPN-12468:
-------------------------------------
On the node where the lock acquisition failed, the lock acquisition timeout is also logged as an ERROR in addition to the WARN message in the description:
{noformat}
12:52:27,364+0100 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (expiration-thread--p5-t1) ISPN000136: Error executing command RemoveExpiredCommand on Cache 'PACS008_ACTIVATOR', writing keys [[4619b98805e540c3a39cfb3b377aa0e3|BARRIT26|2021-02-05T12:50:49.570646+01:00]]: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key [4619b98805e540c3a39cfb3b377aa0e3|BARRIT26|2021-02-05T12:50:49.570646+01:00] and requestor GlobalTransaction{id=185255, addr=ebaipm1tpbe91-48322, remote=false, xid=null, internalId=-1}. Lock is held by GlobalTransaction{id=183703, addr=ebaipm1tpbe91-48322, remote=false, xid=null, internalId=-1}
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:292) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:222) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.checkState(InfinispanLock.java:440) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.toInvocationStage(InfinispanLock.java:412) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.toInvocationStage(DefaultLockManager.java:252) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.toInvocationStage(DefaultLockManager.java:276) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.locking.AbstractLockingInterceptor.lockAndRecord(AbstractLockingInterceptor.java:277) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.checkPendingAndLockKey(AbstractTxLockingInterceptor.java:137) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockOrRegisterBackupLock(AbstractTxLockingInterceptor.java:65) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.locking.PessimisticLockingInterceptor.acquireLocalLock(PessimisticLockingInterceptor.java:92) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.locking.PessimisticLockingInterceptor.acquireLocalLockAndInvokeNext(PessimisticLockingInterceptor.java:285) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitDataWriteCommand(PessimisticLockingInterceptor.java:150) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitRemoveCommand(AbstractLockingInterceptor.java:102) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:64) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.write.RemoveExpiredCommand.acceptVisitor(RemoveExpiredCommand.java:46) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndFinally(BaseAsyncInterceptor.java:155) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.impl.TxInterceptor.handleWriteCommand(TxInterceptor.java:394) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.impl.TxInterceptor.visitRemoveCommand(TxInterceptor.java:232) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:64) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.write.RemoveExpiredCommand.acceptVisitor(RemoveExpiredCommand.java:46) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:59) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.DDAsyncInterceptor.handleDefault(DDAsyncInterceptor.java:53) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.partitionhandling.impl.PartitionHandlingInterceptor.handleSingleWrite(PartitionHandlingInterceptor.java:89) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.partitionhandling.impl.PartitionHandlingInterceptor.visitRemoveCommand(PartitionHandlingInterceptor.java:62) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:64) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.write.RemoveExpiredCommand.acceptVisitor(RemoveExpiredCommand.java:46) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:59) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.statetransfer.TransactionSynchronizerInterceptor.visitCommand(TransactionSynchronizerInterceptor.java:41) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndHandle(BaseAsyncInterceptor.java:190) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.statetransfer.StateTransferInterceptor.handleTxWriteCommand(StateTransferInterceptor.java:259) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.statetransfer.StateTransferInterceptor.handleWriteCommand(StateTransferInterceptor.java:249) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.statetransfer.StateTransferInterceptor.visitRemoveCommand(StateTransferInterceptor.java:108) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:64) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.write.RemoveExpiredCommand.acceptVisitor(RemoveExpiredCommand.java:46) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndFinally(BaseAsyncInterceptor.java:155) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.impl.CacheMgmtInterceptor.visitRemoveCommand(CacheMgmtInterceptor.java:484) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:64) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.write.RemoveExpiredCommand.acceptVisitor(RemoveExpiredCommand.java:46) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndExceptionally(BaseAsyncInterceptor.java:128) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.impl.InvocationContextInterceptor.visitCommand(InvocationContextInterceptor.java:90) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:61) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.DDAsyncInterceptor.handleDefault(DDAsyncInterceptor.java:53) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.DDAsyncInterceptor.visitRemoveCommand(DDAsyncInterceptor.java:64) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:64) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.commands.write.RemoveExpiredCommand.acceptVisitor(RemoveExpiredCommand.java:46) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.DDAsyncInterceptor.visitCommand(DDAsyncInterceptor.java:49) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.interceptors.impl.AsyncInterceptorChainImpl.invokeAsync(AsyncInterceptorChainImpl.java:226) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.cache.impl.InvocationHelper.doInvokeAsync(InvocationHelper.java:293) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.cache.impl.InvocationHelper.executeCommandAsyncWithInjectedTx(InvocationHelper.java:219) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.cache.impl.InvocationHelper.invokeAsync(InvocationHelper.java:146) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.cache.impl.CacheImpl.performRemoveExpiredCommand(CacheImpl.java:719) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.cache.impl.CacheImpl.removeLifespanExpired(CacheImpl.java:700) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.cache.impl.DecoratedCache.removeLifespanExpired(DecoratedCache.java:415) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.expiration.impl.ClusterExpirationManager.removeLifespan(ClusterExpirationManager.java:244) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.expiration.impl.ClusterExpirationManager.handleEitherExpiration(ClusterExpirationManager.java:268) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.expiration.impl.ClusterExpirationManager.handleLifespanExpireEntry(ClusterExpirationManager.java:240) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.expiration.impl.ClusterExpirationManager.purgeInMemoryContents(ClusterExpirationManager.java:159) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
at org.infinispan.expiration.impl.ClusterExpirationManager.processExpiration(ClusterExpirationManager.java:100) [infinispan-core-11.0.9.Final-redhat-00001.jar:11.0.9.Final-redhat-00001]
{noformat}
> Prevent from unnecessary WARN messages ISPN000299 to acquire a lock for expiration handling
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-12468
> URL: https://issues.redhat.com/browse/ISPN-12468
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 12.0.0.Dev05
> Reporter: Wolf-Dieter Fink
> Priority: Minor
>
> If locking will fail to remove expired entries this can be ignored, but the WARN message with stacktrace is confusing for the user and might fill the logfile.
> So the following exception should be at DEBUG level if the cause is expiration
> {noformat}
> WARN [org.infinispan.persistence.manager.PersistenceManagerImpl] (pool-14-thread-1) ISPN000026: Caught exception purging data container!: java.util.concurrent.CompletionException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
> at org.infinispan.util.concurrent.CompletionStages.join(CompletionStages.java:83)
> at org.infinispan.expiration.impl.InternalExpirationManager.handleInStoreExpiration(InternalExpirationManager.java:60)
> ...
> Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
> at org.infinispan.remoting.transport.ResponseCollectors.wrapRemoteException(ResponseCollectors.java:28)
> at org.infinispan.remoting.transport.ValidSingleResponseCollector.withException(ValidSingleResponseCollector.java:37)
> at org.infinispan.remoting.transport.ValidSingleResponseCollector.addResponse(ValidSingleResponseCollector.java:21)
> at org.infinispan.remoting.transport.impl.SingleTargetRequest.receiveResponse(SingleTargetRequest.java:52)
> at org.infinispan.remoting.transport.impl.SingleTargetRequest.onResponse(SingleTargetRequest.java:35)
> at org.infinispan.remoting.transport.impl.RequestRepository.addResponse(RequestRepository.java:52)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.processResponse(JGroupsTransport.java:1380)
> ...
> Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key WrappedByteArray\{bytes=[B0x0..[], hashCode=-123} and requestor CommandInvocation:node2. Lock is held by CommandInvocation:node1:12720556
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288)
> ...
> at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:66)
> ... more
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 4 months
[Red Hat JIRA] (ISPN-12468) Prevent from unnecessary WARN messages ISPN000299 to acquire a lock for expiration handling
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12468?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12468:
--------------------------------
Description:
If locking will fail to remove expired entries this can be ignored, but the WARN message with stacktrace is confusing for the user and might fill the logfile.
So the following exception should be at DEBUG level if the cause is expiration
{noformat}
WARN [org.infinispan.persistence.manager.PersistenceManagerImpl] (pool-14-thread-1) ISPN000026: Caught exception purging data container!: java.util.concurrent.CompletionException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
at org.infinispan.util.concurrent.CompletionStages.join(CompletionStages.java:83)
at org.infinispan.expiration.impl.InternalExpirationManager.handleInStoreExpiration(InternalExpirationManager.java:60)
...
Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
at org.infinispan.remoting.transport.ResponseCollectors.wrapRemoteException(ResponseCollectors.java:28)
at org.infinispan.remoting.transport.ValidSingleResponseCollector.withException(ValidSingleResponseCollector.java:37)
at org.infinispan.remoting.transport.ValidSingleResponseCollector.addResponse(ValidSingleResponseCollector.java:21)
at org.infinispan.remoting.transport.impl.SingleTargetRequest.receiveResponse(SingleTargetRequest.java:52)
at org.infinispan.remoting.transport.impl.SingleTargetRequest.onResponse(SingleTargetRequest.java:35)
at org.infinispan.remoting.transport.impl.RequestRepository.addResponse(RequestRepository.java:52)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.processResponse(JGroupsTransport.java:1380)
...
Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key WrappedByteArray\{bytes=[B0x0..[], hashCode=-123} and requestor CommandInvocation:node2. Lock is held by CommandInvocation:node1:12720556
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288)
...
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:66)
... more
{noformat}
was:
If locking will fail to remove expired entries this can be ignored, but the WARN message with stacktrace is confusing for the user and might fill the logfile.
So the following exception should be at DEBUG level if the cause is expiration
~~~
WARN [org.infinispan.persistence.manager.PersistenceManagerImpl] (pool-14-thread-1) ISPN000026: Caught exception purging data container!: java.util.concurrent.CompletionException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
at org.infinispan.util.concurrent.CompletionStages.join(CompletionStages.java:83)
at org.infinispan.expiration.impl.InternalExpirationManager.handleInStoreExpiration(InternalExpirationManager.java:60)
...
Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
at org.infinispan.remoting.transport.ResponseCollectors.wrapRemoteException(ResponseCollectors.java:28)
at org.infinispan.remoting.transport.ValidSingleResponseCollector.withException(ValidSingleResponseCollector.java:37)
at org.infinispan.remoting.transport.ValidSingleResponseCollector.addResponse(ValidSingleResponseCollector.java:21)
at org.infinispan.remoting.transport.impl.SingleTargetRequest.receiveResponse(SingleTargetRequest.java:52)
at org.infinispan.remoting.transport.impl.SingleTargetRequest.onResponse(SingleTargetRequest.java:35)
at org.infinispan.remoting.transport.impl.RequestRepository.addResponse(RequestRepository.java:52)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.processResponse(JGroupsTransport.java:1380)
...
Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key WrappedByteArray\{bytes=[B0x0..[], hashCode=-123} and requestor CommandInvocation:node2. Lock is held by CommandInvocation:node1:12720556
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288)
...
at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:66)
... more
~~~
> Prevent from unnecessary WARN messages ISPN000299 to acquire a lock for expiration handling
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-12468
> URL: https://issues.redhat.com/browse/ISPN-12468
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 12.0.0.Dev05
> Reporter: Wolf-Dieter Fink
> Priority: Minor
>
> If locking will fail to remove expired entries this can be ignored, but the WARN message with stacktrace is confusing for the user and might fill the logfile.
> So the following exception should be at DEBUG level if the cause is expiration
> {noformat}
> WARN [org.infinispan.persistence.manager.PersistenceManagerImpl] (pool-14-thread-1) ISPN000026: Caught exception purging data container!: java.util.concurrent.CompletionException: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
> at org.infinispan.util.concurrent.CompletionStages.join(CompletionStages.java:83)
> at org.infinispan.expiration.impl.InternalExpirationManager.handleInStoreExpiration(InternalExpirationManager.java:60)
> ...
> Caused by: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node2, see cause for remote stack trace
> at org.infinispan.remoting.transport.ResponseCollectors.wrapRemoteException(ResponseCollectors.java:28)
> at org.infinispan.remoting.transport.ValidSingleResponseCollector.withException(ValidSingleResponseCollector.java:37)
> at org.infinispan.remoting.transport.ValidSingleResponseCollector.addResponse(ValidSingleResponseCollector.java:21)
> at org.infinispan.remoting.transport.impl.SingleTargetRequest.receiveResponse(SingleTargetRequest.java:52)
> at org.infinispan.remoting.transport.impl.SingleTargetRequest.onResponse(SingleTargetRequest.java:35)
> at org.infinispan.remoting.transport.impl.RequestRepository.addResponse(RequestRepository.java:52)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.processResponse(JGroupsTransport.java:1380)
> ...
> Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 0 milliseconds for key WrappedByteArray\{bytes=[B0x0..[], hashCode=-123} and requestor CommandInvocation:node2. Lock is held by CommandInvocation:node1:12720556
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288)
> ...
> at org.infinispan.commands.Visitor.visitRemoveExpiredCommand(Visitor.java:66)
> ... more
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 4 months
[Red Hat JIRA] (ISPN-12320) Disabling authentication per endpoint is not possible
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12320?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12320:
--------------------------------
Status: Open (was: New)
> Disabling authentication per endpoint is not possible
> -----------------------------------------------------
>
> Key: ISPN-12320
> URL: https://issues.redhat.com/browse/ISPN-12320
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod, REST, Security
> Affects Versions: 12.0.0.Dev03
> Reporter: Ryan Emerson
> Assignee: Tristan Tarrant
> Priority: Major
>
> Currently it's not possible to configure the server so that authentication is only enabled on either the REST or HotRod endpoint. When utilising authentication elements on either endpoint it's mandatory for the `<endpoints ...` `security-realm` attribute to be set, otherwise the following exception is thrown:
> {code:java}
> 11:04:12,367 FATAL (main) [org.infinispan.SERVER] ISPN080028: Infinispan Server failed to start org.infinispan.commons.CacheConfigurationException: ISPN080021: Authentication cannot be configured without a security realm
> at org.infinispan.server.configuration.hotrod.HotRodServerConfigurationParser.parseAuthentication(HotRodServerConfigurationParser.java:204)
> at org.infinispan.server.configuration.hotrod.HotRodServerConfigurationParser.parseHotRodConnector(HotRodServerConfigurationParser.java:111)
> at org.infinispan.server.configuration.hotrod.HotRodServerConfigurationParser.readElement(HotRodServerConfigurationParser.java:56)
> at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:224)
> at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:60)
> at org.infinispan.server.configuration.ServerConfigurationParser.parseEndpoints(ServerConfigurationParser.java:1126)
> at org.infinispan.server.configuration.ServerConfigurationParser.parseServerElements(ServerConfigurationParser.java:121)
> at org.infinispan.server.configuration.ServerConfigurationParser.readElement(ServerConfigurationParser.java:92)
> at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:224)
> at org.infinispan.configuration.parsing.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:60)
> at org.infinispan.configuration.parsing.Parser.readElement(Parser.java:127)
> at org.infinispan.configuration.parsing.ParserRegistry.parseElement(ParserRegistry.java:224)
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:194)
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:180)
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:169)
> at org.infinispan.server.Server.parseConfiguration(Server.java:270)
> at org.infinispan.server.Server.<init>(Server.java:198)
> at org.infinispan.server.Bootstrap.runInternal(Bootstrap.java:138)
> at org.infinispan.server.tool.Main.run(Main.java:98)
> at org.infinispan.server.Bootstrap.main(Bootstrap.java:40)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.infinispan.server.loader.Loader.run(Loader.java:76)
> at org.infinispan.server.loader.Loader.main(Loader.java:39)
> {code}
> However, setting the security-realm attribute means that authentication is automatically configured for endpoints that do no have a {{<authentication>}} element set. So the following xml always results in REST authentication being enabled.
> {code:xml}
> <endpoints socket-binding="default" security-realm="default">
> <hotrod-connector name="hotrod">
> <authentication>
> <sasl mechanisms="SCRAM-SHA-512 SCRAM-SHA-384 SCRAM-SHA-256 SCRAM-SHA-1 DIGEST-SHA-512 DIGEST-SHA-384 DIGEST-SHA-256 DIGEST-SHA DIGEST-MD5 PLAIN" />
> </authentication>
> </hotrod-connector>
> <rest-connector name="rest"/>
> </endpoints>
> {code}
> It should be possible for REST auth to be disabled and HotRod auth enabled and vice-versa.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 4 months
[Red Hat JIRA] (ISPN-12718) Add addtional DEBUG logs to Backup/Restore operations
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-12718:
-----------------------------------
Summary: Add addtional DEBUG logs to Backup/Restore operations
Key: ISPN-12718
URL: https://issues.redhat.com/browse/ISPN-12718
Project: Infinispan
Issue Type: Enhancement
Components: Backup/Restore
Affects Versions: 12.0.0.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
Fix For: 12.1.0.Final, 12.0.1.Final
Currently it's not possible to tell from the logs which entries were included in a backup/restore operation from the debug logs.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 4 months