A minor bug is fixed. configuration log for flow time out is not displayed 'seconds'
Change-Id: Ieac1efc368c9a24d77a3e7982dc23f950deff3a5
Showing
1 changed file
with
1 additions
and
1 deletions
... | @@ -384,7 +384,7 @@ public class ReactiveForwarding { | ... | @@ -384,7 +384,7 @@ public class ReactiveForwarding { |
384 | ignoreIpv4McastPackets ? "enabled" : "disabled"); | 384 | ignoreIpv4McastPackets ? "enabled" : "disabled"); |
385 | } | 385 | } |
386 | flowTimeout = Tools.getIntegerProperty(properties, "flowTimeout", DEFAULT_TIMEOUT); | 386 | flowTimeout = Tools.getIntegerProperty(properties, "flowTimeout", DEFAULT_TIMEOUT); |
387 | - log.info("Configured. Flow Timeout is configured to {}", flowTimeout, " seconds"); | 387 | + log.info("Configured. Flow Timeout is configured to {} seconds", flowTimeout); |
388 | 388 | ||
389 | flowPriority = Tools.getIntegerProperty(properties, "flowPriority", DEFAULT_PRIORITY); | 389 | flowPriority = Tools.getIntegerProperty(properties, "flowPriority", DEFAULT_PRIORITY); |
390 | log.info("Configured. Flow Priority is configured to {}", flowPriority); | 390 | log.info("Configured. Flow Priority is configured to {}", flowPriority); | ... | ... |
-
Please register or login to post a comment