January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25375: ------------------------------------- Fix Version/s: 4.5.2.Final (was: 4.5.2.AM3) > Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25375 > URL: https://issues.jboss.org/browse/JBIDE-25375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM1 > Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.Final > > > {code:java} > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520 > java.version=1.8.0_144 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25375) Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25375?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25375: ------------------------------------- Sprint: devex #143 January 2018 (was: devex #142 December 2017) > Server adapter: Problem occured during debugging of Fuse app deployed on open.paas.redhat.com > --------------------------------------------------------------------------------------------- > > Key: JBIDE-25375 > URL: https://issues.jboss.org/browse/JBIDE-25375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM1 > Environment: F27 + open.paas.redhat.com + DevStudio 11.2.0.AM1-v20171106-0622-B1520 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.Final > > > {code:java} > Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) > org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 46271 on localhost > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:639) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:643) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:410) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:395) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:276) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:191) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:167) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:98) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > eclipse.buildId=11.2.0.AM1-v20171106-0622-B1520 > java.version=1.8.0_144 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25512) OpenShift-Restclient-java: release and use 5.9.4.Final in OpenShift tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25512?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25512: ------------------------------------- Sprint: devex #143 January 2018 (was: devex #142 December 2017) > OpenShift-Restclient-java: release and use 5.9.4.Final in OpenShift tooling > --------------------------------------------------------------------------- > > Key: JBIDE-25512 > URL: https://issues.jboss.org/browse/JBIDE-25512 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25512) OpenShift-Restclient-java: release and use 5.9.4.Final in OpenShift tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25512?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25512: ------------------------------------- Fix Version/s: 4.5.2.Final (was: 4.5.2.AM3) > OpenShift-Restclient-java: release and use 5.9.4.Final in OpenShift tooling > --------------------------------------------------------------------------- > > Key: JBIDE-25512 > URL: https://issues.jboss.org/browse/JBIDE-25512 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25545) CDK run via jenkins requires proper ssh to be used on windows slaves

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25545?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25545: ---------------------------------- Git Pull Request: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-cloud-slave..., https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m... (was: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-cloud-slave...) > CDK run via jenkins requires proper ssh to be used on windows slaves > -------------------------------------------------------------------- > > Key: JBIDE-25545 > URL: https://issues.jboss.org/browse/JBIDE-25545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.Final > Environment: windows, jenkins > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.Final > > > When CDK is being run via jenkins on windows slaves, we can see that improper ssh is used to connect to rhel guest, and command that follows will fail: > ie.: > {code} > 14:17:12 &{[-F /dev/null -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none docker(a)127.0.0.1 -o IdentitiesOnly=yes -i C:\Users\Admin\.minishift\machines\minishift\id_rsa -p 49784] C:\ProgramData\chocolatey\bin\ssh.exe <nil>} > 14:17:12 About to run SSH command: > 14:17:12 printf '%s' '-----BEGIN CERTIFICATE----- > 14:17:12 MIICzTCCAbWgAwIBAgIQIo4gxNYty+nXDs+ketnGKDANBgkqhkiG9w0BAQsFADAQ > ... > lwvqfWHvZ3Jo94PygMlhLQTWVMVpXAIBdx8ypeeVyMhcUuPJDa01nhPr3nhMBKPj > 14:17:12 fg== > 14:17:12 -----END CERTIFICATE----- > 14:17:12 ' | sudo tee /etc/docker/ca.pem > 14:17:12 SSH cmd err, output: exit status 1: bash: -c: line 0: unexpected EOF while looking for matching `'' > 14:17:12 bash: -c: line 1: syntax error: unexpected end of file > 14:17:12 > 14:17:14 FAIL E0103 14:17:14.245649 4008 start.go:364] Error starting the VM: Error creating the VM. Error creating machine: Error running provisioning: ssh command error > {code} > This is because CDK will use first ssh on windows path. Fix for this could be position proper ssh (one from cygwin64 installation) on the path beginning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24880) deprecate SOAP from jbosstools-webservices

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24880?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24880: ------------------------------- Sprint: devex #143 January 2018 (was: devex #142 December 2017) > deprecate SOAP from jbosstools-webservices > ------------------------------------------ > > Key: JBIDE-24880 > URL: https://issues.jboss.org/browse/JBIDE-24880 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, webservices > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.AM3 > > > [~psrna] suggests we deprecate the SOAP stuff in Webservices. > I'll let him explain which feature(s) are included in this suggestion. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25276: ------------------------------- Sprint: devex #139 October 2017, devex #143 January 2018 (was: devex #139 October 2017, devex #142 December 2017) > intermittent test failures in webservices > ----------------------------------------- > > Key: JBIDE-25276 > URL: https://issues.jboss.org/browse/JBIDE-25276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.2.AM3 > > > Various tests are failing intermittently. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2 > Can these be fixed or if not, disabled, so that we can consistently get green builds? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25513) update minimum target platform to Oxygen.1a

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25513?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25513. ------------------------------ Resolution: Done > update minimum target platform to Oxygen.1a > ------------------------------------------- > > Key: JBIDE-25513 > URL: https://issues.jboss.org/browse/JBIDE-25513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform, updatesite, upstream > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.AM3 > > > {quote} > Jeff: I'm wondering how do we manage this minimum requirement (Oxygen1A) then ? > Nick: would move to 4.71.0.Final or 4.72.0.AM3-SNAPSHOT > 4.71.0 = Oxygen.1a; 4.72.0 = Oxygen.2 > Jeff: 4.71.0.Final > Nick: if you're suggesting we need to do that now, please open a JIRA (and you can even attach a PR to fix the parent pom. It's one line. > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25441: ------------------------------------ Yes I just merged it so you may test it in a couple of hours/days > Problems with CDI Builder and scanning Jars which support Java 9 > ---------------------------------------------------------------- > > Key: JBIDE-25441 > URL: https://issues.jboss.org/browse/JBIDE-25441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi, common > Affects Versions: 4.5.1.Final, 4.5.2.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.AM3 > > > As reported in https://developer.jboss.org/message/978446?et=watches.email.thread#978446: > {quote} > Setup: > * Eclipse Oxygen 4.7.1 > * JBoss Tools 4.5.1.Final (also tested with latest development version 4.5.2.AM1) > * An maven web application with certain dependencies > ** So far, we found two dependencies, which lead to this jandex scaning error after upgrading to latest version > ** org.apache.logging.log4j version 2.10.0 > ** org.ow2.asm version 6.0 > > This leads to an CDI Builder IllegalStateException - see exception trace below. > Both dependencies started support for Java 9, which seems to cause this exception. > > *Apache Log4j 2.10.0 released*: http://mail-archives.apache.org/mod_mbox/www-announce/201711.mbox/%3Cdf95... > > {code} > !MESSAGE Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'Webapp'. > !STACK 0 > java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 24 > at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:665) > at org.jboss.jandex.Indexer.index(Indexer.java:699) > at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56) > at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150) > at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-586) Fix JVM crash on Wayland when running SWT tests

by Eric Williams (JIRA)

Eric Williams created ERT-586: --------------------------------- Summary: Fix JVM crash on Wayland when running SWT tests Key: ERT-586 URL: https://issues.jboss.org/browse/ERT-586 Project: Eclipse Release Train Issue Type: Task Reporter: Eric Williams Assignee: Eric Williams -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018