Closed cmebarrow closed 7 years ago
The PR looks good and seems to fix the problem. I didn't merge because I thought of adding an integration test.
@danibusu Any ideas for how to do the integration test? I thought it might be possible to do one by using a test service so it can examine the MX bean on the session. I am not sure it's possible though. The unit test does confirm the code change.
@dpwspoon Please merge this once the build completes. @danibusu has reviewed the changes and did an IT which I have added (JmxSessionIT).
Build failed twice in http.proxy service (ProxyServiceTest), filed as https://github.com/kaazing/gateway/issues/846
@danibusu @dpwspoon Please merge this now build has passed.
…nagementSessionStrategy.soSessionClosed to call doSessionClosedListeners on the sessionBean.
This should hopefully address the memory leak noted in ticket 912: the gateway is accumulating SessionMXBeanImpl instances.