April 2017 - jbosstools-issues - Jboss List Archives

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23422: ------------------------------- Sprint: devex #130 April 2017, devex #131 April 2017 (was: devex #130 April 2017) > 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: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > 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)

7 years

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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23422: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > 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: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > 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)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24377) Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24377?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24377: ------------------------------------ Jobs only check github every 6-8hrs. You need to trigger your job manually if you want it to spin up more often. But because I'm awesome, I've kicked it for you. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=8 > Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24377 > URL: https://issues.jboss.org/browse/JBIDE-24377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > {code} > 14:38:32 [INFO] org.jboss.ide.eclipse.as.management.wf11 ........... FAILURE [ 14.669 s] > 14:38:32 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (get-libs) on project org.jboss.ide.eclipse.as.management.wf11: Unable to find artifact. Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT in jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases) > 14:38:32 [ERROR] > 14:38:32 [ERROR] Try downloading the file manually from the project website. > 14:38:32 [ERROR] > 14:38:32 [ERROR] Then, install it using the command: > 14:38:32 [ERROR] mvn install:install-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file > 14:38:32 [ERROR] > 14:38:32 [ERROR] Alternatively, if you host your own repository you can deploy the file there: > 14:38:32 [ERROR] mvn deploy:deploy-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > 14:38:32 [ERROR] > 14:38:32 [ERROR] > 14:38:32 [ERROR] org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT > 14:38:32 [ERROR] > 14:38:32 [ERROR] from the specified remote repositories: > 14:38:32 [ERROR] redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/, releases=true, snapshots=false), > 14:38:32 [ERROR] redhat-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=false), > 14:38:32 [ERROR] jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases, releases=true, snapshots=true), > 14:38:32 [ERROR] jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/, releases=true, snapshots=true), > 14:38:32 [ERROR] jbosstools-experiments (https://repository.jboss.org/nexus/content/repositories/jbosstools-experi..., releases=true, snapshots=true), > 14:38:32 [ERROR] jbosstools-base (http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b..., releases=false, snapshots=false), > 14:38:32 [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true), > 14:38:32 [ERROR] jboss-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=true), > 14:38:32 [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false) > 14:38:32 [ERROR] -> [Help 1] > {code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24377) Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24377?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24377: ------------------------------------- Seems the snapshot disappeared and beta16 is available now. So I've fixed that. Waiting for a build to verify > Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24377 > URL: https://issues.jboss.org/browse/JBIDE-24377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > {code} > 14:38:32 [INFO] org.jboss.ide.eclipse.as.management.wf11 ........... FAILURE [ 14.669 s] > 14:38:32 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (get-libs) on project org.jboss.ide.eclipse.as.management.wf11: Unable to find artifact. Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT in jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases) > 14:38:32 [ERROR] > 14:38:32 [ERROR] Try downloading the file manually from the project website. > 14:38:32 [ERROR] > 14:38:32 [ERROR] Then, install it using the command: > 14:38:32 [ERROR] mvn install:install-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file > 14:38:32 [ERROR] > 14:38:32 [ERROR] Alternatively, if you host your own repository you can deploy the file there: > 14:38:32 [ERROR] mvn deploy:deploy-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > 14:38:32 [ERROR] > 14:38:32 [ERROR] > 14:38:32 [ERROR] org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT > 14:38:32 [ERROR] > 14:38:32 [ERROR] from the specified remote repositories: > 14:38:32 [ERROR] redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/, releases=true, snapshots=false), > 14:38:32 [ERROR] redhat-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=false), > 14:38:32 [ERROR] jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases, releases=true, snapshots=true), > 14:38:32 [ERROR] jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/, releases=true, snapshots=true), > 14:38:32 [ERROR] jbosstools-experiments (https://repository.jboss.org/nexus/content/repositories/jbosstools-experi..., releases=true, snapshots=true), > 14:38:32 [ERROR] jbosstools-base (http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b..., releases=false, snapshots=false), > 14:38:32 [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true), > 14:38:32 [ERROR] jboss-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=true), > 14:38:32 [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false) > 14:38:32 [ERROR] -> [Help 1] > {code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4344) CDK installation fails if an older .minishift configuration exists

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4344?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4344: -------------------------------- Fix Version/s: 10.4.0.GA > CDK installation fails if an older .minishift configuration exists > ------------------------------------------------------------------ > > Key: JBDS-4344 > URL: https://issues.jboss.org/browse/JBDS-4344 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.AM2, 10.4.0.GA > Environment: windows 10 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > > If a ~/.minishift folder with some older configuration exists when installing CDK 3, it just fails silently. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4335) Clearly mark third party components available for installation on confirmation page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4335?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4335: -------------------------------- Fix Version/s: 10.4.0.GA > Clearly mark third party components available for installation on confirmation page > ----------------------------------------------------------------------------------- > > Key: JBDS-4335 > URL: https://issues.jboss.org/browse/JBDS-4335 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.AM1, 10.4.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.GA > > > Current UI does not distinguish Red Hat products and third party components available for installation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1098) Update Neon Target Platform to fix stand-alone installers

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1098: --------------------------------- Summary: Update Neon Target Platform to fix stand-alone installers Key: JBTIS-1098 URL: https://issues.jboss.org/browse/JBTIS-1098 Project: JBoss Tools Integration Stack Issue Type: Task Components: target-platform Affects Versions: 4.4.3.CR1-TP Reporter: Paul Leacu Assignee: Paul Leacu Fix For: 4.4.3.CR2-TP The standalone installers fail because <unit id="org.sonatype.tycho.m2e.feature.feature.group" version="0.8.1.201704211436"/> has been pushed down to the Devstudio core TP. We need it back (duplicated) to get the standalone installer sto be stand-alone. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3827) JBDS installation fails when (windows) user has non-ascii chars in the name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3827: -------------------------------- Fix Version/s: 10.4.0.GA > JBDS installation fails when (windows) user has non-ascii chars in the name > --------------------------------------------------------------------------- > > Key: JBDS-3827 > URL: https://issues.jboss.org/browse/JBDS-3827 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1, 10.4.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.4.0.GA > > > I have created a user named Pakoň and tried to install everything into the default folder. JBDS failed with: > {noformat}Fri, 15 Apr 2016 12:38:40 GMT-ERROR: jbds - Error: Command failed: c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true -jar C:\WINDOWS\7zS9F06.tmp\jbds.jar C:\Users\Pakoň\AppData\Local\Temp\jbds-autoinstall.xml > - ERROR - > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.<init>(FileInputStream.java:138) > at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(AutomatedInstaller.java:564) > at com.izforge.izpack.installer.AutomatedInstaller.<init>(AutomatedInstaller.java:86) > at com.izforge.izpack.installer.Installer.main(Unknown Source){noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-4377. --------------------------------- Resolution: Done I've added one extra feature to install in DevSuite > installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore > ---------------------------------------------------------------------------------------------------------- > > Key: JBDS-4377 > URL: https://issues.jboss.org/browse/JBDS-4377 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, target-platform > Affects Versions: 10.4.0.AM3 > Environment: Windows: DevSuite Installer v1.4 AM3 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > Attachments: devstudio104am3-installer-missing-unpatched-plugin.png > > > Denis reports a problem using the installer jar in automated mode (using .xml script). > Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script. > Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well. > !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail! > So we need to figure out how to include BOTH versions in the installer jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4377) installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4377?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4377: ----------------------------- Sprint: (was: devex #131 May 2017) > installer jar does not contain both the patched and unpatched version of org.eclipse.wst.common.modulecore > ---------------------------------------------------------------------------------------------------------- > > Key: JBDS-4377 > URL: https://issues.jboss.org/browse/JBDS-4377 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, target-platform > Affects Versions: 10.4.0.AM3 > Environment: Windows: DevSuite Installer v1.4 AM3 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > Attachments: devstudio104am3-installer-missing-unpatched-plugin.png > > > Denis reports a problem using the installer jar in automated mode (using .xml script). > Works fine when run `java -jar \*installer\*.jar` and `echo 1 | java -jar \*installer\*.jar -console` but fails when run against an xml install script. > Seems to be caused by the fact that the installer only contains the patched version of org.eclipse.wst.common.modulecore 1.2.501, and not the 1.2.500 version that's in the TP as well. > !devstudio104am3-installer-missing-unpatched-plugin.png|thumbnail! > So we need to figure out how to include BOTH versions in the installer jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2017