From 25a125d47f46ef1b43bb7d17c9b39c547c3fd887 Mon Sep 17 00:00:00 2001
From: alrossi <arossi@otfrid.fnal.gov>
Date: Fri, 22 Jul 2016 09:36:56 -0500
Subject: [PATCH] resilience: fix alarm log level

The log level on this alarm was obviously set back to trace
(after a debugging session) by mistake.

The patch just changes it back from TRACE to ERROR.

Target: master
Request: 2.16
Acked-by: Paul
---
 .../dcache/resilience/handlers/FileTaskCompletionHandler.java   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/dcache-resilience/src/main/java/org/dcache/resilience/handlers/FileTaskCompletionHandler.java b/modules/dcache-resilience/src/main/java/org/dcache/resilience/handlers/FileTaskCompletionHandler.java
index eb4c944c38b..d6f0138f600 100644
--- a/modules/dcache-resilience/src/main/java/org/dcache/resilience/handlers/FileTaskCompletionHandler.java
+++ b/modules/dcache-resilience/src/main/java/org/dcache/resilience/handlers/FileTaskCompletionHandler.java
@@ -119,7 +119,7 @@ public void taskAborted(PnfsId pnfsId,
                                 maxRetries), e);
         }
 
-        LOGGER.trace(AlarmMarkerFactory.getMarker(
+        LOGGER.error(AlarmMarkerFactory.getMarker(
                                         PredefinedAlarm.FAILED_REPLICATION,
                                         pnfsId.toString()),
                         ABORT_REPLICATION_LOG_MESSAGE, pnfsId,