[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23514:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> 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
> Assignee: Jeff MAURY
> Labels: jmx, openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
> 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)
8 years, 8 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23783:
------------------------------------------
after the fix:
!project-settings-composite.png!
> Server adapter editor: Project settings composite is badly layouted
> -------------------------------------------------------------------
>
> Key: JBIDE-23783
> URL: https://issues.jboss.org/browse/JBIDE-23783
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.3.AM2
>
> Attachments: corrected-project-settings-composite.png, project-settings-composite.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a server adapter defined
> # EXEC: open up the editor for your server adapter
> Result:
> The project settings composite is badly layouted, especially the right border boundaries are not even:
> !project-settings-composite.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23783:
-------------------------------------
Attachment: corrected-project-settings-composite.png
> Server adapter editor: Project settings composite is badly layouted
> -------------------------------------------------------------------
>
> Key: JBIDE-23783
> URL: https://issues.jboss.org/browse/JBIDE-23783
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.3.AM2
>
> Attachments: corrected-project-settings-composite.png, project-settings-composite.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a server adapter defined
> # EXEC: open up the editor for your server adapter
> Result:
> The project settings composite is badly layouted, especially the right border boundaries are not even:
> !project-settings-composite.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18983:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> Project cannot be built. Possible open file handle
> --------------------------------------------------
>
> Key: JBIDE-18983
> URL: https://issues.jboss.org/browse/JBIDE-18983
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, maven
> Affects Versions: 4.2.1.Final
> Environment: luna x64 windows 8.1 x64
> java 8u25 x64
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Fix For: 4.4.3.Final
>
>
> Frequently when working in a Java EE7 project I will get an error like.
> "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent.
> I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml
> It looks like either jboss tools or eclipse is holding on to a file handle for this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23490:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.Final
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months