The support for no-local checking for published messages can cause 0-8/0-9/0-9-1 connections to be retained in memory after they are closed, until such time as the published messages are consumed. This is because the ProtocolSession itself is used for the reference check, meaning the messages will reference them and prevent the closed connection (and associated IO threads) being garbage collected until they are themselves are. Short term, the 0-8/0-9/0-9-1 no-local checking should be aligned with the 0-10 behaviour of using a seperate reference object associated with the connection, allowing the connection itself to be collected. Longer term, using the connection IDs etc instead of a separate object would seem more efficient.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||Ready To Review [ 10006 ]|
|Assignee||Robbie Gemmell [ gemmellr ]||Keith Wall [ k-wall ]|
|Status||Ready To Review [ 10006 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|