chore(deps): bump jolokia.js from 2.0.0 to 2.0.1

[dependabot[bot]]

Bumps jolokia.js from 2.0.0 to 2.0.1.

Release notes

Sourced from jolokia.js's releases.

2.0.1

Jolokia 2.0.1 released. Changelog: https://github.com/jolokia/jolokia/milestone/18?closed=1

Changelog

Sourced from jolokia.js's changelog.

How to release Jolokia

There are two major steps required to release Jolokia:

• test, build and deploy Jolokia artifacts to Maven Central
• build and publish the website

Build and test

Building the project is a straightforward step. Jolokia is a Maven project and there's nothing unusual in build configuration, no exotic plugins involved and no antrun tasks.

mvn clean install

Maven build will involve invocation of standard unit and integration tests. If you have a firewall enabled, there may be problems running UDP multicast tests:

[ERROR] Tests run: 9, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 4.068 s <<< FAILURE! -- in TestSuite
[ERROR] org.jolokia.service.discovery.MulticastSocketListenerThreadTest.simple -- Time elapsed: 1.168 s <<< FAILURE!
java.lang.AssertionError: Exactly one in message with the send id should have been received expected [1] but found [0]
    at org.testng.Assert.fail(Assert.java:110)
    at org.testng.Assert.failNotEquals(Assert.java:1413)
    at org.testng.Assert.assertEqualsImpl(Assert.java:149)
    at org.testng.Assert.assertEquals(Assert.java:131)
    at org.testng.Assert.assertEquals(Assert.java:1240)
    at org.jolokia.service.discovery.MulticastSocketListenerThreadTest.simple(MulticastSocketListenerThreadTest.java:78)
...
[ERROR] org.jolokia.service.discovery.DiscoveryMulticastResponderTest.enabledLookup -- Time elapsed: 1.323 s <<< FAILURE!
java.lang.AssertionError: expected [false] but found [true]
at org.testng.Assert.fail(Assert.java:110)
at org.testng.Assert.failNotEquals(Assert.java:1413)
at org.testng.Assert.assertFalse(Assert.java:78)
at org.testng.Assert.assertFalse(Assert.java:88)
at org.jolokia.service.discovery.DiscoveryMulticastResponderTest.lookup(DiscoveryMulticastResponderTest.java:56)
at org.jolokia.service.discovery.DiscoveryMulticastResponderTest.enabledLookup(DiscoveryMulticastResponderTest.java:25)
...

This can be fixed with proper firewall configuration. Here's an example of nft command on Fedora with FedoraServer default zone:

# firewall-cmd --get-default-zone 
FedoraServer
nft add rule inet firewalld filter_IN_FedoraServer_allow ip daddr 239.192.48.84 accept
nft -a list chain inet firewalld filter_IN_FedoraServer_allow
table inet firewalld {
chain filter_IN_FedoraServer_allow { # handle 206
</tr></table>

... (truncated)

Commits

• 41466bb jolokia.js - v2.0.1
• e0967d0 Merge pull request #677 from tadayosi/676-list-mbeaninfoerror
• c54e72a jolokia.js - Add type for MBeanInfo error to ListResponse
• 08902b1 Merge branch 'pr674'
• f048110 Disable a test using ftp://ftp.redhat.com
• 435868a [build] Update maven-compiler-plugin to 3.13.0 and maven-gpg-plugin to 3.2.2
• 58e9799 Have KeyStoreUtil.updateWithServerPems load the full cert chain
• 9fc1b95 Bump version.org.springframework.boot from 3.2.3 to 3.2.4
• c2a4d72 Bump org.apache.maven.plugins:maven-assembly-plugin from 3.7.0 to 3.7.1
• 93172b3 Bump version.com.fasterxml.jackson.core from 2.16.1 to 2.17.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[phantomjinx]

Cannot upgrade at this time as management-api reports following error:

this.jolokia.search is not a function
search@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:295:18
mgmtUpdate/<@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:424:14
fulfilled@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:51:24
promise callback*step@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:63:76
rejected@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:58:13
promise callback*step@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:63:76
rejected@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:58:13
promise callback*step@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:63:76
__async/<@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:64:9
__async@webpack-internal:///../../node_modules/@hawtio/online-management-api/dist/index.js:48:10

Since jolokia.js is also depended on by @hawtio/react and is still at the level of 2.0.0, this maybe a conflict issue.

[phantomjinx]

@dependabot close