Bugzilla – Full Text Bug Listing
| Summary: | [Recoverability] Cannot launch testcases with latest build (code from CVS) after RAC has been restarted | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Marius Slavescu <slavescu> |
| Component: | TPTP | Assignee: | DuWayne Morris <dmorris> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P1 | CC: | apnan, paulslau |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Marius Slavescu
Worked after I restarted the machine. Anyway is strange that I was able to launch the profiler and it worked fine, only the launch testcase operation was afected. Closing bug. The problem still exists, after several runs (restarted several times the AC and Workbench) I hit the problem again. The profiler launch configuration works fine. I also see this error when I try to import a remote log (using 127.0.0.1) with a filter (this scenario uses the file transfer): java.io.FileNotFoundException: D:\test\tptp-4.0-i4\bundleentry:\72\config\Apache\access\v1.3.26\GLA1119301502250.adapter (The handle is invalid. ) java.io.FileNotFoundException: D:\test\tptp-4.0-i4\bundleentry:\72\config\Apache\access\v1.3.26\GLA1119301502250.adapter (The handle is invalid. ) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:201) at java.io.FileOutputStream.<init>(FileOutputStream.java:153) at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createFileOutputStream(URIConverterImpl.java:331) at org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createOutputStream(URIConverterImpl.java:289) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:810) at org.eclipse.tptp.monitoring.logui.internal.util.GLAFilterHelper.addFilterToAdapter(GLAFilterHelper.java:263) at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.importFromRemoteHost(ImportLogWizard.java:1857) at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.importLog(ImportLogWizard.java:1771) at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.run(ImportLogWizard.java:261) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) at org.eclipse.tptp.monitoring.logui.internal.wizards.ImportLogWizard.performFinish(ImportLogWizard.java:187) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:676) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:349) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:556) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:844) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3070) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2703) at org.eclipse.jface.window.Window.runEventLoop(Window.java:809) at org.eclipse.jface.window.Window.open(Window.java:787) at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:159) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:167) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:844) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3070) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2703) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) at org.eclipse.core.launcher.Main.basicRun(Main.java:278) at org.eclipse.core.launcher.Main.run(Main.java:973) at org.eclipse.core.launcher.Main.main(Main.java:948) Looks like theer are problems with the file transfer service on windows in 4.0. We should look at the most recent changes and see if we can isolate the cause of teh regression. Scott -- I can help investigate this tomorrow. Initially I though that this was happening only on hyper-threading machines, but I found and easy way to reproduce it on single CPU machines: 1. Start AgentController (AC) from command line (not as a service) 2. Start a manual test (a simple one with 4 tests and 4 invocations) 3. After the manual runner shows up, kill the AC process 4. Exit the manual runner 5. Redo 1. 6. Redo 2. and you'll see the error. If you run "netstat -a" after 5. you won't see any application listening on port 10005, immediately after 1. you should see RAServer listening on 10005. Also don't wait much between 3, 4 and 5, you can also try to do 5. before 4. I reduced the severity because seems that it is triggered only if the user kills the RAC before all connections were closed. If you want to move it to 4.1 please create a readme entry that describes this behavior and the workaround - restart the workbench and the AgentController. << updated summary, retargeted to 4.1 >> Similar behavior existed in 3.0.2 (and presumably 3.3) -- if you restart a RAC, you need to also restart the workbench to insure reliable subsequent test execution, at least that is the experience documented by a consuming product. Agree that this doesn't meet blocker criteria due to work-around being available. (Left severity as major at Marius' request to keep it above "normal" in the 4.1 activity prioritization.) Updated summary (intended to in last submit, but it got lost due to commit conflict). [ sizing = 3 day ] Has the priority for this defect been recently reviewed given its severity? If not, please take a few minutes and reevaluate the priority. I inherited this defect (which is roughly 1.5 years old). Is there any sense if this is a dupe of https://bugs.eclipse.org/bugs/show_bug.cgi?id=152468 (i.e. whether security is enabled or not, the AC startup is not atomic, and if you try to use the AC before it is done starting the file server, you will run into problems.) If so, I will dupe it. If not, do you agree with the current target milestone and priority (future P2)? Will be included in the 4.4 plan. Please target to a 4.4 iteration. Increasing the priority to P1 since including in the 4.4 plan. Increasing the priority to P1 since including in the 4.4 plan. Assigning target. Using the TPTP-4.4.0-200704231237 workbench and Agent Controller on Windows XP, this defect can only be reproduced with security enabled using the above scenario (https://bugs.eclipse.org/bugs/show_bug.cgi?id=100937#c6). As such, this defect is a duplicate of https://bugs.eclipse.org/bugs/show_bug.cgi?id=152468. *** This bug has been marked as a duplicate of bug 152468 *** Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks. Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct. |