Bugzilla – Full Text Bug Listing
| Summary: | [POG]profile external java app. with VM arguments causes JVMTI error | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Alan Haggarty <haggarty> |
| Component: | TPTP | Assignee: | Stanislav Polevic <stanislav.v.polevic> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P1 | CC: | analexee, jkubasta, kendricw |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | closed460 | ||
|
Description
Alan Haggarty
This is a duplicate of 179816 *** This bug has been marked as a duplicate of bug 179816 *** The duplicate defect is 178916 *** This bug has been marked as a duplicate of bug 178916 *** This problem can be reproduce in Vista using the 200706140100A build exactly as described below. 178916 is marked fixed and last committed on May 29. Whats the command line you are using No command line, but it seems in the later builds it is fixed if I use the VM arg: -Dprop1="prop one" to the launch profile. But if I add: -Dprop1='prop one' it fails with similar behavior as before. single quotes is something covered in the original ArgumentsTest test case.The test case uses the args: -Dprop1="prop one" -Dprop2="prop two" -Dprop3='prop three' Was able to reproduce a similar problem using the TPTP-4.4.0-200706140100C build on LinuxIA32 with JVMPI. No error messages were generated, but there was also no output was sent to the console. There is a seperate defect on reporting the right error message to the user. As regards the command line arguments this is an enh for the AC to process command line args to escape certain chars. Closing this as Works for me and will create an enh for 4.5 against the AC. Does this mean single quotes is no longer supported in the arguments? It was in previous versions tested with JVMPI. I have also found this same behavior for other arguments errors than just single quotes. In the latest test I accidently used -d instead of -D. The result was a usage message to the console but I could not launch another app successfully afterwards. After many minutes I got the same JVMTI exception and then the workbench became usable. It seems in between the error and the exception displaying the profiler is blocked. I can try to submit but the launch status just spins for a while at 51% and then disappears without error. to reproduce: 1) profile an app adding the VM Argument: -dprop1="prop one" 2) notice usage message to console 3) try to rerun the profile with -Dprop1="prop one" eventually you will get an exception error. Close this and try to run the properly configured launch again. Alexander - if you have time after you are done with 194939 - take a look at this. Reassigning to Igor. This defect is fixed in TPTP build #200805130100. 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. |