Bugzilla – Full Text Bug Listing
| Summary: | Unable to do remote execution a Vista machine | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Ken Sandler <ksandler> | ||||
| Component: | TPTP | Assignee: | Joe Toomey <jptoomey> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | jptoomey, ksandler, paulslau | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ken Sandler
I don't see this error. (i.e. we have tested remote execution of tests on Vista and it works fine.) Did you configure the agent controller to accept connections from all hosts? Is the Windows firewall configured to allow connections on the necessary ports? Neither of these are Vista specific, but either could result in a conection refused message. There are some known problems with Vista, and we don't support it yet, but are working on it now. But remote test execution is not one of the known problems. I just ran a remote JUnit test on Vista to validate, and it ran fine. Please confirm when you have figured out your issue so I can close this. Thanks. If this problem can be reproduced, please increase the severity accordingly (e.g. critical or blocking). From what I can tell, this is a dupe of 166213, which addresses several agent controller security issues in Vista. The Vista boxes that we have been using to test with have apparently had security options turned down on them. 166213 should either correct the AC to work properly on Vista w/o security changes, or document the necessary workarounds. *** This bug has been marked as a duplicate of bug 166213 *** Duped to wrong dug number *** This bug has been marked as a duplicate of bug 167842 *** It's not quite a duplicate, since the fix for bug 166213 wasn't checked in to all branches. I'm re-opening, but check in the fix to the 4.2.2 branch, so I will close it shortly. Fix from biug 166213 checked in to the 4.2.2 branch Created attachment 57155 [details]
Test classes to reproduce the problem
To reproduce the problem follow the steps *exactly* as outlined below on a hyperthreading, multi-core or multi-processor machine:
Make sure that a standalone installation of the Agent Controller is configured
and started.
1) Extract the zip file attached to a directory. It should contain three
files: HelloWorld.class, Classpath.class, and ForClasspath.class.
2) Open the profile launch configuration and create a launch configuration of
type "External Java Application".
3) Switch to the Main tab and browse to the "Classpath.class" file
4) Switch to the Monitor tab and de-select everything but "Execution Time
Analysis"
5) Click apply
6) Repeat step 2-5 but select "HelloWorld.class" in step 3)
7) Keep alternating between launching Classpath and Helloworld.
The launch progress will eventually get stuck at 78% and it will not respond
until it is restarted. This is blocking me from running the automated launch
test suites. I can consistenly reproduce this problem on my machine.
Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks. Verified in TPTP-4.4.0-200706140100A |