From 82c3adc1b3e7bc1088eae66050ce537cdada0b18 Mon Sep 17 00:00:00 2001 From: jusung Date: Thu, 20 Jan 2022 09:58:42 +0900 Subject: [PATCH] Change the exception handling logic There is no need to disconnect the socket when MESSAGE_PORT_ERROR_MAX_EXCEEDED error occurs. Change-Id: If34309c70a4549f5a655e1e6dc24cf87bfd6e874 Signed-off-by: jusung --- src/message_port_local.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/message_port_local.c b/src/message_port_local.c index c153444..f3b8096 100644 --- a/src/message_port_local.c +++ b/src/message_port_local.c @@ -1136,7 +1136,8 @@ out: if (fd_list) g_object_unref(fd_list); - if (ret != MESSAGE_PORT_ERROR_NONE) { + if (ret != MESSAGE_PORT_ERROR_NONE + && ret != MESSAGE_PORT_ERROR_MAX_EXCEEDED) { __key_info = NULL; __create_port_key_info(port_info, &__key_info); -- 2.7.4