INT-4259: ACorrelationMH: WARN group reschedule

JIRA: https://jira.spring.io/browse/INT-4259

Since DEBUG can switched off for the application, it becomes difficult
to determine the wrong configuration for the discard flow from
the scheduler thread.

* Change logging level to the `WARN` and log the full stack-trace as well
to give more information about the reason of rescheduling group for
`forceComplete`

**Cherry-pick to 4.3.x**

Conflicts:
	spring-integration-core/src/main/java/org/springframework/integration/aggregator/AbstractCorrelatingMessageHandler.java
Resolved.
This commit is contained in:
Artem Bilan
2017-05-02 17:19:21 -04:00
committed by Gary Russell
parent 89bd2b7f64
commit e8396c5dbf

View File

@@ -454,9 +454,9 @@ public abstract class AbstractCorrelatingMessageHandler extends AbstractMessageP
processForceRelease(groupId);
}
catch (MessageDeliveryException e) {
if (logger.isDebugEnabled()) {
logger.debug("The MessageGroup [ " + groupId +
"] is rescheduled by the reason: " + e.getMessage());
if (logger.isWarnEnabled()) {
logger.warn("The MessageGroup [ " + groupId +
"] is rescheduled by the reason of:", e);
}
scheduleGroupToForceComplete(groupId);
}
@@ -731,7 +731,7 @@ public abstract class AbstractCorrelatingMessageHandler extends AbstractMessageP
}
return messageSequenceSize.equals(getSequenceSize())
&& !(this.sourceGroup != null ? this.sourceGroup.containsSequence(messageSequenceNumber)
: containsSequenceNumber(this.getMessages(), messageSequenceNumber));
: containsSequenceNumber(this.getMessages(), messageSequenceNumber));
}
return true;
}