[JBoss JIRA] (JBIDE-22759) Error logged from Debug UI when EAP is started
by Daniel Dekany (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22759?page=com.atlassian.jira.plugi... ]
Daniel Dekany commented on JBIDE-22759:
---------------------------------------
This problem should be gone with the recent JBIDE-22701 update.
> Error logged from Debug UI when EAP is started
> ----------------------------------------------
>
> Key: JBIDE-22759
> URL: https://issues.jboss.org/browse/JBIDE-22759
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker, server
> Affects Versions: 4.4.1.AM2
> Reporter: Martin Malina
> Assignee: Alexey Kazakov
> Fix For: 4.4.1.AM3
>
>
> When I start EAP 7 in devstudio 10.0.1.AM2, I get two errors in the error log:
> {code}
> Error logged from Debug UI:
> org.eclipse.core.runtime.CoreException: Plug-in org.jboss.ide.eclipse.freemarker was unable to load class org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker.
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.getLineTrackers(ProcessConsoleManager.java:281)
> at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.connect(ConsoleLineNotifier.java:54)
> at org.eclipse.ui.internal.console.ConsolePatternMatcher.addPatternMatchListener(ConsolePatternMatcher.java:232)
> at org.eclipse.ui.console.TextConsole.addPatternMatchListener(TextConsole.java:409)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsole.<init>(ProcessConsole.java:228)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.launchChanged(ProcessConsoleManager.java:149)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:453)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
> at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
> at org.eclipse.debug.core.Launch.fireChanged(Launch.java:393)
> at org.eclipse.debug.core.Launch.addProcess(Launch.java:355)
> at org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:126)
> at org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:787)
> at org.eclipse.jdt.launching.AbstractVMRunner.newProcess(AbstractVMRunner.java:170)
> at org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:424)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractJavaServerLaunchDelegate.fireVMRunner(AbstractJavaServerLaunchDelegate.java:91)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.actualLaunch(AbstractStartJavaServerLaunchDelegate.java:95)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.launch(AbstractStartJavaServerLaunchDelegate.java:89)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.launch(LocalJBossLaunchController.java:94)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker cannot be found by org.jboss.ide.eclipse.freemarker_1.5.101.v20160714-1706
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> ... 31 more
> {code}
> {code}
> Plug-in org.jboss.ide.eclipse.freemarker was unable to load class org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker.
> java.lang.ClassNotFoundException: org.jboss.ide.eclipse.freemarker.linetracker.ConsoleLineTracker cannot be found by org.jboss.ide.eclipse.freemarker_1.5.101.v20160714-1706
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.getLineTrackers(ProcessConsoleManager.java:281)
> at org.eclipse.debug.internal.ui.views.console.ConsoleLineNotifier.connect(ConsoleLineNotifier.java:54)
> at org.eclipse.ui.internal.console.ConsolePatternMatcher.addPatternMatchListener(ConsolePatternMatcher.java:232)
> at org.eclipse.ui.console.TextConsole.addPatternMatchListener(TextConsole.java:409)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsole.<init>(ProcessConsole.java:228)
> at org.eclipse.debug.internal.ui.views.console.ProcessConsoleManager.launchChanged(ProcessConsoleManager.java:149)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:453)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
> at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
> at org.eclipse.debug.core.Launch.fireChanged(Launch.java:393)
> at org.eclipse.debug.core.Launch.addProcess(Launch.java:355)
> at org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:126)
> at org.eclipse.debug.core.DebugPlugin.newProcess(DebugPlugin.java:787)
> at org.eclipse.jdt.launching.AbstractVMRunner.newProcess(AbstractVMRunner.java:170)
> at org.eclipse.jdt.internal.launching.StandardVMRunner.run(StandardVMRunner.java:424)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractJavaServerLaunchDelegate.fireVMRunner(AbstractJavaServerLaunchDelegate.java:91)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.actualLaunch(AbstractStartJavaServerLaunchDelegate.java:95)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.AbstractStartJavaServerLaunchDelegate.launch(AbstractStartJavaServerLaunchDelegate.java:89)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalJBossLaunchController.launch(LocalJBossLaunchController.java:94)
> 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:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> Note: This doesn't seem to have any effect on the functionality of the EAP server adapter.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3951:
--------------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3951:
-----------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3951:
-----------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3951:
-----------------------------
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3951:
--------------------------------
Status: New (was: New)
Target Release: 10.1.0.GA
> Installer needs to add the VirtualBox install directory to the PATH
> -------------------------------------------------------------------
>
> Key: JBDS-3951
> URL: https://issues.jboss.org/browse/JBDS-3951
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 10.1.0.AM3
>
>
> The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found.
> As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-3624) Error while parsing response from auth server
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3624?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3624.
---------------------------------
Resolution: Done
> Error while parsing response from auth server
> ---------------------------------------------
>
> Key: JBDS-3624
> URL: https://issues.jboss.org/browse/JBDS-3624
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3
>
> Attachments: auth-error.png
>
>
> # npm start
> # type "asdf" to username field
> # type "asdf" to password field
> # open dev tools (Ctrl + Shift + i on Linux)
> # click "Log in" button
> result:
> This stack trace appears in console log:
> {code}
> SyntaxError: Unexpected token I
> at Object.parse (native)
> at fromJson (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:1274:14)
> at defaultHttpResponseTransform (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9463:16)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9554:12
> at forEach (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:343:20)
> at transformData (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:9553:3)
> at transformResponse (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:10322:21)
> at processQueue (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14795:28)
> at file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:14811:27
> at Scope.$eval (file:///home/ppitonak/workspace/developer-platform-install/browser/jspm_packages/github/angular/bower-angular@1.4.8/angular.js:16055:28)
> {code}
> JSON.parse failes because the server returned "Invalid user credentials for user asdf"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months