[JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11
by Aurélien Pupier (Jira)
[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-26598:
-----------------------------------------
so my previous investigation is when using Jboss Tools with JDK 11 and having a JDK 8 for the process we want to connect to. it means that sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary is not "backward-compatible".
In case, it is JDK 11 for both places, the problem is in Jboss Tools code. it searching for a management-agent.jar which doesn't exist in org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.getLocalConnectorAddressInternal(Object, int)
it is searching for this kind of file C:\install\jdk\jdk-11.0.2\lib\management-agent.jar but it doesn't exist
> 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
>
> {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)
7 years
[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26599?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26599:
----------------------------------
Steps to Reproduce:
1. Start oc cluster up and import templates, example:
{code:java}
oc cluster up
oc login -u system:admin
oc project openshift
oc create secret generic redhat.io --from-file=.dockerconfigjson=/home/jkopriva/.docker/config.json --type=kubernetes.io/dockerconfigjson
oc secrets link default redhat.io --for=pull
cd /home/jkopriva/git/jboss-eap-7-openshift-image/
oc create -n openshift -f templates
oc create -n openshift -f https://raw.githubusercontent.com/jboss-container-images/jboss-eap-7-open...
{code}
2. Create connection in devstudio, create project with application template *eap72-basic-s2i*
3. Import project and wait for build, afterwards create server adapter
4. Wait for app to start and after wards click on module under server adapter and click *Show in* -> *Web Browser via LiveReload server*
5. Page is opened with error message:
!image-2019-03-27-10-30-34-801.png|thumbnail!
was:
1. Start oc cluster up and import templates, example:
oc cluster up
oc login -u system:admin
oc project openshift
oc create secret generic redhat.io --from-file=.dockerconfigjson=/home/jkopriva/.docker/config.json --type=kubernetes.io/dockerconfigjson
oc secrets link default redhat.io --for=pull
cd /home/jkopriva/git/jboss-eap-7-openshift-image/
oc create -n openshift -f templates
oc create -n openshift -f https://raw.githubusercontent.com/jboss-container-images/jboss-eap-7-open...
2. Create connection in devstudio, create project with application template eap72-basic-s2i
3. Import project and wait for build, afterwards create server adapter
4. Wait for app to start and after wards click on module under server adapter and click Show in -> Web Browser via LiveReload server
5. Page is opened with error message:
!image-2019-03-27-10-30-34-801.png|thumbnail!
> LiveReload does not work with OpenShift3 server adapter
> -------------------------------------------------------
>
> Key: JBIDE-26599
> URL: https://issues.jboss.org/browse/JBIDE-26599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, openshift
> Affects Versions: 4.11.0.Final
> Environment: oc cluster up 3.11 from Fedora repo
> Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre...
> Devstudio + installed livereload:
> Version: 12.11.0.GA
> Build id: GA-v20190321-1925-B4244
> Build date: 20190321-1925
> JDK 11.02 + F29
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.11.0.Final
>
> Attachments: image-2019-03-27-10-30-34-801.png
>
>
> If I try to directly connect to livereload server there is an error message:
> {code:java}
> HTTP ERROR 500
> Problem accessing /. Reason:
> Server Error
> Caused by:
> java.lang.IllegalArgumentException: Invalid URI host: null (authority: null)
> at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506)
> at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438)
> at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at org.eclipse.jetty.server.Server.handle(Server.java:502)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
> at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11
by Aurélien Pupier (Jira)
[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-26598:
-----------------------------------------
I modified manually the value of the returned result when debugging in sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary from _0_ to _return code: 0_ and after that the JMX navigator is working fine
> 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
>
> {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)
7 years
[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26599?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26599:
----------------------------------
Priority: Critical (was: Major)
> LiveReload does not work with OpenShift3 server adapter
> -------------------------------------------------------
>
> Key: JBIDE-26599
> URL: https://issues.jboss.org/browse/JBIDE-26599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, openshift
> Affects Versions: 4.11.0.Final
> Environment: oc cluster up 3.11 from Fedora repo
> Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre...
> Devstudio + installed livereload:
> Version: 12.11.0.GA
> Build id: GA-v20190321-1925-B4244
> Build date: 20190321-1925
> JDK 11.02 + F29
> Reporter: Josef Kopriva
> Priority: Critical
> Fix For: 4.11.0.Final
>
> Attachments: image-2019-03-27-10-30-34-801.png
>
>
> If I try to directly connect to livereload server there is an error message:
> {code:java}
> HTTP ERROR 500
> Problem accessing /. Reason:
> Server Error
> Caused by:
> java.lang.IllegalArgumentException: Invalid URI host: null (authority: null)
> at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506)
> at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438)
> at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at org.eclipse.jetty.server.Server.handle(Server.java:502)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
> at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26599?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26599:
----------------------------------
Fix Version/s: 4.11.0.Final
> LiveReload does not work with OpenShift3 server adapter
> -------------------------------------------------------
>
> Key: JBIDE-26599
> URL: https://issues.jboss.org/browse/JBIDE-26599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload, openshift
> Affects Versions: 4.11.0.Final
> Environment: oc cluster up 3.11 from Fedora repo
> Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre...
> Devstudio + installed livereload:
> Version: 12.11.0.GA
> Build id: GA-v20190321-1925-B4244
> Build date: 20190321-1925
> JDK 11.02 + F29
> Reporter: Josef Kopriva
> Priority: Major
> Fix For: 4.11.0.Final
>
> Attachments: image-2019-03-27-10-30-34-801.png
>
>
> If I try to directly connect to livereload server there is an error message:
> {code:java}
> HTTP ERROR 500
> Problem accessing /. Reason:
> Server Error
> Caused by:
> java.lang.IllegalArgumentException: Invalid URI host: null (authority: null)
> at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506)
> at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449)
> at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438)
> at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
> at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
> at org.eclipse.jetty.server.Server.handle(Server.java:502)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
> at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
> at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
> at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26599) LiveReload does not work with OpenShift3 server adapter
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-26599:
-------------------------------------
Summary: LiveReload does not work with OpenShift3 server adapter
Key: JBIDE-26599
URL: https://issues.jboss.org/browse/JBIDE-26599
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload, openshift
Affects Versions: 4.11.0.Final
Environment: oc cluster up 3.11 from Fedora repo
Openshift templates from: https://github.com/jboss-container-images/jboss-eap-7-openshift-image/tre...
Devstudio + installed livereload:
Version: 12.11.0.GA
Build id: GA-v20190321-1925-B4244
Build date: 20190321-1925
JDK 11.02 + F29
Reporter: Josef Kopriva
Attachments: image-2019-03-27-10-30-34-801.png
If I try to directly connect to livereload server there is an error message:
{code:java}
HTTP ERROR 500
Problem accessing /. Reason:
Server Error
Caused by:
java.lang.IllegalArgumentException: Invalid URI host: null (authority: null)
at org.eclipse.jetty.client.HttpClient.checkHost(HttpClient.java:506)
at org.eclipse.jetty.client.HttpClient.newHttpRequest(HttpClient.java:491)
at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:449)
at org.eclipse.jetty.client.HttpClient.newRequest(HttpClient.java:438)
at org.eclipse.jetty.proxy.AsyncMiddleManServlet.service(AsyncMiddleManServlet.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:542)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:502)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11
by Aurélien Pupier (Jira)
[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-26598:
-----------------------------------------
when i put a breakpoint in org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.getLocalConnectorAddressInternal(Object, int) in the catch. I have access to the following stacktrace which is swallowed:
{noformat}
!ENTRY org.fusesource.ide.launcher.ui 1 1 2019-03-27 10:08:56.543
!MESSAGE Using existing launch configuration
org.jboss.tools.common.jdt.debug.tools.ToolsCoreException: 0
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeLoadAgent(Tools.java:419)
at org.jboss.tools.common.jdt.debug.tools.ToolsCore.loadAgent(ToolsCore.java:157)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.getLocalConnectorAddressInternal(JvmAttachHandler.java:248)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.getLocalConnectorAddress(JvmAttachHandler.java:220)
at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.getLocalConnectorAddress(ActiveJvm.java:556)
at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:444)
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)
Caused by: java.lang.reflect.InvocationTargetException
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 org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeLoadAgent(Tools.java:406)
... 10 more
Caused by: com.sun.tools.attach.AgentLoadException: 0
at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(HotSpotVirtualMachine.java:108)
at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(HotSpotVirtualMachine.java:119)
at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.loadAgent(HotSpotVirtualMachine.java:147)
... 15 more
{noformat}
> 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
>
> {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)
7 years
[JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11
by Aurélien Pupier (Jira)
[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-26598:
------------------------------------
Description:
{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}
was:
{noformat}
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}
> 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
>
> {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)
7 years
[JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11
by Aurélien Pupier (Jira)
Aurélien Pupier created JBIDE-26598:
---------------------------------------
Summary: 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
{noformat}
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)
7 years