[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] There might be an issue with the Target Platform or the way I consume it, the new features requires to have one bundle in exploded mode ( org.eclipse.cdt.core.win32.x86_64 ) otherwise we hit a JVM crash as I reported in [JBDS-4227]
usually I'm using the TP as directory folder but in this case the bundle is jar.
I tried to configure my local TP as an update site but I have several errors:
!screenshot-1.png|thumbnail!
Do you know if it is an issue with the generated TP which should have the jar exploded? or if it is the way that I'm consuming the TP?
> 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
> Attachments: screenshot-1.png
>
>
> 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
[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 updated JBDS-4227:
----------------------------------
Attachment: ErrorsWhenUsingsUpdateSite.png
> 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: ErrorsWhenUsingsUpdateSite.png, hs_err_pid13472.log, hs_err_pid6816.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
[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:
---------------------------------------
yeah found!!
I'm using a local cached TP on which the org.eclipse.cdt.core.win32.x86-64 is in jar and not unpacked in a folder. If I import the project in the workspace, it is working.
Unfortunately, when I try to use the folder as an update site instead of just a folder, i have several errors reported:
!ErrorsWhenUsingsUpdateSite.png|thumbnail!
> 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: ErrorsWhenUsingsUpdateSite.png, hs_err_pid13472.log, hs_err_pid6816.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
[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 updated JBDS-4227:
----------------------------------
Attachment: hs_err_pid6816.log
> 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_pid6816.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
[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 have the exact same error with latest JVM: https://issues.jboss.org/secure/attachment/12414274/hs_err_pid6816.log
> 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_pid6816.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
[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:
---------------------------------------
it seems that I have the exact same stack in erro report than on in this comment on a JVM issue that was closed as cannot reproduce: https://bugs.openjdk.java.net/browse/JDK-8136749?focusedCommentId=1384136...
I notice that when using my cygwin environment, it is not using the same JVM than what I use on my Windows, I try to change that to use the latest version.
> 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
[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:
---------------------------------------
maybe related to the fact that even in JBDS, it is not crashing but I have bad rendering [JBIDE-23294]
> 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
[JBoss JIRA] (JBIDE-23658) Hibernate console configuration wizard problems - and no way to get specifics
by Jesper Skov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23658?page=com.atlassian.jira.plugi... ]
Jesper Skov commented on JBIDE-23658:
-------------------------------------
1. Unpack archive in workspace root
2. Run 'gradlew eclipse' in dk.may.work folder with JDK8 on path
3. Import projects into Eclipse
4. Select dk.may.work.ejb project in Project Explorer
5. Ctrl-n -> Hibernate Console Configuration
Wized comes up with "Could not create JPA based Configuration"
One time I tried the above, it worked.
But then I assigned a JBoss EAP 6.4 Runtime to the JPA facet, and then the wizard failed with same message.
If the Hibernate Console Configuration is created from Run Configurations instead, it seems to work with this test proejct.
At least until the JBoss EAP rutime is assigned to the JPA facet.
Then this also fails.
There are many factors that affect how the JPA / Hibernate plugin works.
And some of those are clearly problematic in our development.
When all potential causes of problems result in the same message, it is really hard to make sense of.
I would dearly love to be able to see some logging from the plugin.
Please tell me that is possible.
[^empty-clean.zip]
> Hibernate console configuration wizard problems - and no way to get specifics
> -----------------------------------------------------------------------------
>
> Key: JBIDE-23658
> URL: https://issues.jboss.org/browse/JBIDE-23658
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.4.2.Final
> Environment: Neon.1 and Neon.2, Windows 7, targeting Oracle
> Reporter: Jesper Skov
> Assignee: Koen Aers
> Attachments: empty-clean.zip
>
>
> Creating a Hibernate Console Configuration using the wizard fails for most of our projects.
> All the feedback we have is the text in red: "Could not create JPA based Configuration"
> I would have liked to qualify this problem report with some more information. But there is no problems reported in the eclipse log.
> I have tried enabling debugging, as per http://docs.jboss.org/tools/latest/en/hibernatetools/html/plugins.html#de..., without getting any output to the Eclipse Error console, or to the hibernate log file.
> We wonder if maybe the plugin/perspective is just dead (or dying).
> The plugin documentation has snapshots from 2010/2011, and the JBossTools documentation itself (http://docs.jboss.org/tools/latest/) was not updated since 4.1.0/2013.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years