[JBoss JIRA] (JBIDE-24187) Provide a minimal updatesite for JBoss servers/runtime in Eclipse
by Beirti O'Nunain (JIRA)
Beirti O'Nunain created JBIDE-24187:
---------------------------------------
Summary: Provide a minimal updatesite for JBoss servers/runtime in Eclipse
Key: JBIDE-24187
URL: https://issues.jboss.org/browse/JBIDE-24187
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Beirti O'Nunain
The JBoss Developer Studio provides too many tools in one big package. I only require the server runtime support so that I can start and stop services. The additional bundled packages slow down a large workspace build massively as they add many unnecessary project facets and builders to projects.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24186) Eclipse workspace deadlocking during refresh/rebuild
by Beirti O'Nunain (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24186?page=com.atlassian.jira.plugi... ]
Beirti O'Nunain updated JBIDE-24186:
------------------------------------
Description:
- Windows 7
- Eclipse Neon.2 (4.6.2)
- Developer Studio 10.3.0
After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane:
+ "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'"
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
....
The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace.
Profiling with yourkit detects a deadlock in the following thread:
Worker-33 <--- Frozen for at least 8m 27s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
I started profiling Yourkit when the build hung. It shows the following as the live call stack:
Call Tree Time (ms) Level
<All threads> 530944 1
org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2
org.eclipse.equinox.launcher.Main.run(String[]) 436 2
org.eclipse.core.internal.jobs.Worker.run() 421 2
I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed
Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs:
Frozen threads found (potential deadlock)
It seems that the following threads have not changed their stack for more than 10 seconds.
These threads are possibly (but not necessarily!) in a deadlock or hung.
main <--- Frozen for at least 2m 21s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69
org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206
org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273
org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297
org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259
org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108
org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92
org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126
org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123
org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231
org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228
org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114
org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343
org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358
org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450
org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158
org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50
org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173
org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155
org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191
org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229
org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258
org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242
org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236
org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405
org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84
org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418
org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079
org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236
org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150
org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610
org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148
org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388
org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243
sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native)
sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62
sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43
java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498
org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673
org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610
org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519
Worker-33 <--- Frozen for at least 14m 43s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
was:
After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane:
+ "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'"
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
....
The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace.
Profiling with yourkit detects a deadlock in the following thread:
Worker-33 <--- Frozen for at least 8m 27s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
I started profiling Yourkit when the build hung. It shows the following as the live call stack:
Call Tree Time (ms) Level
<All threads> 530944 1
org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2
org.eclipse.equinox.launcher.Main.run(String[]) 436 2
org.eclipse.core.internal.jobs.Worker.run() 421 2
I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed
Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs:
Frozen threads found (potential deadlock)
It seems that the following threads have not changed their stack for more than 10 seconds.
These threads are possibly (but not necessarily!) in a deadlock or hung.
main <--- Frozen for at least 2m 21s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69
org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206
org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273
org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297
org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259
org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108
org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92
org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126
org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123
org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231
org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228
org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114
org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343
org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358
org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450
org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158
org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50
org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173
org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155
org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191
org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229
org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258
org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242
org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236
org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405
org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84
org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418
org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079
org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236
org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150
org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610
org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148
org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388
org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243
sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native)
sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62
sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43
java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498
org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673
org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610
org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519
Worker-33 <--- Frozen for at least 14m 43s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
> Eclipse workspace deadlocking during refresh/rebuild
> ----------------------------------------------------
>
> Key: JBIDE-24186
> URL: https://issues.jboss.org/browse/JBIDE-24186
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Beirti O'Nunain
>
> - Windows 7
> - Eclipse Neon.2 (4.6.2)
> - Developer Studio 10.3.0
> After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane:
> + "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'"
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> ....
> The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace.
> Profiling with yourkit detects a deadlock in the following thread:
> Worker-33 <--- Frozen for at least 8m 27s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
> I started profiling Yourkit when the build hung. It shows the following as the live call stack:
> Call Tree Time (ms) Level
> <All threads> 530944 1
> org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2
> org.eclipse.equinox.launcher.Main.run(String[]) 436 2
> org.eclipse.core.internal.jobs.Worker.run() 421 2
> I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed
> Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs:
> Frozen threads found (potential deadlock)
> It seems that the following threads have not changed their stack for more than 10 seconds.
> These threads are possibly (but not necessarily!) in a deadlock or hung.
> main <--- Frozen for at least 2m 21s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69
> org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206
> org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273
> org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297
> org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259
> org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108
> org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92
> org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231
> org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228
> org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114
> org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343
> org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358
> org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31
> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450
> org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50
> org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173
> org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155
> org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191
> org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229
> org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258
> org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242
> org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236
> org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405
> org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84
> org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418
> org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079
> org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236
> org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150
> org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243
> sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native)
> sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43
> java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498
> org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673
> org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610
> org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519
> Worker-33 <--- Frozen for at least 14m 43s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4348) CDK installation fails when windows user has non-ascii character in name
by Jan Richter (JIRA)
Jan Richter created JBDS-4348:
---------------------------------
Summary: CDK installation fails when windows user has non-ascii character in name
Key: JBDS-4348
URL: https://issues.jboss.org/browse/JBDS-4348
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.4.0.AM2
Reporter: Jan Richter
Running the installer as windows user Pakoň, CDK fails with the following error:
{noformat}
Mon, 03 Apr 2017 10:22:22 GMT-INFO: cdk - Copy C:\WINDOWS\7zS746E.tmp\minishift.exe to c:\DevelopmentSuite\cdk\bin\minishift.exe
Mon, 03 Apr 2017 10:22:23 GMT-INFO: cdk - Copy C:\WINDOWS\7zS746E.tmp\minishift.exe to c:\DevelopmentSuite\cdk\bin\minishift.exe SUCCESS
Mon, 03 Apr 2017 10:22:23 GMT-INFO: cdk - Set PATH environment variable to 'c:\DevelopmentSuite\virtualbox\;c:\DevelopmentSuite\cygwin;C:\Python27\Scripts\;C:\Python27\;C:\apache-maven-3.3.3\bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;c:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Users\jbossqa\openshift;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\Program Files\OpenVPN\bin;C:\Users\Pakon\AppData\Local\Microsoft\WindowsApps'
Mon, 03 Apr 2017 10:22:23 GMT-INFO: cdk - Execute command c:\DevelopmentSuite\cdk\bin\minishift.exe setup-cdk --force --default-vm-driver=virtualbox
Mon, 03 Apr 2017 10:22:28 GMT-INFO: cdk - Setting up CDK 3 on host using 'C:\Users\Pakoň\.minishift' as Minishift's home directory
Copying minishift-rhel7.iso to 'C:\Users\Pakoň\.minishift/cache/iso/minishift-rhel7.iso'
Copying oc.exe to 'C:\Users\Pakoň\.minishift/cache/oc/v3.4.1.2/oc.exe'
Creating configuration file 'C:\Users\Pakoň\.minishift/config/config.json'
Creating marker file 'C:\Users\Pakoň\.minishift/cdk'
CDK 3 setup complete.
Mon, 03 Apr 2017 10:22:28 GMT-INFO: cdk - Execute c:\DevelopmentSuite\cdk\bin\minishift.exe setup-cdk --force --default-vm-driver=virtualbox SUCCESS
Mon, 03 Apr 2017 10:22:28 GMT-ERROR: cdk failed to install: TypeError: Cannot read property 'replace' of undefined
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24186) Eclipse workspace deadlocking during refresh/rebuild
by Beirti O'Nunain (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24186?page=com.atlassian.jira.plugi... ]
Beirti O'Nunain commented on JBIDE-24186:
-----------------------------------------
[~rob.stryker] Think this may be related to https://issues.jboss.org/browse/JBIDE-23757 ?
> Eclipse workspace deadlocking during refresh/rebuild
> ----------------------------------------------------
>
> Key: JBIDE-24186
> URL: https://issues.jboss.org/browse/JBIDE-24186
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Beirti O'Nunain
>
> After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane:
> + "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'"
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> ....
> The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace.
> Profiling with yourkit detects a deadlock in the following thread:
> Worker-33 <--- Frozen for at least 8m 27s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
> I started profiling Yourkit when the build hung. It shows the following as the live call stack:
> Call Tree Time (ms) Level
> <All threads> 530944 1
> org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2
> org.eclipse.equinox.launcher.Main.run(String[]) 436 2
> org.eclipse.core.internal.jobs.Worker.run() 421 2
> I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed
> Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs:
> Frozen threads found (potential deadlock)
> It seems that the following threads have not changed their stack for more than 10 seconds.
> These threads are possibly (but not necessarily!) in a deadlock or hung.
> main <--- Frozen for at least 2m 21s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69
> org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206
> org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273
> org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297
> org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259
> org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108
> org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92
> org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231
> org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228
> org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114
> org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343
> org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358
> org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31
> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450
> org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50
> org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173
> org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155
> org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191
> org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229
> org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258
> org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242
> org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236
> org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405
> org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84
> org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418
> org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079
> org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236
> org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150
> org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243
> sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native)
> sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43
> java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498
> org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673
> org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610
> org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519
> Worker-33 <--- Frozen for at least 14m 43s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24186) Eclipse workspace deadlocking during refresh/rebuild
by Beirti O'Nunain (JIRA)
Beirti O'Nunain created JBIDE-24186:
---------------------------------------
Summary: Eclipse workspace deadlocking during refresh/rebuild
Key: JBIDE-24186
URL: https://issues.jboss.org/browse/JBIDE-24186
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Beirti O'Nunain
After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane:
+ "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'"
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
+ Updating Maven Project (Waiting)
....
The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace.
Profiling with yourkit detects a deadlock in the following thread:
Worker-33 <--- Frozen for at least 8m 27s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
I started profiling Yourkit when the build hung. It shows the following as the live call stack:
Call Tree Time (ms) Level
<All threads> 530944 1
org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2
org.eclipse.equinox.launcher.Main.run(String[]) 436 2
org.eclipse.core.internal.jobs.Worker.run() 421 2
I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed
Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs:
Frozen threads found (potential deadlock)
It seems that the following threads have not changed their stack for more than 10 seconds.
These threads are possibly (but not necessarily!) in a deadlock or hung.
main <--- Frozen for at least 2m 21s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112
org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69
org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206
org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273
org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297
org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259
org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108
org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92
org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126
org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123
org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231
org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56
org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228
org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114
org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343
org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358
org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31
org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450
org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158
org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50
org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173
org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155
org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191
org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229
org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258
org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242
org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236
org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405
org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84
org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418
org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079
org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236
org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150
org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610
org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148
org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388
org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243
sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native)
sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62
sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43
java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498
org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673
org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610
org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519
Worker-33 <--- Frozen for at least 14m 43s
org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24185:
-------------------------------------
Description:
* eap
** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
{code}
"com.redhat.dev-mode": "DEBUG:true",
{code}
** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
{code}
"com.redhat.dev-mode.port": "DEBUG_PORT:8787"
{code}
* nodejs
** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
{code}
"com.redhat.dev-mode": "DEV_MODE:false",
"com.redhat.dev-mode.port": "DEBUG_PORT:5858",
{code}
was:
* eap
** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
{code}
"com.redhat.dev-mode": "DEBUG:true",
{code}
** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
{code}
"com.redhat.dev-mode.port": "DEBUG_PORT:8787"
{code}
* to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
{code}
"com.redhat.dev-mode": "DEV_MODE:false",
"com.redhat.dev-mode.port": "DEBUG_PORT:5858",
{code}
> Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24185
> URL: https://issues.jboss.org/browse/JBIDE-24185
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.4.AM3
>
>
> * eap
> ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
> {code}
> "com.redhat.dev-mode": "DEBUG:true",
> {code}
> ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
> {code}
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787"
> {code}
> * nodejs
> ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
> {code}
> "com.redhat.dev-mode": "DEV_MODE:false",
> "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24185:
-------------------------------------
Fix Version/s: 4.4.4.AM3
> Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24185
> URL: https://issues.jboss.org/browse/JBIDE-24185
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.4.AM3
>
>
> * eap
> ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
> {code}
> "com.redhat.dev-mode": "DEBUG:true",
> {code}
> ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
> {code}
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787"
> {code}
> * to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
> {code}
> "com.redhat.dev-mode": "DEV_MODE:false",
> "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24185:
-------------------------------------
Summary: Server adapter: approach to set nodejs/eap apps to debugging is inconsistent (was: Server adapter: DEV_MODE and DEBUG are inconsistent btw. nodejs and eap)
> Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24185
> URL: https://issues.jboss.org/browse/JBIDE-24185
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.4.AM3
>
>
> * eap
> ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
> {code}
> "com.redhat.dev-mode": "DEBUG:true",
> {code}
> ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
> {code}
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787"
> {code}
> ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
> {code}
> "com.redhat.dev-mode": "DEV_MODE:false",
> "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24185:
-------------------------------------
Description:
* eap
** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
{code}
"com.redhat.dev-mode": "DEBUG:true",
{code}
** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
{code}
"com.redhat.dev-mode.port": "DEBUG_PORT:8787"
{code}
* to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
{code}
"com.redhat.dev-mode": "DEV_MODE:false",
"com.redhat.dev-mode.port": "DEBUG_PORT:5858",
{code}
was:
* eap
** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
{code}
"com.redhat.dev-mode": "DEBUG:true",
{code}
** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
{code}
"com.redhat.dev-mode.port": "DEBUG_PORT:8787"
{code}
** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
{code}
"com.redhat.dev-mode": "DEV_MODE:false",
"com.redhat.dev-mode.port": "DEBUG_PORT:5858",
{code}
> Server adapter: approach to set nodejs/eap apps to debugging is inconsistent
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24185
> URL: https://issues.jboss.org/browse/JBIDE-24185
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.4.4.AM3
>
>
> * eap
> ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*.
> {code}
> "com.redhat.dev-mode": "DEBUG:true",
> {code}
> ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label
> {code}
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787"
> {code}
> * to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858*
> {code}
> "com.redhat.dev-mode": "DEV_MODE:false",
> "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-3827) JBDS installation fails when (windows) user has non-ascii chars in the name
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3827:
------------------------------
Fix Version/s: 11.0.0.AM1
> JBDS installation fails when (windows) user has non-ascii chars in the name
> ---------------------------------------------------------------------------
>
> Key: JBDS-3827
> URL: https://issues.jboss.org/browse/JBDS-3827
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.1.0.AM3, 11.0.0.AM1
>
>
> I have created a user named Pakoň and tried to install everything into the default folder. JBDS failed with:
> {noformat}Fri, 15 Apr 2016 12:38:40 GMT-ERROR: jbds - Error: Command failed: c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true -jar C:\WINDOWS\7zS9F06.tmp\jbds.jar C:\Users\Pakoň\AppData\Local\Temp\jbds-autoinstall.xml
> - ERROR -
> java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified)
> java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.<init>(FileInputStream.java:138)
> at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(AutomatedInstaller.java:564)
> at com.izforge.izpack.installer.AutomatedInstaller.<init>(AutomatedInstaller.java:86)
> at com.izforge.izpack.installer.Installer.main(Unknown Source){noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years