[JBoss JIRA] (JBIDE-23512) Properties: Header hidden by another header is not retrievable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23512?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23512:
-------------------------------------
Fix Version/s: 4.4.3.AM1
> Properties: Header hidden by another header is not retrievable
> --------------------------------------------------------------
>
> Key: JBIDE-23512
> URL: https://issues.jboss.org/browse/JBIDE-23512
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Marián Labuda
> Labels: openshift_v3, properties
> Fix For: 4.4.3.AM1
>
> Attachments: properties.ogv
>
>
> Table header in Properties for OpenShift 3 resources can be moved/resized. If I resize a header to beginning of another header, the another header is hidden and I cant resize is back or retrieve the second header with its column. See video for more details
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4191:
--------------------------------------
No, I would rather remove unsupported plugin from Central. I don't want us to own/support this plugin. We don't have to do anything right now, but when we are bringing back Central to RPM let's just remove attlassian connector from Central at all.
> problem installing atlassian: depends on javax.servlet 3.1.0
> ------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.x
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4191:
----------------------------------
So does that mean I should find the time to fork and fix this for use in Neon when installed via RPM? Please clarify.
> problem installing atlassian: depends on javax.servlet 3.1.0
> ------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.x
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4191:
--------------------------------------
It's still being installed. Not super popular but somewhere in the middle. One third of the most popular AngularJS installations.
> problem installing atlassian: depends on javax.servlet 3.1.0
> ------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.x
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-20045) Software/Update page looks bad in Dark mode
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20045?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-20045:
----------------------------------------
It's worth fixing, yes.
> Software/Update page looks bad in Dark mode
> -------------------------------------------
>
> Key: JBIDE-20045
> URL: https://issues.jboss.org/browse/JBIDE-20045
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: LATER
>
> Attachments: central.png, windowws-screenshot.png
>
>
> - Enable Eclipse Dark Theme in Preferences > Appearance,
> - Open Central, click on the Software Update page
> - Make sure Early Access is enabled
> - Check this :
> !http://content.screencast.com/users/fbricon/folders/Jing/media/679d7466-cba0-42b8-aaf0-8d6b2f35691a/00000113.png!
> - grey areas around the checkboxes and the titles
> - blue links don't look good
> - Early-Access items are not highlighted (even after fixing JBIDE-20007)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
Description:
Most likely server adapters for non-eap based apps should not have a jmx node.
Steps to reproduce:
# ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template)
# ASSERT: make sure the build is finished, the pod is running.
# ASSERT: make sure that you have a server adapter for your service
# ASSERT: make sure that it is in "[Started, Synchronized]" state)
# EXEC: unfold the server adapter and double click on the JMX child
Result:
An error shows up
!jmx-error-nodejs.png!
{code}
java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328)
at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
{code}
was:Most likely server adapters for non-eap based apps should not have a jmx node.
> Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: jmx, openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
> Attachments: jmx-error-nodejs.png
>
>
> Most likely server adapters for non-eap based apps should not have a jmx node.
> Steps to reproduce:
> # ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template)
> # ASSERT: make sure the build is finished, the pod is running.
> # ASSERT: make sure that you have a server adapter for your service
> # ASSERT: make sure that it is in "[Started, Synchronized]" state)
> # EXEC: unfold the server adapter and double click on the JMX child
> Result:
> An error shows up
> !jmx-error-nodejs.png!
> {code}
> java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
Description:
Most likely server adapters for non-java based apps should not have a jmx node.
Steps to reproduce:
# ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template)
# ASSERT: make sure the build is finished, the pod is running.
# ASSERT: make sure that you have a server adapter for your service
# ASSERT: make sure that it is in "[Started, Synchronized]" state)
# EXEC: unfold the server adapter and double click on the JMX child
Result:
An error shows up
!jmx-error-nodejs.png!
{code}
java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328)
at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
{code}
was:
Most likely server adapters for non-eap based apps should not have a jmx node.
Steps to reproduce:
# ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template)
# ASSERT: make sure the build is finished, the pod is running.
# ASSERT: make sure that you have a server adapter for your service
# ASSERT: make sure that it is in "[Started, Synchronized]" state)
# EXEC: unfold the server adapter and double click on the JMX child
Result:
An error shows up
!jmx-error-nodejs.png!
{code}
java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328)
at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278)
at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
{code}
> Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: jmx, openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
> Attachments: jmx-error-nodejs.png
>
>
> Most likely server adapters for non-java based apps should not have a jmx node.
> Steps to reproduce:
> # ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template)
> # ASSERT: make sure the build is finished, the pod is running.
> # ASSERT: make sure that you have a server adapter for your service
> # ASSERT: make sure that it is in "[Started, Synchronized]" state)
> # EXEC: unfold the server adapter and double click on the JMX child
> Result:
> An error shows up
> !jmx-error-nodejs.png!
> {code}
> java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months