September 2016 - jbosstools-issues

[JBoss JIRA] (ERT-396) Connection is not added(same parameters, different name) [EBZ#499854]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-396?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-396: ------------------------------ Sprint: devex #119 August 2016 > Connection is not added(same parameters, different name) [EBZ#499854] > --------------------------------------------------------------------- > > Key: ERT-396 > URL: https://issues.jboss.org/browse/ERT-396 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > Steps to reproduce: > 1. Create connection in Docker Explorer > 2. Create connection in Docker Explorer with same parameters as in step 1, but different name. > The second connection is not added. > Docker tooling version: > 2.1.0201608170955 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-396) Connection is not added(same parameters, different name) [EBZ#499854]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-396?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon resolved ERT-396. ------------------------------- Resolution: Done Fixed upstream > Connection is not added(same parameters, different name) [EBZ#499854] > --------------------------------------------------------------------- > > Key: ERT-396 > URL: https://issues.jboss.org/browse/ERT-396 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Affects Versions: Neon (4.6) > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > Steps to reproduce: > 1. Create connection in Docker Explorer > 2. Create connection in Docker Explorer with same parameters as in step 1, but different name. > The second connection is not added. > Docker tooling version: > 2.1.0201608170955 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22657) smart import nullpointer

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22657?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22657: ----------------------------------- Fix Version/s: 4.4.1.Final > smart import nullpointer > ------------------------ > > Key: JBIDE-22657 > URL: https://issues.jboss.org/browse/JBIDE-22657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.4.1.Final, 4.5.0.AM1 > > > when using smartimport to import https://github.com/maxandersen/imapfilter-docker.git from disk I got a NPE in jaxrs: > {code} > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.ui.internal.importer.JaxRsConfigurator.canConfigure(JaxRsConfigurator.java:66) > at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.importProjectAndChildrenRecursively(SmartImportJob.java:466) > at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.run(SmartImportJob.java:242) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ERT-396) Connection is not added(same parameters, different name) [EBZ#499854]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-396?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon reassigned ERT-396: --------------------------------- Assignee: Xavier Coulon > Connection is not added(same parameters, different name) [EBZ#499854] > --------------------------------------------------------------------- > > Key: ERT-396 > URL: https://issues.jboss.org/browse/ERT-396 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > > Steps to reproduce: > 1. Create connection in Docker Explorer > 2. Create connection in Docker Explorer with same parameters as in step 1, but different name. > The second connection is not added. > Docker tooling version: > 2.1.0201608170955 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23037) JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23037?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23037: ------------------------------------ Could you, please, provide steps to reproduce? Or maybe [~pleacu] could verify this himself? > JBossASHandler instantiating RuntimeDefinition when server bean type is Fuse > ---------------------------------------------------------------------------- > > Key: JBIDE-23037 > URL: https://issues.jboss.org/browse/JBIDE-23037 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.4.1.AM2 > Reporter: Paul Leacu > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM3 > > > Recent changes in runtimes.core meant to improve efficiency then keep track of which AbstractRuntimeDetectorDelegate created the runtime definition (the thing you see in the dialog) and when it seems time to actually create it we go back to that one that created it so we dont go asking 10 people to create things they dont know about. > ref: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > This is critical to the stand-alone installer for Fuse that includes a supplemental runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22657) smart import nullpointer

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22657?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22657: ----------------------------------- Fix Version/s: (was: 4.4.1.Final) > smart import nullpointer > ------------------------ > > Key: JBIDE-22657 > URL: https://issues.jboss.org/browse/JBIDE-22657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.5.0.AM1 > > > when using smartimport to import https://github.com/maxandersen/imapfilter-docker.git from disk I got a NPE in jaxrs: > {code} > java.lang.NullPointerException > at org.jboss.tools.ws.jaxrs.ui.internal.importer.JaxRsConfigurator.canConfigure(JaxRsConfigurator.java:66) > at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.importProjectAndChildrenRecursively(SmartImportJob.java:466) > at org.eclipse.ui.internal.wizards.datatransfer.SmartImportJob.run(SmartImportJob.java:242) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4033) Cannot add virtualbox box files on windows duringinstallation CDK via devstuite bundle installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-4033?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-4033: ----------------------------- > Cannot add virtualbox box files on windows duringinstallation CDK via devstuite bundle installer > ------------------------------------------------------------------------------------------------ > > Key: JBDS-4033 > URL: https://issues.jboss.org/browse/JBDS-4033 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 1.1.0.GA > Environment: NB: windows 10 Pro, x86_64 > Virtual machines: > windows 10 Enterprise, x86_64 > windows 7 Pro, x86_64, SP1 > Reporter: Ondrej Dockal > Assignee: Denis Golovin > Priority: Critical > > Installation ends up with CDK failed status. Others installation of components is completed. > Error message from install log: > ------------------------------ > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute options { > "env": { > "ALLUSERSPROFILE": "C:\\ProgramData", > "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming", > "CommonProgramFiles": "C:\\Program Files\\Common Files", > "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files", > "CommonProgramW6432": "C:\\Program Files\\Common Files", > "COMPUTERNAME": "SOME-PC", > "ComSpec": "C:\\Windows\\system32\\cmd.exe", > "FP_NO_HOST_CHECK": "NO", > "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q", > "HOMEDRIVE": "C:", > "HOMEPATH": "\\Users\\jbossqa", > "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local", > "LOGONSERVER": "\\\\SOME-PC", > "NUMBER_OF_PROCESSORS": "2", > "OS": "Windows_NT", > "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\DevelopmentSuite\\jdk8\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;C:\\DevelopmentSuite\\vagrant\\bin;bin;C:\\DevelopmentSuite\\virtualbox\\", > "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC", > "PROCESSOR_ARCHITECTURE": "AMD64", > "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel", > "PROCESSOR_LEVEL": "6", > "PROCESSOR_REVISION": "3c01", > "ProgramData": "C:\\ProgramData", > "ProgramFiles": "C:\\Program Files", > "ProgramFiles(x86)": "C:\\Program Files (x86)", > "ProgramW6432": "C:\\Program Files", > "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\", > "PUBLIC": "C:\\Users\\Public", > "SystemDrive": "C:", > "SystemRoot": "C:\\Windows", > "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", > "USERDOMAIN": "Some-PC", > "USERNAME": "jbossqa", > "USERPROFILE": "C:\\Users\\jbossqa", > "VAGRANT_DETECTED_OS": "cygwin", > "VBOX_MSI_INSTALL_PATH": "C:\\DevelopmentSuite\\virtualbox\\", > "windir": "C:\\Windows", > "windows_tracing_flags": "3", > "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", > "__COMPAT_LAYER": "VistaSetup" > }, > "cwd": "c:\\DevelopmentSuite\\cdk\\boxes" > } > Wed, 31 Aug 2016 11:23:39 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box > [0;31mAn error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. > ---------------------- > After manual attempt to add box via cli with commad: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box: > --------------------- > C:\DevelopmentSuite\cdk\boxes>vagrant box add --name cdkv2 rhel-vagrant-virtualb > ox.box > ==> box: Box file was not detected as metadata. Adding it directly... > ==> box: Adding box 'cdkv2' (v0) for provider: > box: Unpacking necessary files from: file://C:/DevelopmentSuite/cdk/boxes/rh > el-vagrant-virtualbox.box > box: > An error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4033) Cannot add virtualbox box files on windows duringinstallation CDK via devstuite bundle installer

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBDS-4033: ----------------------------------- Summary: Cannot add virtualbox box files on windows duringinstallation CDK via devstuite bundle installer Key: JBDS-4033 URL: https://issues.jboss.org/browse/JBDS-4033 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 1.1.0.GA Environment: NB: windows 10 Pro, x86_64 Virtual machines: windows 10 Enterprise, x86_64 windows 7 Pro, x86_64, SP1 Reporter: Ondrej Dockal Assignee: Denis Golovin Priority: Critical Installation ends up with CDK failed status. Others installation of components is completed. Error message from install log: ------------------------------ Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute command vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box Wed, 31 Aug 2016 11:23:37 GMT-INFO: cdk - Execute options { "env": { "ALLUSERSPROFILE": "C:\\ProgramData", "APPDATA": "C:\\Users\\jbossqa\\AppData\\Roaming", "CommonProgramFiles": "C:\\Program Files\\Common Files", "CommonProgramFiles(x86)": "C:\\Program Files (x86)\\Common Files", "CommonProgramW6432": "C:\\Program Files\\Common Files", "COMPUTERNAME": "SOME-PC", "ComSpec": "C:\\Windows\\system32\\cmd.exe", "FP_NO_HOST_CHECK": "NO", "GOOGLE_API_KEY": "AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q", "HOMEDRIVE": "C:", "HOMEPATH": "\\Users\\jbossqa", "LOCALAPPDATA": "C:\\Users\\jbossqa\\AppData\\Local", "LOGONSERVER": "\\\\SOME-PC", "NUMBER_OF_PROCESSORS": "2", "OS": "Windows_NT", "Path": "C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\;C:\\DevelopmentSuite\\jdk8\\bin;C:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cdk\\bin;c:\\DevelopmentSuite\\vagrant\\bin;c:\\DevelopmentSuite\\cygwin\\bin;C:\\DevelopmentSuite\\vagrant\\bin;bin;C:\\DevelopmentSuite\\virtualbox\\", "PATHEXT": ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC", "PROCESSOR_ARCHITECTURE": "AMD64", "PROCESSOR_IDENTIFIER": "Intel64 Family 6 Model 60 Stepping 1, GenuineIntel", "PROCESSOR_LEVEL": "6", "PROCESSOR_REVISION": "3c01", "ProgramData": "C:\\ProgramData", "ProgramFiles": "C:\\Program Files", "ProgramFiles(x86)": "C:\\Program Files (x86)", "ProgramW6432": "C:\\Program Files", "PSModulePath": "C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\", "PUBLIC": "C:\\Users\\Public", "SystemDrive": "C:", "SystemRoot": "C:\\Windows", "TEMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", "TMP": "C:\\Users\\jbossqa\\AppData\\Local\\Temp", "USERDOMAIN": "Some-PC", "USERNAME": "jbossqa", "USERPROFILE": "C:\\Users\\jbossqa", "VAGRANT_DETECTED_OS": "cygwin", "VBOX_MSI_INSTALL_PATH": "C:\\DevelopmentSuite\\virtualbox\\", "windir": "C:\\Windows", "windows_tracing_flags": "3", "windows_tracing_logfile": "C:\\BVTBin\\Tests\\installpackage\\csilogfile.log", "__COMPAT_LAYER": "VistaSetup" }, "cwd": "c:\\DevelopmentSuite\\cdk\\boxes" } Wed, 31 Aug 2016 11:23:39 GMT-ERROR: cdk - Error: Command failed: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box [0;31mAn error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again. ---------------------- After manual attempt to add box via cli with commad: vagrant box add --name cdkv2 rhel-vagrant-virtualbox.box: --------------------- C:\DevelopmentSuite\cdk\boxes>vagrant box add --name cdkv2 rhel-vagrant-virtualb ox.box ==> box: Box file was not detected as metadata. Adding it directly... ==> box: Adding box 'cdkv2' (v0) for provider: box: Unpacking necessary files from: file://C:/DevelopmentSuite/cdk/boxes/rh el-vagrant-virtualbox.box box: An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22998) update 4.60.1.Final TPs to latest Docker/Vagrant tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22998?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-22998: --------------------------------------- Great ! thanks, [~nickboldt] ! > update 4.60.1.Final TPs to latest Docker/Vagrant tooling > -------------------------------------------------------- > > Key: JBIDE-22998 > URL: https://issues.jboss.org/browse/JBIDE-22998 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > Attachments: docker-rc1-vs-rc2.p2diff.txt > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/updates-docker-nightly/ > We should include the latest docker tooling 2.1 once it's ready to be included in the TP. > cc: [~xcoulon] [~fbricon] [~akazakov] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 4 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23006: ------------------------------------ Seems to be related to the first exchanges made with Openshift. If your Openshift connection is defined without password stored, then you will get the credential dialog and you will get 2 leaks detected. If your Openshift connection is defined with a password, then you will get only 1 leak which seem logical as you will have two initial exchanges if your password is not stored. I added a throwable object to the leak mechanism in okhttp in order to display the stacktrace of the allocation path but didn't figure why the leak appears but found several places where Response objects are not closed. Fixing didn't remove the message(s) > 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.1.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 (v6.4.11#64026)

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 September 2016