February 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26445) Remote server cannot start on windows when connected via local remote system type

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26445?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26445: ------------------------------------- Fix Version/s: 4.11.x (was: 4.11.0.AM1) > Remote server cannot start on windows when connected via local remote system type > --------------------------------------------------------------------------------- > > Key: JBIDE-26445 > URL: https://issues.jboss.org/browse/JBIDE-26445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.Final, 4.11.0.AM1 > Environment: windows > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.11.x > > > I got this in Console when trying to start remote EAP 7.x server adapter: > {code} > 'cmd' is not recognized as an internal or external command, operable program or batch file. > {code} > And server is still starting until timeout is reached. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26445) Remote server cannot start on windows when connected via local remote system type

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26445?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26445: ------------------------------------------ [~rob.stryker] ok so what^s the solution for this? And what's the ETA? > Remote server cannot start on windows when connected via local remote system type > --------------------------------------------------------------------------------- > > Key: JBIDE-26445 > URL: https://issues.jboss.org/browse/JBIDE-26445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.Final, 4.11.0.AM1 > Environment: windows > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.11.x > > > I got this in Console when trying to start remote EAP 7.x server adapter: > {code} > 'cmd' is not recognized as an internal or external command, operable program or batch file. > {code} > And server is still starting until timeout is reached. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4756: -------------------------------- Story Points: 2 > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.11.0.GA > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25050: ---------------------------------- Fix Version/s: 4.11.0.Final (was: 4.11.x) > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins > Fix For: 4.11.0.Final > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26454) Proxy usage within QE teams, needs and requirements for deploying

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26454?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26454: ---------------------------------- Fix Version/s: 4.11.0.Final (was: 4.11.0.AM1) > Proxy usage within QE teams, needs and requirements for deploying > ----------------------------------------------------------------- > > Key: JBIDE-26454 > URL: https://issues.jboss.org/browse/JBIDE-26454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: quality > Fix For: 4.11.0.Final > > > Find out: > * existing solutions within RH > * needs of other teams > * usability of open source proxy technologies/solutions > * usage among different OS -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4756: -------------------------------- Fix Version/s: 12.11.0.GA (was: 12.x) > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.11.0.GA > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26453) Adapters/vscode-openshift tooling onboarding

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26453?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26453: ---------------------------------- Fix Version/s: 4.11.0.Final (was: 4.11.0.AM1) > Adapters/vscode-openshift tooling onboarding > -------------------------------------------- > > Key: JBIDE-26453 > URL: https://issues.jboss.org/browse/JBIDE-26453 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: integration-test, quality > Fix For: 4.11.0.Final > > > Jump in adapters stuff: > * go through repos, get familiar with plugins > * start exploring locally, build it, run it > * pick up github issues and start implementing in typescript/java > * increase unit tests coverage > * get familiar with infrastructure -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4713) Fix installer tests

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4713?page=com.atlassian.jira.plugin.... ] Ondrej Dockal updated JBDS-4713: -------------------------------- Fix Version/s: 12.11.0.GA (was: 12.11.0.AM1) > Fix installer tests > ------------------- > > Key: JBDS-4713 > URL: https://issues.jboss.org/browse/JBDS-4713 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Affects Versions: 12.0.0.GA > Reporter: Vojtech Prusa > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 12.11.0.GA > > > Fix devstudio installer tests on jenkins, suites: > * [BYOE Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Post Installation Tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Devstudio Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26561) Cannot download EAP 7.2 server with devstudio

by Mohit Suman (Jira)

[ https://issues.jboss.org/browse/JBIDE-26561?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26561: -------------------------------- Story Points: 5 > Cannot download EAP 7.2 server with devstudio > --------------------------------------------- > > Key: JBIDE-26561 > URL: https://issues.jboss.org/browse/JBIDE-26561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.11.0.AM1 > Environment: F29, devstudio AM1-v20190221-1020-B4114 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.11.0.Final > > Attachments: image-2019-02-26-07-48-15-726.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26562) debugging does not work for eap-cd-basic-s2i template from CRC

by Mohit Suman (Jira)

[ https://issues.jboss.org/browse/JBIDE-26562?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26562: -------------------------------- Story Points: 8 > debugging does not work for eap-cd-basic-s2i template from CRC > -------------------------------------------------------------- > > Key: JBIDE-26562 > URL: https://issues.jboss.org/browse/JBIDE-26562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift, server > Affects Versions: 4.11.0.AM1 > Environment: F29, devstudio AM1-v20190221-1020-B4114, CDK v3.8.0-alpha.1-1 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.11.0.Final > > Attachments: image-2019-02-26-10-19-19-366.png > > > Restarting server adapter in debug for openshift application results in not responding job *Enabling "openshift maven profile"*: !image-2019-02-26-10-19-19-366.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 February 2019