December 2016 - jbosstools-issues

[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: --------------------------------------- I'm using Vagrant 1.8.1. i just tried also from another JBDS installed from the development suite installer and it works. So either it doesn't like something in my development mode or there is a missing implicit dependency in the jbds Integration Stack. I still don't know how to investigate in the vm which is started why the OpenShift instance inside it is not working > 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)

9 years, 3 months

1
0
0 / 0

[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: ---------------------------------- Works for me with the CDK from the DevSuite installer. Which vagrant do you use ? > 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23021 at 12/20/16 11:48 AM: --------------------------------------------------------------- Need to expand functionality of https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... so it can be used to diff github vs. json instead of just json vs. json. Once the script is enhanced, can then add that into https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... so it can run more fequently & verify that all commits are done before doing a stage. Could also create a buildflow orchestrator job, so that missing commits can be built and pushed to download.jboss.org. was (Author: nickboldt): Need to expand functionality of https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... so it can be used to diff github vs. json instead of just json vs. json. Once the script is enhanced, can then add that into https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... so it can run more fequently & verify that all commits are done before doing a stage. Could also create a buildflow orchestrator job, so that missing commits can be built and pushed to download.jboss.org. > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ] Aurélien Pupier commented on JBTIS-1008: ---------------------------------------- [~pleacu] currently i'm facing this issue https://issues.jboss.org/browse/JBDS-4227 in development mode but we don't know what is happening, it can be an issue with the Target Platform or it can be something totally different. just to let you know that i'm still tryign to validating that I have all that I need in the Target Platform > Provide OpenShift 3 support feature in Integration Stack Target Platform > ------------------------------------------------------------------------ > > Key: JBTIS-1008 > URL: https://issues.jboss.org/browse/JBTIS-1008 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > My goal is to be able to leverage OpenShift 3 and CDK integration. > I think that the required feature is org.jboss.tools.openshift.feature > [~adietish]Can you confirm that it is the right feature? > *Reason:* Leverage OpenShift 3 and CDK integration. > *Project page/sources:* > *Version:* 3.3.1 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .devstudiois > *Include in JBDS:* Yes (DevtsudioIS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 commented on JBIDE-23657: ------------------------------------ PRs updated. Please +1 / -1 as appropriate. > 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.AM2 > > > 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)

9 years, 3 months

1
0
0 / 0

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

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23657?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBIDE-23657: --------------------------------------- yep, use only *-XX:MetaspaceSize* for initial size (top limit is literally useful only if you need to limit consumption of all memory on your machine) or remove it all ;) > 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.AM2 > > > 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)

9 years, 3 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23657?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23657: ------------------------------------ One of the big plus of metaspace vs PermGen space is that it can auto increase to I would suggest removing sizing options of metaspace instead of mapping permgen sizes to metaspace sizing > 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.AM2 > > > 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)

9 years, 3 months

1
0
0 / 0

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

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23657?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBIDE-23657: --------------------------------------- [~nickboldt] yes, thanks! > 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.AM2 > > > 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)

9 years, 3 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 edited comment on JBIDE-23657 at 12/20/16 10:28 AM: --------------------------------------------------------------- PRs: https://github.com/jbosstools/jbosstools-build/pull/239 https://github.com/jbdevstudio/jbdevstudio-product/pull/438 [~manaRH] is that what you were looking for? Any objections to increasing the MetaspaceSize too? cc: [~jeffmaury] [~fbricon] [~mickael_istria] was (Author: nickboldt): PRs: https://github.com/jbosstools/jbosstools-build/pull/239 https://github.com/jbdevstudio/jbdevstudio-product/pull/438 > 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.AM2 > > > 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)

9 years, 3 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.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 > Fix For: 4.4.3.AM2 > > > 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)

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