HPR Troubleshoot:how to trace conflicting routing options?

Bernd Welter · Post by **Bernd Welter** » Fri Jan 08, 2021 12:43 pm

Hi there,

sometimes you may encounter the fallback from HPR to CONVENTIONAL in a routing or dima request of xServer2. Though you are getting told that the fallback is applied you might want to know in depth why there's no search graph matching your requested profile.

The troubleshooting paragraph says:

Another possibility is to enable the trace logs of the corresponding service. Then, for each high-performance routing network the parameters that are different to the routing relevant parameters of the request are logged.

Here's a hint that is currently missing in the documentation and we will add it later. For the impatient ones:
Of course this is only a valid approach on premise
Add a specific logger section in the logging-module.xml to trace this in xRoute:

Code: Select all

<Logger name="com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools"
 level="trace" additivity="false">
      <AppenderRef ref="File"/>
    </Logger>

For xDima the section looks like this:

Code: Select all

<Logger name="com.ptvgroup.xserver.xdima.router.ContractionHierarchiesTools"
 level="trace" additivity="false">
      <AppenderRef ref="File"/>
</Logger>

Here's some sample trace from a logfile:

2021-01-07 11:11:01,938;DEBUG;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;No high-performance routing data available in the hpr folder of the map for current profile settings.
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;--> "/opt/maps/PTV_World_City_Map_Premium_2021_1H/hpr/46fc4498-3dc1-48c3-94e1-ca17e00a13d6"
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;differs TIMECONSIDERATION_MODE: SNAPSHOT != NONE
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;differs allowedCountries: 1110111111100111111111111111111111111110010000000110000100011111011111000000000000000000000000000000000000010000000100110000000100010000000000000000000000000011000101000000000000100001010000000000000100000000000000000000000000001110110001000010001000010000100001000100000000000000000000000000000000000000000000000000000000000000000000000000000000000 != 1111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;differs vehicleProfile/@numberOfTrailers: 1 != 0
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;differs vehicleProfile/axle/@axleLoad: 10000 != 11500
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;differs vehicleProfile/dimensions/@length: 1875 != 1650
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;differs vehicleProfile/weight/@emptyWeight: 14500 != 15000
2021-01-07 11:11:01,940;TRACE;com.ptvgroup.xserver.xroute.router.ContractionHierarchiesTools.ChDataAdministration;differs vehicleProfile/weight/@loadWeight: 25500 != 25000

Another potential source of the mismatch is the scope: if you create your own search graphs through xData you need to ensure that TENANT and SCOPE are matching, too (not a topic for global graophs)

Last but not least the allowedCountries and prohibitedCountries in a Dima request have to match, too.

Thanks to Max for the hint!
Bernd