WU graph view fails with IPropertyTree: Ambiguous xpath used getProp: ambiguous xpath "node[@id="51"]"
Field Tab
Administrator use only
Field Tab
Administrator use only
Environment
UK NTT
Description
Conclusion
None
Activity
Show:

Gavin Halliday November 5, 2015 at 11:12 AM
I have reproduced it on a simple example. It occurs for hthor queries, where a child query has multiple subgraphs.

Gavin Halliday November 4, 2015 at 5:21 PM
It looks like there is a stats entry for the subgraph, and also one for the subgraph that contains the child query with the subgraph. The first one should not be present.
I'll try and reproduce it on a simple example.

Gavin Halliday November 4, 2015 at 5:13 PM
It looks like the problem occurs when merging in the graph results.
The merged results contain a duplicate entry. This is for a child query, running on hthor.

Jacob Cobbett-Smith November 4, 2015 at 4:22 PM
Kevin can you look/try to reproduce this please.

Jacob Cobbett-Smith November 4, 2015 at 4:15 PM
I've looked at an example of this, and there is no ambiguity in the generated XML.
So I think fault must lie in either the workunit code processing the graphs, or in eclwatch code.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Gavin HallidayGavin HallidayReporter
charles mortoncharles mortonPriority
MajorFix versions
Pull Request URL
Details
Details
Assignee

Reporter

Priority
Fix versions
Pull Request URL
Created September 22, 2015 at 8:19 PM
Updated November 10, 2015 at 1:46 PM
Resolved November 10, 2015 at 1:46 PM
we are on 5.2.8-rc1
here is an example:
http://10.193.64.21:8010/?Wuid=W20150922-211522&GraphName=graph1&SafeMode=false&Widget=GraphPageWidget
the full error is:
WsWorkunits.WUGetGraph
2015-09-22 20:20:27 GMT: IPropertyTree: Ambiguous xpath used getProp: ambiguous xpath "node[@id="51"]"