Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARTEMIS-2111 ManagementContext can leak #129

Conversation

clebertsuconic
Copy link
Contributor

(cherry picked from commit 744838f)
(cherry picked from commit 70a70f4)

downstream: ENTMQBR-1878

jbertram and others added 2 commits October 12, 2018 15:06
(cherry picked from commit 744838f)
(cherry picked from commit 70a70f4)

downstream: ENTMQBR-1878
fix pom to not use hard coded version
further close cf's

(cherry picked from commit 755f71e)
(cherry picked from commit 475ff33)

This is fixing tests broken after downstream ENTMQBR-1878 / ARTEMIS-2111
@andytaylor
Copy link
Contributor

@rvais @michalxo There is a test for this that:

  1. starts server with management connector
  2. stops the broker
  3. asserts that the connector is stopped

I think this is enough and would advise a qe ack.

One thing I would note is why regression testing hasn't picked this up, Im assuming that you always have a management connector configured?

@michalxo
Copy link
Contributor

michalxo commented Oct 15, 2018

Yes, we always have enabled JMX (in the past via artemis.profile), currently we're using connector-host & connector-port, as we use it for queue operations.

Clicked the wrong button... :-)

@andytaylor
Copy link
Contributor

merged

@andytaylor andytaylor closed this Oct 15, 2018
@clebertsuconic clebertsuconic deleted the ENTMQBR-1878 branch October 15, 2018 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants