Objects remain opened after timePerObject expires

[joemirizio]

Similar to #101, I'm not seeing the active object getting closed after timePerObject seconds. It isn't until the operator receives another message outside of the window that it gets closed. I am using version 2.2.6.

Looking at the trace logs, I can see ScheduledExecutorService - trigger object expiry in cache printing every 3 seconds. The nActiveObjects stays at 1, and the nClosedObjects is not increased.