[jbosstools-issues] [JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11

Bob Davis (Jira) issues at jboss.org
Wed Mar 27 10:02:03 EDT 2019


    [ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713943#comment-13713943 ] 

Bob Davis commented on JBIDE-26598:
-----------------------------------

Great catch, [~aurelien.pupier] - 
We just talked about it. Here's the plan for now.
Since we don't know just how deep this goes, we want to explore it and come up with a reasonable estimate on how much time it could take to fix/test/etc., so [~jeffmaury] will dig in and be able to provide an analysis of the problem by EOB, 28 March or early 29 March. At that point we can figure out the best "go forward" plan. Right now, we see 3 options -

# Ship on existing date, with documentation noting the workaround, and fix in the next scheduled release
# Ship on existing date, with documentation noting the workaround, and issue a bug fix as soon as is possible, but before the next scheduled release
# Push the release date until it's fixed

The best answer will sort of depend on what the level of effort is and on what we collectively decide based on Jeff's digging (your input will be important here). 



> Unable to connect to JMX process when instance launched with JDK 11
> -------------------------------------------------------------------
>
>                 Key: JBIDE-26598
>                 URL: https://issues.jboss.org/browse/JBIDE-26598
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jmx
>    Affects Versions: 4.11.0.Final
>            Reporter: Aurélien Pupier
>            Priority: Blocker
>             Fix For: 4.11.0.Final
>
>
> {code}
> org.jboss.tools.jmx.local
> Error
> Wed Mar 27 09:25:29 CET 2019
> Unable to connect to jvm
> org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException: Could not get JMX service URL (PID: 9470)
> 	at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:462)
> 	at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:445)
> 	at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:233)
> 	at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:213)
> 	at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect(JvmConnectionWrapper.java:118)
> 	at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)



More information about the jbosstools-issues mailing list