Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-12468

Prevent from unnecessary WARN messages ISPN000299 to acquire a lock for expiration handling

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 13.0.0.Dev02
    • 12.0.0.Dev05
    • Core
    • None

    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

      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
      

       
       

      Attachments

        Activity

          People

            wburns@redhat.com Will Burns
            rhn-support-wfink Wolf Fink
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: