Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/365
@neykov previous build failure here could well be fixed by
https://github.com/apache/brooklyn-server/pull/368 - our `BrooklynLeakListener`
wasn't finding any left-behind management contexts to stop them, so our memory
usage might have been climbing over time.
Once that PR is confirmed to work in jenkins (including checking its stdout
that the leak-detector really executed) then I'll merge
https://github.com/apache/brooklyn-server/pull/368).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
