| Summary: | [dstore] Trace should be written when load miner is failed. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Target Management | Reporter: | Missing name <mayu> | ||||
| Component: | RSE | Assignee: | David McKnight <dmcknigh> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Martin Oberhuber <mober.at+eclipse> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | dmcknigh, onno | ||||
| Version: | 3.2.2 | ||||||
| Target Milestone: | 3.4 M5 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 367420, 367421 | ||||||
| Attachments: |
|
||||||
|
Description
Missing name
Does RDz use DSTORE_TRACING_ON or do you just use the rsecomm logging? RDz uses DSTORE_TRACING_ON. We would like to get dstore trace when a Exception occurs in org.eclipse.dstore.internal.core.server.loadMiner to figure out which class or miner causes error. please backport to 3.2.x and 3.0.x Created attachment 208731 [details]
patch to add tracing - and disable any remote lookup of classes
With this patch I also disable the remote lookup of unfound classes since it may lead to unexpected results.
I've committed the fix to the HEAD stream. I opened bug 367420 for the 3.2.x backport. I opened bug 367421 for the 3.0.x backport. |