November 2016 - jbosstools-issues

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23422: ------------------------------------ This has been asked a long time ago but it is in OpenShift hands > Server Adapter: 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, 4 months

1
0
0 / 0

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

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-23422: --------------------------------------- Maybe a larger topic exposed by this issue, but we should revisit how we debug since I dont think the router should need to be involved. Besides the issues described above, its an extra network hop, it places you behind the service, and doesn't guarantee a specific pod to debug. We should be able to accomplish debug using port forwarding which does not depend on a route or service. We should additionally be able to accomplish pod selection or inference with minimal input from the user. Changing the router timeouts is not going to be available to the non-admin user unless they are working against a dev instance of openshift. > Server Adapter: 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, 4 months

1
0
0 / 0

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

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23422: ------------------------------------- [~jeffmaury] [~jcantrill] could we simply increase the default server timeout value? > Server Adapter: 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8785) The requested profile "local.site" could not be activated because it does not exist

by lakshmi priya (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8785?page=com.atlassian.jira.plugin... ] lakshmi priya commented on JBIDE-8785: -------------------------------------- Hi , i am facing exactly same issue . But i have only one POM.XML under my project . Can you please help me how to resolve this issue .I have like : D:\Java Handson\wf-web\pom.xml I am trying with Maven Tomcat server . Do we need to do anyother configuration . > The requested profile "local.site" could not be activated because it does not exist > ----------------------------------------------------------------------------------- > > Key: JBIDE-8785 > URL: https://issues.jboss.org/browse/JBIDE-8785 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 3.3.0.M1 > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 3.3.0.M1 > > > I'm trying to build JBT using the three steps from http://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3 > a) {noformat}mvn clean install -f build/parent/pom.xml -Dmaven.repo.local=.repository{noformat} > b) {noformat} mvn clean install -f build/target-platform/pom.xml -Pget.local.target -Dmaven.repo.local=.repository{noformat} > c) {noformat} mvn clean install -U -B -fae -e -P local.site -f build/target-platform/pom.xml -Dlocal.site=file://home/igels/Projects/jbt-3.3/trunk/build/target-platform/REPO/ -Dmaven.repo.local=.repository{noformat} > a) and b) are successful but on the step c) I got: > {noformat} > [INFO] Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] Building JBoss Tools Target Platform Definition 0.0.2-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ org.jboss.tools.target.platform --- > [INFO] > [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ org.jboss.tools.target.platform --- > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ org.jboss.tools.target.platform --- > [INFO] Installing /home/igels/Projects/jbt-3.3/trunk/build/target-platform/pom.xml to /home/igels/Projects/jbt-3.3/trunk/.repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT.pom > [INFO] Installing /home/igels/Projects/jbt-3.3/trunk/build/target-platform/multiple.target to /home/igels/Projects/jbt-3.3/trunk/.repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT-multiple.target > [INFO] Installing /home/igels/Projects/jbt-3.3/trunk/build/target-platform/unified.target to /home/igels/Projects/jbt-3.3/trunk/.repository/org/jboss/tools/org.jboss.tools.target.platform/0.0.2-SNAPSHOT/org.jboss.tools.target.platform-0.0.2-SNAPSHOT-unified.target > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 0.495s > [INFO] Finished at: Mon Apr 25 10:49:46 PDT 2011 > [INFO] Final Memory: 3M/119M > [INFO] ------------------------------------------------------------------------ > [WARNING] The requested profile "local.site" could not be activated because it does not exist. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23422: ------------------------------------ Tested and changed the server timeout to 1h. My browser kept waiting for the response. Changing the router config will probably be denied for non admin users > Server Adapter: 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-23136: --------------------------------------- [~dbocharov] the intent here is to remove the image tag at the end of the operation, in order to restore the initial state. So, if the image had a tag before the whole push operation, this tag should be kep at the end. The "temporary" tag which is used to push to the "project" organization on the OpenShift registry should not be kept afterwards, IMO. > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung commented on JBDS-4168: --------------------------------------- Resolving this issue as it was meant for "Docs for Red Hat Developers" and created there https://issues.jboss.org/browse/RHDEVDOCS-293. > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk, documentation > Reporter: Budh Ram Gurung > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like *BOX*. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung resolved JBDS-4168. ----------------------------------- Resolution: Done > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk, documentation > Reporter: Budh Ram Gurung > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like *BOX*. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4168) Updated the "Setting up CDK software components" for adding Vagrant box

by Budh Ram Gurung (JIRA)

[ https://issues.jboss.org/browse/JBDS-4168?page=com.atlassian.jira.plugin.... ] Budh Ram Gurung commented on JBDS-4168: --------------------------------------- Please close this issue. > Updated the "Setting up CDK software components" for adding Vagrant box > ----------------------------------------------------------------------- > > Key: JBDS-4168 > URL: https://issues.jboss.org/browse/JBDS-4168 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: cdk, documentation > Reporter: Budh Ram Gurung > > We have updated our Vagrantfiles so that user can use any customized box name. > This can be easily done with adding an environment variable like *BOX*. > The PR is sent upstream [here|https://github.com/projectatomic/adb-atomic-developer-bundle/pull/569]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ] Supriya Bharadwaj commented on JBDS-4179: ----------------------------------------- Thanks, [~mhusnain]. Added a note in RHDEVDOCS-247 to see this when working on Install guide for 10.2 GA. > DevStudio installer uses console installation instead of wizard > --------------------------------------------------------------- > > Key: JBDS-4179 > URL: https://issues.jboss.org/browse/JBDS-4179 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, installer, upstream > Affects Versions: 10.2.0.GA > Environment: openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Denis Golovin > Fix For: 10.x > > > I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination. > This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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