October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25168) cdk 3.2+ is tech preview in one place and not in another

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25168?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25168. --------------------------------- Both adapter/detector items do not have Tech Preview in the name. Verified on devstudio Version: 11.1.0.GA-v20171026-1022-B1486. > cdk 3.2+ is tech preview in one place and not in another > -------------------------------------------------------- > > Key: JBIDE-25168 > URL: https://issues.jboss.org/browse/JBIDE-25168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > > Currently for AM3, the new cdk 3.2+ runtime detector is listed as Tech Preview (as seen in Preferences -> JBoss Runtime Detection). But the server adapter does not say Tech Preview (as seen in New Server wizard). > These two should be consistent, no? Ideally both should say tech preview. > But... since this won't be fixed for AM3, what happens next? The adapter should no longer be Tech Preview for JBT 4.5.1.Final, right? Because CDK 3.2 will be released at the same time and then 3.1 will be no longer maintained. Yes, the profiles may not be fully supported, but the server adapter as a whole should be supported. > So it's quite likely that this will be Out of date before it can be fixed - the adapter/detector will no longer be tech preview. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25303: ------------------------------------- Affects Version/s: 4.5.1.Final > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25304) In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25304?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25304: ------------------------------------- Labels: cdk_server_adapter_wizard openshift_v3 (was: ) > In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25304 > URL: https://issues.jboss.org/browse/JBIDE-25304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Minor > Labels: cdk_server_adapter_wizard, openshift_v3 > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25304) In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25304?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25304: ------------------------------------- Fix Version/s: 4.5.x > In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25304 > URL: https://issues.jboss.org/browse/JBIDE-25304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25304) In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25304?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25304: ------------------------------------------ [~rob.stryker] dare to look into this please? > In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25304 > URL: https://issues.jboss.org/browse/JBIDE-25304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25304) In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25304?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25304: ---------------------------------------- Assignee: Rob Stryker > In CDK server wizard, decorator is not shown for Minishift Binary label while "Unknown error while checking for minishift version" message pops up in page description > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25304 > URL: https://issues.jboss.org/browse/JBIDE-25304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25303: ------------------------------------- Summary: Server adapter: support hot-deployment on OpenShift for SpringBoot app (was: Support hot-deployment on OpenShift for SpringBoot app) > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Aurélien Pupier > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25303: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Support hot-deployment on OpenShift for SpringBoot app > ------------------------------------------------------ > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Aurélien Pupier > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM1 > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25287: ------------------------------------- Fix Version/s: 4.5.x > Jolokia Connection errors are swallowed > --------------------------------------- > > Key: JBIDE-25287 > URL: https://issues.jboss.org/browse/JBIDE-25287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Affects Versions: 4.5.0.Final, 4.5.1.AM3 > Reporter: Aurélien Pupier > Labels: jmx, jolokia, openshift > Fix For: 4.5.x > > Attachments: image-2017-10-24-13-30-30-715.png > > > even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed. > I have another use case for which I have: > !image-2017-10-24-13-30-30-715.png|thumbnail! > with stack in log > {noformat} > !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523 > !MESSAGE An error occurred while opening the connection. > !STACK 0 > java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115) > 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:56) > Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > 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:313) > ... 4 more > {noformat} > although when using a Rest client i have this error which contains far more information: > {noformat} > { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "pods "camel-ose-springboot-xml-3-t99hx" not found", > "reason": "NotFound", > "details": { > "name": "camel-ose-springboot-xml-3-t99hx", > "kind": "pods" > }, > "code": 404 > } > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25287: ---------------------------------------- Assignee: Rob Stryker > Jolokia Connection errors are swallowed > --------------------------------------- > > Key: JBIDE-25287 > URL: https://issues.jboss.org/browse/JBIDE-25287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Affects Versions: 4.5.0.Final, 4.5.1.AM3 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Labels: jmx, jolokia, openshift > Fix For: 4.5.x > > Attachments: image-2017-10-24-13-30-30-715.png > > > even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed. > I have another use case for which I have: > !image-2017-10-24-13-30-30-715.png|thumbnail! > with stack in log > {noformat} > !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523 > !MESSAGE An error occurred while opening the connection. > !STACK 0 > java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115) > 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:56) > Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > 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:313) > ... 4 more > {noformat} > although when using a Rest client i have this error which contains far more information: > {noformat} > { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "pods "camel-ose-springboot-xml-3-t99hx" not found", > "reason": "NotFound", > "details": { > "name": "camel-ose-springboot-xml-3-t99hx", > "kind": "pods" > }, > "code": 404 > } > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017