This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 174775 - [monitor] Invalid Thread Access when connecting new dstore
Summary: [monitor] Invalid Thread Access when connecting new dstore
Status: RESOLVED DUPLICATE of bug 176601
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 2.0   Edit
Assignee: David McKnight CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-20 09:33 EST by Martin Oberhuber CLA
Modified: 2008-08-13 13:19 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-02-20 09:33:44 EST
Have an existing dstore-linux connection, with the Monitor showing "My Processes".
Now select an existing dstore-windows connection, and with the Host selected choose "connect".
Observe the following exception:

org.eclipse.swt.SWTException: Invalid thread access
	at org.eclipse.swt.SWT.error(SWT.java:3478)
	at org.eclipse.swt.SWT.error(SWT.java:3401)
	at org.eclipse.swt.SWT.error(SWT.java:3372)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:432)
	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:326)
	at org.eclipse.swt.widgets.Widget.getData(Widget.java:485)
	at org.eclipse.rse.internal.ui.view.monitor.MonitorViewWorkbook.getCurrentTabItem(MonitorViewWorkbook.java:156)
	at org.eclipse.rse.internal.ui.view.monitor.MonitorViewWorkbook.getViewer(MonitorViewWorkbook.java:180)
	at org.eclipse.rse.internal.ui.view.monitor.SystemMonitorViewPart.getViewer(SystemMonitorViewPart.java:639)
	at org.eclipse.rse.internal.ui.view.monitor.SystemMonitorViewPart.systemResourceChanged(SystemMonitorViewPart.java:805)
	at org.eclipse.rse.internal.model.SystemResourceChangeManager.notify(SystemResourceChangeManager.java:74)
	at org.eclipse.rse.model.SystemRegistry.fireEvent(SystemRegistry.java:2955)
	at org.eclipse.rse.model.SystemRegistry.connectedStatusChange(SystemRegistry.java:2860)
	at org.eclipse.rse.model.SystemRegistry.connectedStatusChange(SystemRegistry.java:2844)
	at org.eclipse.rse.core.subsystems.SubSystem$ConnectJob.performOperation(SubSystem.java:1590)
	at org.eclipse.rse.core.subsystems.SubSystem$SubSystemOperationJob.run(SubSystem.java:1274)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)


-----------Enter bugs above this line-----------
TM 2.0M5 Testing
installation : eclipse-SDK-3.3M5 (I20070209-1006), cdt-4.0M5, emf-2.3M5
RSE install  : RSE-SDK I20070219-1645 + discovery + efs
java.runtime : Sun 1.4.2_13
os.name:     : Windows XP 5.1, Service Pack 1
------------------------------------------------
systemtype   : Unix-ssh / Linux-dstore-processes
targetos     : Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
targetuname  : Linux parser.takefive.co.at 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux
targetvm     : Sun Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
------------------------------------------------
Comment 1 David McKnight CLA 2007-02-20 09:53:04 EST
I tried but failed to reproduce this.  Is this something you can reproduce consistently?
Comment 2 Martin Oberhuber CLA 2007-02-20 09:55:46 EST
During the milestone test, I'm just recording bugs but not trying to reproduce.
I know that those SWT exceptions are often hard to reproduce, and I don't intend to try doing so until there is more time.
Comment 3 David McKnight CLA 2007-02-22 09:17:29 EST
I think the title of this is misleading because there doesn't appear to be anything dstore-specific about the exception.
Comment 4 David McKnight CLA 2007-05-30 09:50:04 EDT
Bug 176601 will have fixed this.

*** This bug has been marked as a duplicate of bug 176601 ***
Comment 5 Martin Oberhuber CLA 2008-08-13 13:19:13 EDT
[target cleanup] 2.0 RC1 was the original target milestone for this bug