Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332699 - NPE during remote rename after Bug fix 328060
Summary: NPE during remote rename after Bug fix 328060
Status: CLOSED WORKSFORME
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 3.0.3   Edit
Hardware: Other other
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: dsdp.tm.rse-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-15 21:40 EST by Onno Van den Troost CLA
Modified: 2010-12-17 10:28 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Onno Van den Troost CLA 2010-12-15 21:40:03 EST
We applied OpenRSE 11-05 build to resolve Bug 328060 (backport 329259 and 328154) "command queue in Miner should be synchronized".

Now we notice a NPE on the RDz client when doing a rename or delete of a remote member.

!ENTRY org.eclipse.rse.ui 4 0 2010-12-15 15:43:24.195
!MESSAGE RSEG1063U: SUB#1:java.lang.NullPointerException
!STACK 0
java.lang.Exception
	at org.eclipse.rse.ui.messages.SystemMessageDialog.logMessage(Unknown Source)
	at org.eclipse.rse.ui.messages.SystemMessageDialog.open(Unknown Source)
	at org.eclipse.rse.ui.messages.SystemMessageDialog.openInUIThread(Unknown Source)
	at org.eclipse.rse.ui.messages.SystemMessageDialog.displayErrorMessage(Unknown Source)
	at com.ibm.ftt.ui.common.project.navigator.MVSCommonActionProvider.doDelete(Unknown Source)
	at com.ibm.ftt.projects.view.ui.delete.actions.PBSystemCommonDeleteAction.getDialogValue(Unknown Source)
	at org.eclipse.rse.ui.actions.SystemBaseDialogAction.run(Unknown Source)
	at org.eclipse.jface.action.Action.runWithEvent(Unknown Source)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Unknown Source)
	at org.eclipse.jface.action.ActionContributionItem.access$2(Unknown Source)
	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(Unknown Source)
	at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
	at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
	at org.eclipse.ui.internal.Workbench.access$4(Unknown Source)
	at org.eclipse.ui.internal.Workbench$5.run(Unknown Source)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Unknown Source)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(Unknown Source)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)
	at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
	at org.eclipse.equinox.launcher.Main.run(Unknown Source)
	at org.eclipse.equinox.launcher.Main.main(Unknown Source)
Comment 1 David McKnight CLA 2010-12-16 09:07:31 EST
Onno, I think Masao indicated in the work item that the NPEs have nothing to do with the server.
Comment 2 Onno Van den Troost CLA 2010-12-17 10:28:37 EST
Further investigation by development shows that the root cause is a racing condition on the client, so not related to the RSE server code at all. We just happen to run into it now.

case closed.