Extended log size routsched.log with message: Assuming original behavior and retrieving 'SITENAME' from provided properties object...

[jbarreraballestas]

Describe the bug
The routsched.log is increased after update to 7.0.14 with message:
WARNING 12/05/24 20:09:57 property value source was not set. Assuming original behavior and retrieving 'SITENAME' from provided properties object.This will be removed in future releases and you should update values to ${java.SITENAME} at your earliest convenience.

To Reproduce
Update to 7.0.14 using existing database

Screenshots

Desktop/ServerSide (please complete the following information):

• OS: Red Hat Enterprise Linux
• Version 9.2

[MikeNeilson]

that'll be removed in a future release. we've introduced a way to get properties from different locations and we're still working out a few kinks on the reporting having erred on the side of more initially.

The usage causing the message is still correct, though changing to the suggested format should work and would prevent the message.

[jbarreraballestas]

Thanks for the info, I know how to set environment properties but not how to set java properties ${java.PROPERTY_NAME}.

I try -SITENAME=localhost in the start command of routsched but didn't work.
Sorry for the basic question, ¿How to set the java.SITENAME correctly?

I am new working in this project, thanks for the help!

[MikeNeilson]

oh sorry, I did not explain correctly. You do not need to set the property or environment for the SITENAME variable; it is provided to the routing spec run at usage.

The way to reference it in the spec is what's changed. If you open the routing spec (might be the source for the routing spec actually), you should see `${SITENAME} in most likely the URL field.

If you change that usage to ${java.SITENAME} the Spec should still work, but the error message goes away.

We're working on having ${SITENAME} work without the error message, but are still struggling with how to do so cleanly in the code. So still a bug and this should be left open; but the above suggestion will also continue to be valid and remove the error; it just won't work if you revert to an older version of the software so be aware of that.