December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4227: ---------------------------------- Then your JBDS from DevSuite installer should fail if you're missing some DLLs ? > JVM crash in development when launching the CDK server > ------------------------------------------------------ > > Key: JBDS-4227 > URL: https://issues.jboss.org/browse/JBDS-4227 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 10.2.0.GA > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Attachments: hs_err_pid13472.log, hs_err_pid7936.log > > > When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing > {noformat} > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0 > j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39 > j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489 > j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4 > j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91 > j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87 > j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9 > j org.eclipse.core.internal.jobs.Worker.run()V+23 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4230) JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4230?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4230: ---------------------------------- The above document SHOULD say Fedora 23 and 24 are supported. See https://issues.jboss.org/browse/JBIDE-23213 [~mmalina] [~mhusnain] [~rkratky] [~supriya.bharadwaj] Can we get https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... fixed to show *Fedora 23 and 24* instead of *Fedora 22 and 23* ? > JBDS running on Fedora 25 with Wayland makes GUI rendering awful and return "No more handles" every time > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-4230 > URL: https://issues.jboss.org/browse/JBDS-4230 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Environment: Fedora 25 with Wayland > Reporter: Ricardo Martinelli Oliveira > Assignee: Nick Boldt > Priority: Critical > > Workaround: Add GDK_BACKEND=x11 in devstudio.ini file to force use x11 to run JBDS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4227: --------------------------------------- today the VM is not startign at all. based on this comment, it seems that some dlls seems to be loaded on the system: http://eclipse.1072660.n5.nabble.com/Bug-159803-PTY-in-console-mode-on-Wi... I will search if there is some required installation on the OS to have it running > JVM crash in development when launching the CDK server > ------------------------------------------------------ > > Key: JBDS-4227 > URL: https://issues.jboss.org/browse/JBDS-4227 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 10.2.0.GA > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Attachments: hs_err_pid13472.log, hs_err_pid7936.log > > > When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing > {noformat} > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0 > j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39 > j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489 > j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4 > j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91 > j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87 > j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9 > j org.eclipse.core.internal.jobs.Worker.run()V+23 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23659) integrationt-tests: LogsTest is failing and cannot run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23659?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23659: ------------------------------------- Fix Version/s: 4.4.3.AM1 > integrationt-tests: LogsTest is failing and cannot run individually > ------------------------------------------------------------------- > > Key: JBIDE-23659 > URL: https://issues.jboss.org/browse/JBIDE-23659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > > LogsTest cannot run individually, it relies on prior tests to create an EAP application in OpenShift. > Furthermore it is currently failing because of JBIDE-23622 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23659) integrationt-tests: LogsTest is failing and cannot run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23659?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23659: ---------------------------------------- Assignee: Andre Dietisheim > integrationt-tests: LogsTest is failing and cannot run individually > ------------------------------------------------------------------- > > Key: JBIDE-23659 > URL: https://issues.jboss.org/browse/JBIDE-23659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > > LogsTest cannot run individually, it relies on prior tests to create an EAP application in OpenShift. > Furthermore it is currently failing because of JBIDE-23622 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23659) integrationt-tests: LogsTest is failing and cannot run individually

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23659?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23659: ------------------------------------- Story Points: 8 Sprint: devex #125 December 2017 > integrationt-tests: LogsTest is failing and cannot run individually > ------------------------------------------------------------------- > > Key: JBIDE-23659 > URL: https://issues.jboss.org/browse/JBIDE-23659 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > > LogsTest cannot run individually, it relies on prior tests to create an EAP application in OpenShift. > Furthermore it is currently failing because of JBIDE-23622 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23659) integrationt-tests: LogsTest is failing and cannot run individually

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23659: ---------------------------------------- Summary: integrationt-tests: LogsTest is failing and cannot run individually Key: JBIDE-23659 URL: https://issues.jboss.org/browse/JBIDE-23659 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests Affects Versions: 4.4.2.Final Reporter: Andre Dietisheim LogsTest cannot run individually, it relies on prior tests to create an EAP application in OpenShift. Furthermore it is currently failing because of JBIDE-23622 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23657) Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23657?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23657: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Upgrade memoryoptions properties in org.jboss.tools:parent to Java 8 > -------------------------------------------------------------------- > > Key: JBIDE-23657 > URL: https://issues.jboss.org/browse/JBIDE-23657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Marek Novotny > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > There are _memoryoptions1_ and _memoryoptions2_ properties in https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... which are ignored in Java 8 - instead there are options if you need to set it up like: > * -XX:MetaspaceSize for initial size > * -XX:MaxMetaspaceSize for maximum size (it is not required as the value is by default the max memory on runnning machine. > Otherwise just remove them. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4229: ----------------------------- Attachment: nstall.log > If updating CDK installation error reported > ------------------------------------------- > > Key: JBDS-4229 > URL: https://issues.jboss.org/browse/JBDS-4229 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Reporter: Jeff MAURY > Labels: cdk, installer > Fix For: 10.3.0.GA > > Attachments: nstall.log > > > If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4229: ---------------------------------- Then it was caused by Vagrant because I had difficulties removing the box > If updating CDK installation error reported > ------------------------------------------- > > Key: JBDS-4229 > URL: https://issues.jboss.org/browse/JBDS-4229 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Reporter: Jeff MAURY > Labels: cdk, installer > Fix For: 10.3.0.GA > > Attachments: nstall.log > > > If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

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