[JBoss JIRA] (JBIDE-21812) Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21812?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21812.
---------------------------------
> Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1
> ----------------------------------------------------------------------
>
> Key: JBIDE-21812
> URL: https://issues.jboss.org/browse/JBIDE-21812
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final, 4.3.1.Beta2
> Environment: JBoss AS 7.1.1
> Eclipse Mars.2 4.5.2
> IPv4 stack specified
> Local host connectivity (127.0.0.1 specified)
> Reporter: William Darby
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final
>
> Attachments: eclipse.log
>
>
> When starting JBoss from within Eclipse the following error appears on the console:
> 17:25:23,182 ERROR [org.jboss.remoting.remote.connection] (Remoting "hostname:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine
> This occurs with or without firewall/anti-virus enabled.
> And with the startup/shutdown pollers set to Management Service or Web Port.
> Also with Server Ports specified or 'Detected from Local Runtime'
> It occurs occasionally on the first server startup, but repeatedly after stopping and restarting the server.
> It also occurs when the 'Server Details' are browsed in the Servers view, i.e., selecting any folder will cause another of the errors to display.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17591.
---------------------------------
Closing.
> org.jboss.tools.common.el.core.test fails on Max OS X Mavericks
> ---------------------------------------------------------------
>
> Key: JBIDE-17591
> URL: https://issues.jboss.org/browse/JBIDE-17591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks
> Reporter: Denis Golovin
> Assignee: Alexey Kazakov
> Fix For: 4.4.2.Final
>
> Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt
>
>
> {code}junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:55)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.Assert.assertNotNull(Assert.java:248)
> at junit.framework.TestCase.assertNotNull(TestCase.java:417)
> at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[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:
----------------------------------
I'm using the JBossTools TP and it runs fine even in Debug mode.
> 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: Alexey Kazakov
> 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
[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 the new Integration stack which integrates Openshift, ti is available here (not sure you have access) https://10.8.63.16/job/Fuse-Tooling-Target-Platform-Builder/lastSuccessfu...
I asked for this new TP on https://issues.jboss.org/browse/JBTIS-1008
I was launching it in Debug mode
> 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: Alexey Kazakov
> 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
[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:
----------------------------------
Just tried with my Win10 env and it works OK. Which TP are you using in Eclipse and do you start JBDS from Eclipse in Run or Debug mode ?
> 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: Alexey Kazakov
> 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
[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:
----------------------------------
Issue Type: Bug (was: Feature Request)
> 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: Alexey Kazakov
> 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
[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBDS-4227:
-------------------------------------
Summary: 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: Feature Request
Components: cdk, openshift
Affects Versions: 10.2.0.GA
Reporter: Aurélien Pupier
Assignee: Alexey Kazakov
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
[JBoss JIRA] (JBIDE-23587) Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23587?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-23587.
---------------------------------
Closing. PR merged.
> Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test
> -----------------------------------------------------------------------
>
> Key: JBIDE-23587
> URL: https://issues.jboss.org/browse/JBIDE-23587
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Labels: integration, integration_tests, maven
> Fix For: 4.4.3.AM1
>
>
> Maven command from CLI:
> {code}
> mvn clean verify -Dtest.module=org.jboss.tools.maven.ui.bot.test -DskipTests=false
> {code}
> Launching in Eclipse needs the following parameters:
> {code}
> -Dusage_reporting_enabled=false -Drd.config=resources/servers -Djbosstools.test.seam.2.1.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.1.2 -Djbosstools.test.seam.2.3.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.3.0.CR1 -Djbosstools.test.seam.2.2.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.2.0.GA -Djbosstools.test.wildfly8.home=/home/dbocharo/wildfly-8.2.1.Final -Dmaven.settings.path=/home/dbocharo/dev/openshift/jbosstools-integration-tests/tests/org.jboss.tools.maven.ui.bot.test/target/classes/usersettings/settings.xml
> {code}
> Corresponding directories must contain Seam and Wildfly
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months