-
Notifications
You must be signed in to change notification settings - Fork 474
Description
Describe the bug
In my project, Session is inactive becuase keep alive failure, but failed too many times,
Under normal circumstances, failureCount should be 2, Is it blocking when process response or other reason?
Expected behavior
my config is:
keepAliveFailuresAllowed is 2
keepAliveInterval is 5000 ms
keepAliveTimeout is 5000 ms
Logs and Packet Captures
09:13:05.848|W||7416|milo-shared-thread-pool-41515|o.e.m.o.s.c.t.u.UascClientMessageHandler|No pending request with requestId=413718 for PublishResponse
09:13:05.902|W||7416|milo-shared-thread-pool-41506|o.e.m.o.s.c.t.u.UascClientMessageHandler|No pending request with requestId=594462 for PublishResponse
09:13:05.933|E||7416|milo-netty-event-loop-18|o.e.m.o.s.c.t.u.UascClientMessageHandler|[remote=/10.21.103.118:4850] Exception caught: An established connection was aborted by the software in your host machine
09:13:05.934|W||7416|milo-shared-thread-pool-41350|o.e.m.o.s.c.SessionFsm|[43] Keep Alive failureCount=3 exceeds failuresAllowed=2
09:13:05.937|W||7416|milo-shared-thread-pool-41513|o.e.m.o.s.c.SessionFsm|[43] Keep Alive failureCount=88 exceeds failuresAllowed=2
09:13:05.937|W||7416|milo-shared-thread-pool-41513|o.e.m.o.s.c.SessionFsm|[43] Keep Alive failureCount=89 exceeds failuresAllowed=2
09:13:05.937|W||7416|milo-shared-thread-pool-41519|o.e.m.o.s.c.SessionFsm|[43] Keep Alive failureCount=90 exceeds failuresAllowed=2
09:13:05.937|W||7416|milo-shared-thread-pool-41519|o.e.m.o.s.c.SessionFsm|[43] Keep Alive failureCount=91 exceeds failuresAllowed=2
Additional context
milo version is v0.6.13.
my project is an client and conect eight server.