From: Tom Pantelis Date: Wed, 22 Aug 2018 16:45:23 +0000 (-0400) Subject: Lower warn level in AbstractInvokableServiceMetadata X-Git-Tag: v3.0.0~45^2 X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=commitdiff_plain;h=fd1e91a593b7f00e158df8481f3adae9e033fe8f;p=mdsal.git Lower warn level in AbstractInvokableServiceMetadata The warning "interface interface X has no accptable entries, assuming it is satisfied" is emmitted quite often from RpcServiceMetadata, ie for every routed RPC I believe. I'm unclear as to why it filters out routed RPCs here and why it's a warning but we should at least reduce to debug to avoid the noise. Change-Id: I954a4b7c6b2a5e0d3fdbe7bbd2cc44b47ef01fdc Signed-off-by: Tom Pantelis --- diff --git a/src/main/java/org/opendaylight/controller/blueprint/ext/AbstractInvokableServiceMetadata.java b/src/main/java/org/opendaylight/controller/blueprint/ext/AbstractInvokableServiceMetadata.java index 30ee9aab5a..10ec16f1ab 100644 --- a/src/main/java/org/opendaylight/controller/blueprint/ext/AbstractInvokableServiceMetadata.java +++ b/src/main/java/org/opendaylight/controller/blueprint/ext/AbstractInvokableServiceMetadata.java @@ -91,7 +91,7 @@ abstract class AbstractInvokableServiceMetadata extends AbstractDependentCompone final Collection schemaPaths = RpcUtil.decomposeRpcService(rpcInterface, schemaContext, rpcFilter()); if (schemaPaths.isEmpty()) { - log.warn("{}: interface {} has no accptable entries, assuming it is satisfied", logName(), rpcInterface); + log.debug("{}: interface {} has no acceptable entries, assuming it is satisfied", logName(), rpcInterface); setSatisfied(); return; }