[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:
-----------------------------------------
here is a PR for one of the 2 problematic use cases (Eclipse instance with JDK9+ and process to which we try to connect with JMX with JDK9+ too) https://github.com/jbosstools/jbosstools-server/pull/619
> 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)
6 years, 9 months
[JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11
by Bob Davis (Jira)
[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ]
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)
6 years, 9 months
[JBoss JIRA] (JBDS-4766) Installation of all soft. in Central introduces new layout of View elements
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4766?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal commented on JBDS-4766:
-------------------------------------
If you take a look closely, you can see a black lines bordering view elements. Which could be both feature or a bug.
> Installation of all soft. in Central introduces new layout of View elements
> ---------------------------------------------------------------------------
>
> Key: JBDS-4766
> URL: https://issues.jboss.org/browse/JBDS-4766
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 12.11.0.GA
> Environment: Fedora 29
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Major
> Attachments: Screenshot_20190326_231224.png
>
>
> After installation of All software in central, including early access, I got this new layout:
> !Screenshot_20190326_231224.png|thumbnail!
> Bug or feature?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26600) Cannot remove JSF capabilities from JSF project
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-26600:
-------------------------------------
Summary: Cannot remove JSF capabilities from JSF project
Key: JBIDE-26600
URL: https://issues.jboss.org/browse/JBIDE-26600
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsf
Affects Versions: 4.11.0.Final
Environment: Fedora 29, Java 11.0.2
Reporter: Ondrej Dockal
Removing JSF capabilities introduces Command 'org.jboss.tools.jsf.ui.project.configure.disable' failed error.
{code}
eclipse.buildId=12.11.0.GA-v20190321-1925-B4244
java.version=11.0.2
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -data file:/home/odockal/workspace_12110Ga-Staging/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.eclipse.e4.ui.workbench
Error
Wed Mar 27 14:32:09 CET 2019
Command 'org.jboss.tools.jsf.ui.project.configure.disable' failed
org.eclipse.core.commands.ExecutionException: Error executing 'org.jboss.tools.jsf.ui.project.configure.disable': java.lang.NullPointerException
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:170)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:497)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:490)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5783)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1411)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:5051)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4579)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
at org.eclipse.equinox.launcher.Main.run(Main.java:1476)
at org.eclipse.equinox.launcher.Main.main(Main.java:1449)
Caused by: org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:320)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:254)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
... 33 more
Caused by: java.lang.NullPointerException
at org.jboss.tools.jsf.model.handlers.RemoveJSFNatureContribution.execute(RemoveJSFNatureContribution.java:40)
at org.jboss.tools.common.model.handlers.RemoveModelNatureHandler.executeHandler(RemoveModelNatureHandler.java:99)
at org.jboss.tools.common.meta.action.impl.XActionImpl.executeHandler(XActionImpl.java:65)
at org.jboss.tools.common.model.ui.action.XModelObjectAction.actionPerformed(XModelObjectAction.java:96)
at org.jboss.tools.common.model.ui.action.XModelObjectActionInvoker.execute(XModelObjectActionInvoker.java:36)
at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:53)
at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:40)
at org.jboss.tools.common.model.ui.internal.handlers.ModelResourceHandler.doRun(ModelResourceHandler.java:94)
at org.jboss.tools.common.model.ui.internal.handlers.ModelResourceHandler.execute(ModelResourceHandler.java:74)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:96)
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.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
... 37 more
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26598) Unable to connect to JMX process when instance launched with JDK 11
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26598:
----------------------------------
Fix Version/s: 4.11.0.Final
> 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)
6 years, 9 months
[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)
6 years, 9 months
[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)
6 years, 9 months
[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)
6 years, 9 months
[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)
6 years, 9 months
[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)
6 years, 9 months