Bug #1832

Listener deactivation leaves receiving strategy registered on bus in case of socket transport

Added by J. Wienke about 10 years ago. Updated about 10 years ago.

Status:ResolvedStart date:04/04/2014
Priority:NormalDue date:
Assignee:J. Wienke% Done:

100%

Category:Java
Target version:rsb-0.9

Description

In the case of the socket transport, a deactivation of a listener seems to leave the event receiving strategy registered inside the socket bus dispatching logic. As a consequence, the receiving strategies are still called for all newly received events, do not process them and hence we have a memory leak.

Associated revisions

Revision 29ba0629
Added by J. Wienke about 10 years ago

Fix deactivation of SocketInPushConnector

Deregister all handlers etc correctly

fixes #1832

Revision a7021a86
Added by J. Wienke about 10 years ago

Backport: Fix deactivation of SocketInPushConnector

Deregister all handlers etc correctly

fixes #1832

Revision 5e7432fd
Added by J. Wienke about 10 years ago

Backport: Fix deactivation of SocketInPushConnector

Deregister all handlers etc correctly

fixes #1832

History

#1 Updated by J. Wienke about 10 years ago

  • Category set to Java
  • Status changed from New to In Progress
  • Assignee set to J. Wienke

#2 Updated by J. Wienke about 10 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset rsb-java|commit:29ba0629903455e6ca29a3a2623a72b240d7d3fc.

Also available in: Atom PDF