[JBoss JIRA] (JBIDE-23514) Server adapter: double clicking on JMX child of a non-eap adapter causes error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
Fix Version/s: 4.4.3.AM1
> Server adapter: double clicking on JMX child of a non-eap adapter causes error
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> 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
>
>
> # 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: double clicking on JMX child of a non-eap adapter causes error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
Description: (was: # 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: double clicking on JMX child of a non-eap adapter causes error
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> 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
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23514) Server adapter: double clicking on JMX child of a non-eap adapter causes error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
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: double clicking on JMX child of a non-eap adapter causes error
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> 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
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23514) Server adapter: double clicking on JMX child of a non-eap adapter causes error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
Description:
# 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:
# 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: double clicking on JMX child of a non-eap adapter causes error
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: jmx, openshift_v3, server_adapter
> Attachments: jmx-error-nodejs.png
>
>
> # 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: double clicking on JMX child of a non-eap adapter causes error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
Labels: jmx openshift_v3 server_adapter (was: )
> Server adapter: double clicking on JMX child of a non-eap adapter causes error
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: jmx, openshift_v3, server_adapter
> Attachments: jmx-error-nodejs.png
>
>
> # 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: double clicking on JMX child of a non-eap adapter causes error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23514:
-------------------------------------
Attachment: jmx-error-nodejs.png
> Server adapter: double clicking on JMX child of a non-eap adapter causes error
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Attachments: jmx-error-nodejs.png
>
>
> # 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: double clicking on JMX child of a non-eap adapter causes error
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23514:
----------------------------------------
Summary: Server adapter: double clicking on JMX child of a non-eap adapter causes error
Key: JBIDE-23514
URL: https://issues.jboss.org/browse/JBIDE-23514
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.2.AM3
Reporter: Andre Dietisheim
Attachments: jmx-error-nodejs.png
# 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] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4175 at 11/23/16 2:28 PM:
------------------------------------------------------------
Current status:
I've installed everything from Central and only these are still a problem:
||3rd Party||Status in RPM||Status Upstream||Issue||Description or Errors||
|Atlassian_Connector|(x)|(x)|JBDS-4191|would need to fork https://bitbucket.org/atlassian/connector-eclipse/overview and run their Ant build :(
|Spring_IDE|(x)|(/)|JBDS-4190|Fixed in master branch for Spring IDE 3.8.3.CI (no idea when 3.8.3.RELEASE is due): http://dist.springsource.com/snapshot/TOOLS/nightly/e4.6
|JRebel|(x)|(/)|n/a|Fixed in http://update.zeroturnaround.com/update-site-nightly/ but no release date for 7.0.1 avail yet
||Red Hat||Status in RPM||Status Upstream||Issue||Description or Errors||
|Teiid Designer|(x)|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|SwitchYard 2.2.0|(x)|(x)|JBDS-4200|slf4j use constraint violation
|rest of integration stack 10.0.0.GA|(/)|(/)|n/a|works OOTB when installed from https://devstudio.jboss.com/10.0/stable/updates/integration-stack/
We will need to make sure this is properly documented in https://issues.jboss.org/browse/RHDEVDOCS-120?focusedCommentId=13327430&p... so users don't break their Eclipse/devstudio rpm installs by installation of these tools.
was (Author: nickboldt):
Current status:
I've installed everything from Central and only these are still a problem:
||3rd Party||Status in RPM||Status Upstream||Issue||Description or Errors||
|Atlassian_Connector|(x)|(x)|JBDS-4191|would need to fork https://bitbucket.org/atlassian/connector-eclipse/overview and run their Ant build :(
|Spring_IDE|(x)|(/)|JBDS-4190|Fixed in master branch for Spring IDE 3.8.3.CI (no idea when 3.8.3.RELEASE is due): http://dist.springsource.com/snapshot/TOOLS/nightly/e4.6
|JRebel|(x)|(/)|n/a|Fixed in http://update.zeroturnaround.com/update-site-nightly/ but no release date for 7.0.1 avail yet
||Red Hat||Status in RPM||Status Upstream||Issue||Description or Errors||
|Teiid Designer|(x)|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|SwitchYard 2.2.0|(x)|(x)|JBDS-4200|slf4j use constraint violation
|rest of integration stack 10.0.0.GA|(/)|(/)|n/a|works OOTB when installed from https://devstudio.jboss.com/10.0/stable/updates/integration-stack/
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.x
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4175 at 11/23/16 2:26 PM:
------------------------------------------------------------
Current status:
I've installed everything from Central and only these are still a problem:
||3rd Party||Status in RPM||Status Upstream||Issue||Description or Errors||
|Atlassian_Connector|(x)|(x)|JBDS-4191|would need to fork https://bitbucket.org/atlassian/connector-eclipse/overview and run their Ant build :(
|Spring_IDE|(x)|(/)|JBDS-4190|Fixed in master branch for Spring IDE 3.8.3.CI (no idea when 3.8.3.RELEASE is due): http://dist.springsource.com/snapshot/TOOLS/nightly/e4.6
|JRebel|(x)|(/)|n/a|Fixed in http://update.zeroturnaround.com/update-site-nightly/ but no release date for 7.0.1 avail yet
||Red Hat||Status in RPM||Status Upstream||Issue||Description or Errors||
|Teiid Designer|(x)|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|SwitchYard 2.2.0|(x)|(x)|JBDS-4200|slf4j use constraint violation
|rest of integration stack 10.0.0.GA|(/)|(/)|n/a|works OOTB when installed from https://devstudio.jboss.com/10.0/stable/updates/integration-stack/
was (Author: nickboldt):
Current status:
I've installed everything from Central and only these are still a problem:
||3rd Party||Status in RPM||Status Upstream||Issue||Description or Errors||
|Atlassian_Connector|(x)|(x)|JBDS-4191|would need to fork https://bitbucket.org/atlassian/connector-eclipse/overview and run their Ant build :(
|Spring_IDE|(x)|(/)|JBDS-4190|Fixed in master branch for Spring IDE 3.8.3.CI (no idea when 3.8.3.RELEASE is due)
|JRebel|(x)|(/)|n/a|Fixed in http://update.zeroturnaround.com/update-site-nightly/ but no release date for 7.0.1 avail yet
||Red Hat||Status in RPM||Status Upstream||Issue||Description or Errors||
|Teiid Designer|(x)|(/)|JBDS-4189|Fixed in master branch for Teiid Designer 11.0 (but not in integration stack 10.0.0.GA)
|SwitchYard 2.2.0|(x)|(x)|JBDS-4200|slf4j use constraint violation
|rest of integration stack 10.0.0.GA|(/)|(/)|n/a|works OOTB when installed from https://devstudio.jboss.com/10.0/stable/updates/integration-stack/
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.x
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months