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

first spike of #125 to add a discovery mechanism to jolokia; which defau... #126

Closed
wants to merge 4 commits into from

Conversation

jstrachan
Copy link
Contributor

...lts to using files on the local machine (with keep-alive and tidying up of old files), a little JMX API and an experimental zeroconf plugin implementation.

currently only the JVM agent is supported; the challenge for the servlet/osgi agents is figuring out the jolokia URL before the servlet's been invoked...

…hich defaults to using files on the local machine (with keep-alive and tidying up of old files), a little JMX API and an experimental zeroconf plugin implementation.

currently only the JVM agent is supported; the challenge for the servlet/osgi agents is figuring out the jolokia URL before the servlet's been invoked...
@rhuss
Copy link
Member

rhuss commented Feb 4, 2014

I'll close that one and let's continue at #127. Snapshot is out, I target the weekend for a final 1.2.0 release with multicast support.

@rhuss rhuss closed this Feb 4, 2014
@davidkarlsen
Copy link

davidkarlsen commented Feb 13, 2017

@jstrachan @rhuss
I don't see this filebased discovery in the codebase any longer? Was it removed in favour of the multicast based solution? It would be a nice way to provide discovery when using jolokia in hawtio when deployed as a central .war

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

Successfully merging this pull request may close these issues.

None yet

3 participants