[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4321:
-----------------------------
Attachment: rpm-installed-everything-from-central.png
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rpm-installed-everything-from-central.png
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-23783.
---------------------------------
Resolution: Done
Resolving this issue. I'd suggest opening a new one for the labels if you can replicate consistently. I can't see anything wrong here.
> 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: Rob Stryker
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.4.AM3
>
> Attachments: JBIDE-23783.png, adapter.png, corrected-project-settings-composite.png, project-settings-composite.png, resized-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!
> # EXEC: maximise the editor
> Result:
> The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes.
> !resized-project-settings-composite.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-21857:
----------------------------------
Assignee: Rob Stryker (was: Andre Dietisheim)
> 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.4.Final
>
> 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)
8 years, 11 months
[JBoss JIRA] (JBIDE-23710) Properites: Disable scaling on completed deployments
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23710:
-------------------------------------
Sprint: devex #131 May 2017
> Properites: Disable scaling on completed deployments
> ----------------------------------------------------
>
> Key: JBIDE-23710
> URL: https://issues.jboss.org/browse/JBIDE-23710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Labels: openshift_v3, properties
> Fix For: 4.5.0.AM1
>
>
> In web console, scaling completed deployments is disabled.
> In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift.
> Sometimes I also got this exception (but not allways):
> {noformat}
> !ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562
> !MESSAGE Unable to scale wildfly-1
> !STACK 0
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> I think we should do the same as web console -> disable scaling options on completed deployments.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23710) Properites: Disable scaling on completed deployments
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23710:
----------------------------------------
Assignee: Andre Dietisheim
> Properites: Disable scaling on completed deployments
> ----------------------------------------------------
>
> Key: JBIDE-23710
> URL: https://issues.jboss.org/browse/JBIDE-23710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Labels: openshift_v3, properties
> Fix For: 4.5.0.AM1
>
>
> In web console, scaling completed deployments is disabled.
> In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift.
> Sometimes I also got this exception (but not allways):
> {noformat}
> !ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562
> !MESSAGE Unable to scale wildfly-1
> !STACK 0
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> I think we should do the same as web console -> disable scaling options on completed deployments.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months