[
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)