jmxutils icon indicating copy to clipboard operation
jmxutils copied to clipboard

Exporting JMX mbeans made easy

Results 16 jmxutils issues
Sort by recently updated
recently updated
newest added

That'd be useful when `TestingMBeanServer` is used to expose metrics using Airlift

ManagedClasses that are registered in exportedManagedClasses are never unregistered. This is causing an accumulation of memory.

Bumps [guava](https://github.com/google/guava) from 31.1-jre to 32.0.0-jre. Release notes Sourced from guava's releases. 32.0.0 Maven <dependency> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> <version>32.0.0-jre</version> <!-- or, for Android: --> <version>32.0.0-android</version> </dependency> Jar files 32.0.0-jre.jar 32.0.0-android.jar Guava...

dependencies

Bumps [testng](https://github.com/cbeust/testng) from 6.2.1 to 7.7.0. Release notes Sourced from testng's releases. TestNG v7.7.0 What's Changed Replace FindBugs by SpotBugs by @​gruenich in cbeust/testng#2781 Gradle: Drop forUseAtConfigurationTime() by @​gruenich in...

dependencies

Hi there, Our project is using `jmxutils` and our dependency vulnerability scanning is reporting a Guava vulnerability [CVE-2020-8908](https://nvd.nist.gov/vuln/detail/CVE-2020-8908) that's being brought in by `jmxutils`. I'm not sure if the project...

`@Managed` operations with arguments throw an exception during parameter name extraction. This code should used more generic paranamer code. See Swift for an example https://github.com/facebook/swift/blob/master/swift-codec/src/main/java/com/facebook/swift/codec/metadata/ReflectionHelper.java#L241 ``` Caused by: java.lang.ArrayIndexOutOfBoundsException: 74340...

Hi, The following source files are without license headers: ./src/main/java/org/weakref/jmx/JmxException.java ./src/main/java/org/weakref/jmx/ManagedAnnotation.java ./src/main/java/org/weakref/jmx/ObjectNameBuilder.java ./src/main/java/org/weakref/jmx/ObjectNames.java ./src/main/java/org/weakref/jmx/guice/ExportBinder.java ./src/main/java/org/weakref/jmx/guice/ExportBuilder.java ./src/main/java/org/weakref/jmx/guice/MapExportBinder.java ./src/main/java/org/weakref/jmx/guice/MapMapping.java ./src/main/java/org/weakref/jmx/guice/MapNamingFunction.java ./src/main/java/org/weakref/jmx/guice/MapObjectNameFunction.java ./src/main/java/org/weakref/jmx/guice/NamingFunction.java ./src/main/java/org/weakref/jmx/guice/ObjectNameFunction.java ./src/main/java/org/weakref/jmx/guice/SetExportBinder.java ./src/main/java/org/weakref/jmx/guice/SetMapping.java ./src/main/java/org/weakref/jmx/guice/StringMapExportBinder.java ./src/main/java/org/weakref/jmx/testing/TestingMBeanModule.java ./src/main/java/org/weakref/jmx/testing/TestingMBeanServer.java ./src/test/java/org/weakref/jmx/AbstractMbeanTest.java ./src/test/java/org/weakref/jmx/CustomAnnotationObject.java ./src/test/java/org/weakref/jmx/TestExports.java ./src/test/java/org/weakref/jmx/TestMBeanBuilder.java...

I am very keen to switch to this JMX enabling library and move away from pojo-mbean, as the features here are a more natural fit. However, I am having trouble...

Depends on pull #15 A jmxutils annotation on a method explicitly indicates the class's intent to have that method managed by jmxutils. It shouldn't also be necessary for the class...