| Summary: | Dump Inspector doesn't read dumps | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Vladimir Stevanovic <vstevanovic> |
| Component: | runtime | Assignee: | Chris Frost <eclipse> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | b.kapukaranov, eclipse, glyn.normington, troycald, vstevanovic |
| Version: | 3.0.0.M06 | ||
| Target Milestone: | 3.0.0.RC1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Vladimir Stevanovic
If needed I could provide test PAR. Also, the dump generated by M06 could not be read by M05 Thanks for raising this and sorry you are having so much trouble with our resolution diagnostics! FWIW - The StandardDumpPathLocator is returning a null dump directory. Something seems to be wrong with the the medic configuration. Looking at the configuration sets it appears that many of the config sets from M05 have gone missing. Perhaps related to the introduction of the osgi.console config sets? (In reply to comment #4) > FWIW - The StandardDumpPathLocator is returning a null dump directory. > Something seems to be wrong with the the medic configuration. > Looking at the configuration sets it appears that many of the config sets from > M05 have gone missing. Perhaps related to the introduction of the osgi.console > config sets? Great observation Troy! M06 introduced an additional instance of config admin in order to configure the new shell separately in the kernel and user regions. Copying in Borislav who made that change for his thoughts. Targeting 3.0.0.RC1 to indicate this bug is a "must fix". This is fixed, the admin console now looks up the configuration using MBeans and correctly resolves the configured dump directory. Thanks for raising the bug and the diagnostics. |