November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22773: ------------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.2.AM3) > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.4.2.Final > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23006: ------------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.2.AM3) Sprint: devex #119 August 2016, devex #123 November 2016 (was: devex #119 August 2016, devex #122 October 2016) > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.2.Final > > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23421) Terminating Server Adapter running in debug mode does not terminate Node.js debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23421?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23421: ------------------------------------- Labels: nodejs openshift_v3 server_adapter (was: ) > Terminating Server Adapter running in debug mode does not terminate Node.js debug session > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23421 > URL: https://issues.jboss.org/browse/JBIDE-23421 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.2.Final > > > Stopping server adapter will not stop the V8 debug session - one should still terminate it manually. This might be coupled with the replication controller issue - https://issues.jboss.org/browse/JBIDE-23412 due to the fact that after stopping server adapter app is still running in the DEV_MODE (which is unexpected behaviour IMO) and debug session is still alive. Moreover, If you try to restart the adapter the debug session will be terminated (expected behaviour), so it might be just a side effect of other issue -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23422: ------------------------------------- Labels: nodejs openshift_v3 server_adapter (was: ) > Node.js debug session is terminated after ~1 minute and browser shows 502 error > ------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.2.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23422: ------------------------------------- Priority: Critical (was: Major) > Node.js debug session is terminated after ~1 minute and browser shows 502 error > ------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.2.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23005) [Watcher] Server Adapter: Stuck on creating/publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23005: ------------------------------------------ [~mlabuda] In the [github issue|https://github.com/openshift/origin/issues/9726] they're asking us to try different things so that we can help them to tackle this. Can you please follow up there? > [Watcher] Server Adapter: Stuck on creating/publishing > ------------------------------------------------------ > > Key: JBIDE-23005 > URL: https://issues.jboss.org/browse/JBIDE-23005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter, upstream > Fix For: 4.4.2.Final > > Attachments: stucked_server_adapter > > > When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23321: ------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.2.AM3) > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.2.Final > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23321) Integration tests for OpenShift Node.js debugger

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23321?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23321: ------------------------------------ The tests itself are relatively easy to implement because we have some integration tests for nodejs debugger in JSDT. The problem with openshift is that until now we do not have working environment in central-ci. So I started working on that first. There are basically 3 options: # use external openshift server # run cdk # run minishift Option 1) is not very reliable for tests - the server may be down during tests execution, performance may vary according to the current load, the tests need to cleanup etc. Option 2) is good, but it has more dependencies than Option 3), eg. vagrant etc. Option 3) easy to run, only kvm dependency. But there are no openshift templates deployed. I'm working on option 3 POC. > Integration tests for OpenShift Node.js debugger > ------------------------------------------------- > > Key: JBIDE-23321 > URL: https://issues.jboss.org/browse/JBIDE-23321 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, openshift > Affects Versions: 4.4.2.AM1 > Reporter: Ilya Buziuk > Assignee: Pavol Srna > Fix For: 4.4.2.AM3 > > > Node.js Debugging support implemented as part of https://issues.jboss.org/browse/JBIDE-22225 > Should be covered with red deer integration tests. Basically, test coverage of Node.js Debugger facilities already covered with red deer in JSDT project - https://git.eclipse.org/r/#/c/82836/ > However, implementing smth. similar for OpenShift will be much trickier. Basically, there is an integration test *org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.PublishChangesTest* which is used for server adapter publishing. For now this test is not sustainable due to https://issues.jboss.org/browse/JBIDE-23005 . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23055) Repeated toggling of JAX-RS support on project does not cause it to rebuild

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23055?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-23055: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.2.AM3) > Repeated toggling of JAX-RS support on project does not cause it to rebuild > --------------------------------------------------------------------------- > > Key: JBIDE-23055 > URL: https://issues.jboss.org/browse/JBIDE-23055 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.1.AM3 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.4.x > > > When JAX-RS support is toggled in a project's preferences, clicking Apply will rebuild the project and JAX-RS services will (dis)/appear and validation is enabled/disabled. > But if without closing the preferences I toggle JAX-RS support again and press Apply, nothing happens - the project is not built with the new settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4119) Some paths are too long for the uninstaller

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4119?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4119: ------------------------------ Fix Version/s: 10.2.0.GA (was: 10.2.0.AM3) > Some paths are too long for the uninstaller > ------------------------------------------- > > Key: JBDS-4119 > URL: https://issues.jboss.org/browse/JBDS-4119 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.2.0.GA > > > It is possible to install everything and still get 'path too long' error on uninstallation. For example it seems that drive labels are in fact factored into the 255 character path limit in powershell. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 November 2016