[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier updated JENKINS-52017 I release the plugin with this fix. Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Status: In Review Resolved Resolution: Fixed Released As: 4.0.2.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier updated JENKINS-52017 Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier commented on JENKINS-52017 Re: Metrics Plugin relies on un-exposed module API It seems that the PR I provided is enough. Here why I say this: I started a Jenkins instance using jenkins/jenkins:jdk11 Docker image I did install any plugin using the wizard Using the plugin manager, I installed metrics plugin, version 4.0.2.2 I had to restart the instance I can confirm that I have the same issue as described here I built the changeset I provided in the PR and uploaded the hpi binary to the instance using the plugin manager during the restart, there is no error in the logs once the instance is up and running, I configured the metrics and I could see vm.cpu.load in JENKINS_URL/metrics/currentUser/metrics Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier commented on JENKINS-52017 Re: Metrics Plugin relies on un-exposed module API So, the PR I provided to the repository seems to fix this problem but I cannot certify it because it is now facing JENKINS-54355, because of commons-beanutils. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier updated JENKINS-52017 Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier commented on JENKINS-52017 Re: Metrics Plugin relies on un-exposed module API I filled a PR to track this. I tried to focus my solution on removing the reflection, as this is almost impossible with Java 9+ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier updated JENKINS-52017 Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier started work on JENKINS-52017 Change By: Adrien Lecharpentier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier updated JENKINS-52017 Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier assigned an issue to Adrien Lecharpentier Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Assignee: Adrien Lecharpentier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Baptiste Mathus Labels: illegalReflectiveAccess java10 java10_hackathon java11 java11-compatibility triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Baptiste Mathus Labels: illegalReflectiveAccess java10 java10_hackathon java11 java11-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Baptiste Mathus reopened an issue Reopening after I confirmed this is still present in the latest version of the Metrics plugin. Just reproduced using the Evergreen Java 11 flavor, launched with Version in that case is 4.0.2.3-rc229.d9b0eb3c576d docker volume create jenkins-evergreen-data && \ docker pull jenkins/evergreen:java11-docker-cloud && \ docker run --name evergreen \ --restart=always \ -ti \ -p 8080:80 \ -v /var/run/docker.sock:/var/run/docker.sock \ -v jenkins-evergreen-data:/evergreen/data \ -e LOG_LEVEL=info \ jenkins/evergreen:java11-docker-cloud Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Baptiste Mathus Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Baptiste Mathus Labels: java10 java10_hackathon java11 java11-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title
Baptiste Mathus edited a comment on JENKINS-52017
Re: Metrics Plugin relies on un-exposed module API
Pretty sure this is actually unresolved , caused by https://github . com/jenkinsci/metrics-plugin/blob/d9b0eb3c576dd1aeff3bff113ca9cd0253aef40f/src/main/java/jenkins/metrics/impl/VMMetricProviderImpl.java#L226. Will double-check and possibly reopen soonish I confirm that it does not stop Jenkins from starting though. Just seen with Jenkins 2.153-SNAPSHOT on Java 11:{noformat}nov. 29, 2018 10:59:35 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorWARNING: Failed to instantiate Key[type=jenkins.metrics.impl.VMMetricProviderImpl, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors:1) Error injecting constructor, java.lang.reflect.InaccessibleObjectException: Unable to make public long com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime() accessible: module jdk.management does not "opens com.sun.management.internal" to unnamed module @41b1dccd at jenkins.metrics.impl.VMMetricProviderImpl.(VMMetricProviderImpl.java:61)1 errorat com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:440)at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:402)at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:393)at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:494)at hudson.ExtensionList.load(ExtensionList.java:380)at hudson.ExtensionList.ensureLoaded(ExtensionList.java:318)at hudson.ExtensionList.iterator(ExtensionList.java:172)at jenkins.metrics.api.Metrics.afterExtensionsAugmented(Metrics.java:335)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.base/java.lang.reflect.Method.invoke(Method.java:566)at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1069)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)at java.base/java.lang.Thread.run(Thread.java:834)Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make public long com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime() accessible: module jdk.management does not "opens com.sun.management.internal" to unnamed module @41b1dccdat java.base/java.lang.reflect.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title
Baptiste Mathus edited a comment on JENKINS-52017
Re: Metrics Plugin relies on un-exposed module API
Pretty sure this is actually unresolved. Will double-check and possibly reopen soonish Just seen with Jenkins 2.153-SNAPSHOT on Java 11:{noformat}nov. 29, 2018 10:59:35 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorWARNING: Failed to instantiate Key[type=jenkins.metrics.impl.VMMetricProviderImpl, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors:1) Error injecting constructor, java.lang.reflect.InaccessibleObjectException: Unable to make public long com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime() accessible: module jdk.management does not "opens com.sun.management.internal" to unnamed module @41b1dccd at jenkins.metrics.impl.VMMetricProviderImpl.(VMMetricProviderImpl.java:61)1 errorat com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:440)at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:402)at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:393)at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:494)at hudson.ExtensionList.load(ExtensionList.java:380)at hudson.ExtensionList.ensureLoaded(ExtensionList.java:318)at hudson.ExtensionList.iterator(ExtensionList.java:172)at jenkins.metrics.api.Metrics.afterExtensionsAugmented(Metrics.java:335)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.base/java.lang.reflect.Method.invoke(Method.java:566)at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1069)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)at java.base/java.lang.Thread.run(Thread.java:834)Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make public long com.sun.management.internal.OperatingSystemImpl.getProcessCpuTime() accessible: module jdk.management does not "opens com.sun.management.internal" to unnamed module @41b1dccdat java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:340)at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:280)at java.base/java.lang.reflect.Method.checkCanSetAccessi
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Baptiste Mathus commented on JENKINS-52017 Re: Metrics Plugin relies on un-exposed module API Pretty sure this is actually unresolved. Will double-check and possibly reopen soonish Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Oleg Nenashev Labels: java10 java10_hackathon java11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
