[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21857:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM1
>
> Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 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:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(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
> 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, 3 months
[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19506:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Connection wizard, Connection: should have unit tests
> ------------------------------------------------------
>
> Key: JBIDE-19506
> URL: https://issues.jboss.org/browse/JBIDE-19506
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, tests
> Fix For: 4.4.3.AM1
>
> Original Estimate: 2 days
> Time Spent: 3 days
> Remaining Estimate: 3 days
>
> In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23019:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Integration tests: have them running automatically, continuously
> ----------------------------------------------------------------
>
> Key: JBIDE-23019
> URL: https://issues.jboss.org/browse/JBIDE-23019
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.3.AM1
>
>
> The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI.
> There are several pain-points currently:
> - there's no dedicated OS instance to run them against
> - tests are not stable
> - etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23625) JMX: jmx tree is not very usable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23625:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> JMX: jmx tree is not very usable
> --------------------------------
>
> Key: JBIDE-23625
> URL: https://issues.jboss.org/browse/JBIDE-23625
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.3.AM1
>
> Attachments: image-2016-12-02-16-47-59-519.png
>
>
> steps to reproduce:
> # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
> # EXEC: create a server adapter for it
> # ASSERT: your server adapter now has a JMX child node
> # EXEC: double click it and wait until all MBeans are loaded
> # EXEC: now try to see if you can find your deployment
> Result:
> You get a listing of tons of beans.
> !mbeans.png!
> Your deployment is a child bean of jboss.as, named by the war that was created:
> !mbean-deployment.png!
> Rather painfull to find a listing of your deployments in this way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months