[jbosstools-issues] [JBoss JIRA] (JBIDE-20738) JMX Navigator Refresh Command is running in main UI Thread

Alexey Kazakov (JIRA) issues at jboss.org
Fri Sep 18 15:06:00 EDT 2015


     [ https://issues.jboss.org/browse/JBIDE-20738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov updated JBIDE-20738:
-----------------------------------
    Fix Version/s: 4.3.1.Final
                   4.4.0.Alpha1


> JMX Navigator Refresh Command is running in main UI Thread
> ----------------------------------------------------------
>
>                 Key: JBIDE-20738
>                 URL: https://issues.jboss.org/browse/JBIDE-20738
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jmx
>    Affects Versions: 4.3.0.CR1
>            Reporter: Denis Golovin
>             Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
>
> Refresh in JMX Navigator freezes UI because executed in main UI thread:
> {code}Thread [main] (Suspended (breakpoint at line 435 in org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm))	
> 	owns: org.jboss.tools.jmx.local.internal.JvmConnectionWrapper  (id=162)	
> 	org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(javax.management.remote.JMXServiceURL) line: 435	
> 	org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(java.lang.String, int) line: 465	
> 	org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize() line: 445	
> 	org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int, boolean) line: 233	
> 	org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(int) line: 213	
> 	org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect() line: 121	
> 	org.jboss.tools.jmx.ui.internal.actions.RefreshAction.refreshObjectNode(java.lang.Object) line: 107	
> 	org.jboss.tools.jmx.ui.internal.actions.RefreshAction.run() line: 153	
> 	org.jboss.tools.jmx.ui.internal.actions.RefreshAction(org.eclipse.jface.action.Action).runWithEvent(org.eclipse.swt.widgets.Event) line: 473	
> 	org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(org.eclipse.swt.widgets.Event, boolean) line: 595	
> 	org.eclipse.jface.action.ActionContributionItem.access$2(org.eclipse.jface.action.ActionContributionItem, org.eclipse.swt.widgets.Event, boolean) line: 511	
> 	org.eclipse.jface.action.ActionContributionItem$5.handleEvent(org.eclipse.swt.widgets.Event) line: 420	
> 	org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84	
> 	org.eclipse.swt.widgets.Display.sendEvent(org.eclipse.swt.widgets.EventTable, org.eclipse.swt.widgets.Event) line: 4481	
> 	org.eclipse.swt.widgets.MenuItem(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1327	
> 	org.eclipse.swt.widgets.Display.runDeferredEvents() line: 3819	
> 	org.eclipse.swt.widgets.Display.readAndDispatch() line: 3430	
> 	org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() line: 1127	
> 	org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337	
> 	org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(org.eclipse.e4.ui.model.application.MApplicationElement, org.eclipse.e4.core.contexts.IEclipseContext) line: 1018	
> 	org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(org.eclipse.e4.ui.model.application.MApplicationElement) line: 156	
> 	org.eclipse.ui.internal.Workbench$5.run() line: 654	
> 	org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 337	
> 	org.eclipse.ui.internal.Workbench.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 598	
> 	org.eclipse.ui.PlatformUI.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 150	
> 	org.eclipse.ui.internal.ide.application.IDEApplication.start(org.eclipse.equinox.app.IApplicationContext) line: 139	
> 	org.eclipse.equinox.internal.app.EclipseAppHandle.run(java.lang.Object) line: 196	
> 	org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(java.lang.Object) line: 134	
> 	org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(java.lang.Object) line: 104	
> 	org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.Object) line: 380	
> 	org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.String[], java.lang.Runnable) line: 235	
> 	sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) line: not available [native method]	
> 	sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 62	
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 43	
> 	java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line: 497	
> 	org.eclipse.equinox.launcher.Main.invokeFramework(java.lang.String[], java.net.URL[]) line: 669	
> 	org.eclipse.equinox.launcher.Main.basicRun(java.lang.String[]) line: 608	
> 	org.eclipse.equinox.launcher.Main.run(java.lang.String[]) line: 1515	
> 	org.eclipse.equinox.launcher.Main.main(java.lang.String[]) line: 1488	
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list