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

[Client] JMX Sampler can't reconnect after the target JVM dies (avg prio) #34

Open
doriancransac opened this issue Apr 4, 2016 · 2 comments
Assignees

Comments

@doriancransac
Copy link
Contributor

Stopping and restarting the sampler doesn't seem to work. I have to open a new Session and Connection every time.

Can we please do this so that the client tries to recreate a clean JMX Connection and bind it to my existing djigger session when I stop-start the sampler?

Also I believe we lost the visual information that a target VM is no more reachable (might be dead).

@jeromecomte
Copy link
Contributor

I've disabled the auto-reconnect for JMX connections while fixing "[Client] Session tab opens even though connection failed (high prio) #24 ". I thought this won't be needed anymore. In this case I will reactivate it in a way that the first connection attempt throws an exception and the following auto-reconnect attempts not.

@doriancransac
Copy link
Contributor Author

I'm not talking about auto reconnect here.

I'm talking about trying again, when the user clicks on the stop & start sampler button again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants