June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25861) Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25861?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25861: --------------------------------------- Checked on RC3 Eclipse Photon and it seems alright. Verified on devstudio 12.0.0.AM3-v20180614-1606-B2737. > Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25861 > URL: https://issues.jboss.org/browse/JBIDE-25861 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker > Affects Versions: 4.5.3.AM3 > Environment: Fedora 27 x86_64 > Reporter: Ondrej Dockal > Assignee: Jeff Johnston > Labels: upstream > Fix For: 4.6.0.AM1 > > > After the docker connection is interrupted by force, there is written to console endless output from docker connection: > {code} > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: Retrying request to {}->unix://localhost:80 > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: Retrying request to {}->unix://localhost:80 > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: Retrying request to {}->unix://localhost:80 > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25861) Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25861?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25861. --------------------------------- > Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25861 > URL: https://issues.jboss.org/browse/JBIDE-25861 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker > Affects Versions: 4.5.3.AM3 > Environment: Fedora 27 x86_64 > Reporter: Ondrej Dockal > Assignee: Jeff Johnston > Labels: upstream > Fix For: 4.6.0.AM1 > > > After the docker connection is interrupted by force, there is written to console endless output from docker connection: > {code} > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: Retrying request to {}->unix://localhost:80 > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: Retrying request to {}->unix://localhost:80 > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: Retrying request to {}->unix://localhost:80 > Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute > INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25700) Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25700: ------------------------------------------ a PR to fix the oc binary is on it's way: https://github.com/openshift/origin/pull/19972 > Server adapter: hot deploy of Spring Boot errors with permission issues when rsyncing local->pod (OS Online and CDK) > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25700 > URL: https://issues.jboss.org/browse/JBIDE-25700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: server_adapter, springboot, upstream > Fix For: 4.6.0.Final > > Attachments: permission-error-rsync-fc26.png, server-adapter-rebublish-state.png > > > neither with open.paas.redhat.com > so only when using the CDK. > it seems to be due to the fact that the user in the pod are not the same. > Jeff said: > {quote} > For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF > The user permissions on those folders are the following: > /deployments: writable by user jboss and group root > /deployments/BOOT-INF: writable by user jboss readable only by group root > /deployments/META-INF: writable by user jboss readable only by group root > The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22138: ------------------------------------------ [~ksuzumur] great, we lack user feedback to see how people use OpenShift with Eclipse in the devcycle. We'd love to get more in order to create the helpful thing. Appreciate any feedback a lot! > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.6.x > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26014) Minishift binary downloaded from download runtime wizard does not have .exe extension on windows

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26014?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26014: ---------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.x) > Minishift binary downloaded from download runtime wizard does not have .exe extension on windows > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-26014 > URL: https://issues.jboss.org/browse/JBIDE-26014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.6.0.AM1 > Environment: Windows 10, > Devstudio 12.0.0.AM1-v20180508-1631-B2428 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.6.0.Final > > Attachments: minishift_binary.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26053) Forge New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26053?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26053. ------------------------------ Resolution: Rejected > Forge New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26053 > URL: https://issues.jboss.org/browse/JBIDE-26053 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge 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 Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge 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... {code}JBIDE-26045 #comment Create N&N for Forge 4.6.0.AM3 #close{code}... 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 Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26060) JSF New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26060?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26060. ------------------------------ Resolution: Rejected > JSF New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26060 > URL: https://issues.jboss.org/browse/JBIDE-26060 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html-source-editing > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed JSF 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 JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for JSF 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... {code}JBIDE-26045 #comment Create N&N for JSF 4.6.0.AM3 #close{code}... 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 JSF for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26056) Batch New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26056?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26056. ------------------------------ Resolution: Rejected > Batch New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26056 > URL: https://issues.jboss.org/browse/JBIDE-26056 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Batch 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 Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Batch 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... {code}JBIDE-26045 #comment Create N&N for Batch 4.6.0.AM3 #close{code}... 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 Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26055) Maven New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26055?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26055. ------------------------------ Resolution: Rejected > Maven New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26055 > URL: https://issues.jboss.org/browse/JBIDE-26055 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Maven 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 Maven, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Maven 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... {code}JBIDE-26045 #comment Create N&N for Maven 4.6.0.AM3 #close{code}... 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 Maven for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26057) Server New and Noteworthy for 4.6.0.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26057?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26057. ------------------------------ Resolution: Rejected > Server New and Noteworthy for 4.6.0.AM3 > --------------------------------------------------- > > Key: JBIDE-26057 > URL: https://issues.jboss.org/browse/JBIDE-26057 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Labels: task > Fix For: 4.6.0.AM3 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server 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 Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server 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... {code}JBIDE-26045 #comment Create N&N for Server 4.6.0.AM3 #close{code}... 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 Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 June 2018