| Summary: | Basic Client & Agent compatibility on Windows EM64T | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Karla Callaghan <karla.callaghan> |
| Component: | TPTP | Assignee: | Randy D. Smith <randy.d.smith> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Server 2003 | ||
| Whiteboard: | closed460 | ||
|
Description
Karla Callaghan
Everything looks ready to go into place with the i3 RC build once the machine is on the network for real. Basic functionality is in place in that SampleClient works as does PerfmonAgent. However, profiling is DOA. It will start the profiled CarModel, but then terminate. If I "java -XrunpiAgent profilingExample/CarModel" externally, it runs fine until I "Start Monitoring" from the workbench. Setting priority to P1 since we do want to complete EM64T on Windows. I was holding off declaring this done as I saw profiling as DOA. I understand there are successful test passes, which implies we have a JVM issue. I'll bugzilla the specific JVM I'm seeing problems with, and declare this (basic compatibility for EM64T) as done. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |