WARN PTV_SpeedPatterns is not licensed

[HaliFeri]

Hi,

(bernd: XSERS-1681)

we recently upgraded xServices (xRoute, xLocate, xMap) from 1.24.0 to 1.28.1 and since our PTV logs are full of the following warnings:

Code: Select all

2020-02-04 09:47:37,025;WARN;com.ptvag.xserver.module.xroute.m0014;163eb888-75e7-4f91-a83c-c56d1fd59dd6;default;;;The theme PTV_TruckSpeedPatterns is not licensed.
2020-02-04 09:46:42,561;WARN;com.ptvag.xserver.module.xroute.m0014;1e291a0e-369b-4729-ae18-7bf2db01680f;default;;;The theme PTV_SpeedPatterns is not licensed.

We never had license for speed patterns and never used them either. The EuropePremium.geo maps we use always contained the speed pattern feature layer as I checked.

Is there any configuration option, to mute these warnings which appear with every single routing request?
Now it's very hard to notice any real warnings.

Thank you for your help!

[Bernd Welter]

Hello HaliFeri,

here's a recommendation of our core experts: use an expression filter (available for LOG4J 1.2). You can update the configuration in the server-logging.properties:

log4j.appender.XSERVER.filter.0=org.apache.log4j.filter.ExpressionFilter
log4j.appender.XSERVER.filter.0.expression=(MSG ~= 'The theme PTV_TruckSpeedPatterns is not licensed.')||(MSG ~= 'The theme PTV_SpeedPatterns is not licensed.') log4j.appender.XSERVER.filter.0.acceptOnMatch=false

If you want to enable the server to use this feature
- download the required JAR from https://mvnrepository.com/artifact/log4 ... ras/1.2.17
- copy it to [server]/shared/lib
Best regards,
Bernd

[HaliFeri]

Thank you Bernd!

I will try this after installing the Extras module.

In the meanwhile I wonder how much performance degradation should I expect because of this new filtering.

[Bernd Welter]

how about disabling WARNINGS as a whole?

[Bernd Welter]

did you ever try to remove the spee pattern data from the map?

[HaliFeri]

Hi Bernd!

I tried the method you suggested in server-logging.properties, but it doesn't seem to change anything.
In addition with the

Code: Select all

log4j.appender.XSERVER.filter.0=org.apache.log4j.filter.ExpressionFilter
log4j.appender.XSERVER.filter.0.acceptOnMatch=false

I tried

Code: Select all

log4j.appender.XSERVER.filter.0.expression=(MSG ~= 'The theme PTV_SpeedPatterns is not licensed.')

and

Code: Select all

log4j.appender.XSERVER.filter.0.expression=(MSG ~= 'PTV_SpeedPatterns')

as well with no success.

After reading a bit about log4j 1.2, I also tried

Code: Select all

org.apache.log4j.varia.StringMatchFilter

, which doesn't need any additional lib, but it has no visible effect either.

I'm positive I'm working with the right appender settings, as when I modified the log level on the appender, I saw the effect. I also restarted the service after every config modification (the log level change took effect only after restart I think).

So right now it seems that no filtering mechanism works.

We don't really want to switch off WARN level completely, as other useful messages could be hidden that way.

[Bernd Welter]

Hello

unfortunately I am not familiar with the logging framework recommended by DEV.
What I did was easier:
- stop the service
- remove the /featurelayer folder from the map (back them up!)
- start the service

Worked fine on my local environment:

warnings.PNG (6.38 KiB) Viewed 8742 times

Best regards,
Bernd




PS: I do not expect that we create a minor 1.28 just because of this suboptimal behaviour

[HaliFeri]

We also noticed this.

Removing /featurelayer/*/{trafficpatterns,trucktrafficpatterns} folders stops the warn messages.

We will probably go with this solution.
Thank you for your support.

[Bernd Welter]

sounds good!!

C u
Bernd