jmc
jmc copied to clipboard
7455: Add support for jolokia JMX service connection
Setting back for review. The azure problem requires a fix in Jolokia.
Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol.
Progress
- [x] Commit message must refer to an issue
- [ ] Change must be properly reviewed (1 review required, with at least 1 Committer)
Issue
- JMC-7455: Add support for jolokia JMX service connection
Reviewing
Using git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jmc pull/332/head:pull/332
$ git checkout pull/332
Update a local copy of the PR:
$ git checkout pull/332
$ git pull https://git.openjdk.org/jmc pull/332/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 332
View PR using the GUI difftool:
$ git pr show -t 332
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/332.diff
Hi @skarsaune, welcome to this OpenJDK project and thanks for contributing!
We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed
in a comment in this pull request.
If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user skarsaune" as summary for the issue.
If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered
in a comment in this pull request.
@skarsaune do you have an JMC issue already or do you need help creating one?
@reinhapa : Please help creating an issue. I do not have access.
@skarsaune created JMC-7455 change the title to: 7455: Add support for jolokia JMX service connection
Webrevs
- 42: Full - Incremental (f9ea2f75)
- 41: Full - Incremental (b01b0b13)
- 40: Full (aefa414d)
- 39: Full - Incremental (cd51f88e)
- 38: Full - Incremental (ac841705)
- 37: Full - Incremental (31afef25)
- 36: Full - Incremental (21c94c5d)
- 35: Full (b524debd)
- 34: Full - Incremental (cbb06d89)
- 33: Full - Incremental (cfc26886)
- 32: Full - Incremental (a8d49090)
- 31: Full - Incremental (b33f15be)
- 30: Full - Incremental (1783f1bc)
- 29: Full (41501e7d)
- 28: Full - Incremental (7754b8be)
- 27: Full - Incremental (0028a086)
- 26: Full - Incremental (4ed92653)
- 25: Full (f8492788)
- 24: Full - Incremental (6d1d1d97)
- 23: Full - Incremental (7337f3a9)
- 22: Full - Incremental (350617e1)
- 21: Full - Incremental (0e9e1461)
- 20: Full - Incremental (f523ab38)
- 19: Full - Incremental (43d21621)
- 18: Full - Incremental (51c97824)
- 17: Full - Incremental (412ad827)
- 16: Full - Incremental (1dba9790)
- 15: Full - Incremental (96abdf1f)
- 14: Full (19dfea25)
- 13: Full - Incremental (854fed64)
- 12: Full (37d06c4e)
- 11: Full (dc047f95)
- 10: Full - Incremental (1b543ec0)
- 09: Full (eb20109f)
- 08: Full (da30ca75)
- 07: Full - Incremental (d64cb38a)
- 06: Full - Incremental (800a31d5)
- 05: Full - Incremental (955e3f8a)
- 04: Full (69bbb53a)
- 03: Full - Incremental (ab3085ce)
- 02: Full - Incremental (cf9a170b)
- 01: Full - Incremental (5af95b70)
- 00: Full (41ed1372)
I noticed the failed test run. Have used spotbugs to reformat. Re-run please.
I have corrected the last formatting and rebased with master. When I run the shell scripts from the github action definition on my mac, the first 3 run fine, however in scripts/runagenttests.sh there is a test failure (test-permissions). Should not be related to this PR however.
Fails on some platforms: "Unrecognized option: -XstartOnFirstThread" , will fix
⚠️ @skarsaune This pull request contains merges that bring in commits not present in the target repository. Since this is not a "merge style" pull request, these changes will be squashed when this pull request in integrated. If this is your intention, then please ignore this message. If you want to preserve the commit structure, you must change the title of this pull request to Merge <project>:<branch>
where <project>
is the name of another project in the OpenJDK organization (for example Merge jdk:master
).
It would be good to get a new CI run with the new way of handling OSGi dependencies
Hi again! Have been missing in action for a bit due to very critical phase at client, but have taken some time off my holiday to figure out a way to test the kubernetes support by mocking. If I could please have a CI test run to see that it works fine in the pipeline. Also rebased and updated to 8.3. cc: @thegreystone
Yeah, whenever I think I am done done, I think of something more to fix .... Set to draft now. Will probably draw the line in not too many days.
Hi @skarsaune! The master branch is now JMC 9, and now would be a great opportunity to get this in. Is there anything else you'd like to fix before I look at it again?
Great @thegreystone . Some actions I must take:
- Align with current master
- Do some manual testing in jmc after updating
- Ideally I would like to see if I can get a new release of Jolokia with some improvements
Edit: The kubernetes test is broken after I rebased onto master, and I haven't found out why yet. Tycho surefire complains that the test class is not found, however the compile stage reports 1 file compiled and I see it both (!) under target/classes AND target/test-classes. Anyone experienced anything like this before?
Manual tests look good. Solved a problem with stored credentials. Have requested merges and a release on the jolokia side. Still problems running the test though. Would it be possible to request a CI run on this PR?
Hi @skarsaune! Are you ready to make this PR ready for review?
Regarding the tests, typically the tests would be run in your fork, on commits to your branch. I can try running them on a few OSes locally here though.
-
Great if you can run the tests @thegreystone ! The jolokia tests run , but the Kubernetes tests not. They should be set up the same way, but it here is probably a silly error somewhere.
-
Thanks for checking in ☺️. I just asked for a release of jolokia. I hope to conclude that soon.
@skarsaune this pull request can not be integrated into master
due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:
git checkout jolokia-support
git fetch https://git.openjdk.org/jmc master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push
Jolokia is updated now. Merged with master and marking ready for review. PR is ready for slaughter 😉
Kuternetes tests still fail when I run ./build.sh --test
I need some assistance in understanding that one.
Found a functional problem with the Kubernetes test after upgrading to jolokia 1.7.2. will investigate ASAP
Edit: fixed https://github.com/openjdk/jmc/pull/332/commits/b33f15be2161c2eeae21890e61359387a1bdbb33
@thegreystone : I believe the previous review should be addressed. You can have a new look when you have time, and any assistance on running the test would be appreciated.
@skarsaune Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.
@skarsaune This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!
Still troubleshooting Kubernetes tests. Now they run , but fail with class not found on Apache commons http classes
Hi Martin! We're getting closer to the JMC release date. Is this something you're aiming to get into JMC 9?
Really interested by the jolokia support in JMC. Will be amazing to have it in the next release ;)
Sorry, missed this email. I'm still struggling with the classloading of the
kubernetes tests, and it has been hard to prioritze lately. It should be
reproducible running ./build.sh --test
on both linux and macos.
On Wed, Jan 3, 2024 at 7:26 PM Marcus Hirt @.***> wrote:
Hi Martin! We're getting closer to the JMC release date. Is this something you're aiming to get into JMC 9?
— Reply to this email directly, view it on GitHub https://github.com/openjdk/jmc/pull/332#issuecomment-1875787578, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQB2GSKG654E3LAYEABNSLYMWPDHAVCNFSM5GYUGXXKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBXGU3TQNZVG44A . You are receiving this because you were mentioned.Message ID: @.***>
Wondering if it is easiest to simply rip the PR in 2. Then we could merge joloka and struggle on with Kubernetes 😅
On Tue, Jan 23, 2024 at 7:25 AM Martin Skarsaune @.***> wrote:
Sorry, missed this email. I'm still struggling with the classloading of the kubernetes tests, and it has been hard to prioritze lately. It should be reproducible running
./build.sh --test
on both linux and macos.On Wed, Jan 3, 2024 at 7:26 PM Marcus Hirt @.***> wrote:
Hi Martin! We're getting closer to the JMC release date. Is this something you're aiming to get into JMC 9?
— Reply to this email directly, view it on GitHub https://github.com/openjdk/jmc/pull/332#issuecomment-1875787578, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQB2GSKG654E3LAYEABNSLYMWPDHAVCNFSM5GYUGXXKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBXGU3TQNZVG44A . You are receiving this because you were mentioned.Message ID: @.***>
replaced by https://github.com/openjdk/jmc/pull/548