From d102a8ac11aa0c98461762aca6d6d026b314395b Mon Sep 17 00:00:00 2001 From: Jonathan Locke Date: Tue, 26 Feb 2019 09:23:27 +0000 Subject: [PATCH] ENT-3059: RPC disconnect log entry changed to info When an RPC client disconnects from the RPC server, the log entry created now has its log level set to info rather than warning. It is perfectly normal for an RPC client to disconnect - only the RPC client knows if it was intentional. --- node/src/main/kotlin/net/corda/node/services/rpc/RPCServer.kt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/node/src/main/kotlin/net/corda/node/services/rpc/RPCServer.kt b/node/src/main/kotlin/net/corda/node/services/rpc/RPCServer.kt index 583a3e9705..1023e5a1ab 100644 --- a/node/src/main/kotlin/net/corda/node/services/rpc/RPCServer.kt +++ b/node/src/main/kotlin/net/corda/node/services/rpc/RPCServer.kt @@ -255,7 +255,7 @@ class RPCServer( val notificationType = artemisMessage.getStringProperty(ManagementHelper.HDR_NOTIFICATION_TYPE) require(notificationType == CoreNotificationType.BINDING_REMOVED.name){"Message contained notification type of $notificationType instead of expected ${CoreNotificationType.BINDING_REMOVED.name}"} val clientAddress = artemisMessage.getStringProperty(ManagementHelper.HDR_ROUTING_NAME) - log.warn("Detected RPC client disconnect on address $clientAddress, scheduling for reaping") + log.info("Detected RPC client disconnect on address $clientAddress, scheduling for reaping") invalidateClient(SimpleString(clientAddress)) }