January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23662) Scaling To/Up/Down: show an error message (from OpenShift API) reporting outdated objects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23662?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23662: ---------------------------------------- Assignee: Andre Dietisheim > Scaling To/Up/Down: show an error message (from OpenShift API) reporting outdated objects > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23662 > URL: https://issues.jboss.org/browse/JBIDE-23662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Ricardo Martinelli Oliveira > Assignee: Andre Dietisheim > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.3.AM2 > > > Every Scale option I select in the OpenShift Explorer view show this error: > Unable to scale guestbook-service > Exception trying to PUT https://10.1.2.2:8443/api/v1/namespaces/sample-project/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "guestbook-service-2": the object has been modified; please apply your changes to the latest version and try again > However, the scale command is executed successfuly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20569) OpenShift Explorer : "Import Application" menu is confusing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20569?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20569: ---------------------------------------- Assignee: Andre Dietisheim > OpenShift Explorer : "Import Application" menu is confusing > ----------------------------------------------------------- > > Key: JBIDE-20569 > URL: https://issues.jboss.org/browse/JBIDE-20569 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, ux > Fix For: 4.4.3.AM2 > > Attachments: import-application.png > > > [~sspeiche] finds the "Import Application" menu in OpenShift Explorer is confusing: does it mean import from eclipse to openshift or the other way around (it's the latter). Needs better wording. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22362: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.AM2 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[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.AM2 (was: 4.4.3.AM1) > 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.AM2 > > > 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)

9 years, 2 months

1
0
0 / 0

[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.AM2 (was: 4.4.3.AM1) > 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.AM2 > > 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, 2 months

1
0
0 / 0

[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: ------------------------------- Story Points: 8 Sprint: devex #126 January 2017 > 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.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, 2 months

1
0
0 / 0

[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 reassigned JBIDE-23514: ---------------------------------- Assignee: Jeff MAURY > 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.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23705) no content assist in freemarker templates for interface-based beans

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23705?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-23705: --------------------------------------- I cannot really say anything, because my knowledge of freemarker is really not that deep. What I see in PR it drops java bean introspection and re-implements reflection based introspection. I'd rather like to see PR using the introspection utils from freemarker itself or apache commons beanutils BeanUtilBean with custom Introspector registered to tackle InterfaceBased beans introspection problems. > no content assist in freemarker templates for interface-based beans > ------------------------------------------------------------------- > > Key: JBIDE-23705 > URL: https://issues.jboss.org/browse/JBIDE-23705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Ronald Müller > > If your beans in freemarker templates are described by an interface, the code completion (content assist) will not work. > There two mechanism implemented to provide content suggestion: > # Bean-Introspection: this doesn't work for interfaces > # Java Reflections: there are bugs which prevent any suggestions > My suggestion: use only reflections - it will work for both and isn't that harder to implement. > I'm working on a pull request for fixing this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23697) Arquillian New and Noteworthy for 4.4.3.AM1

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23697?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23697. ------------------------------ > Arquillian New and Noteworthy for 4.4.3.AM1 > --------------------------------------------------- > > Key: JBIDE-23697 > URL: https://issues.jboss.org/browse/JBIDE-23697 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Arquillian4.4.3.AM1 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22007) JPA: New Field should select the field in outline view and editor

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22007?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-22007: --------------------------------------- [~gastaldi] I am changing it to minor:) > JPA: New Field should select the field in outline view and editor > ----------------------------------------------------------------- > > Key: JBIDE-22007 > URL: https://issues.jboss.org/browse/JBIDE-22007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.4.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017