Order XML overflows for repeated orders

If an order is in a job chain with
orders_recoverable="yes"
and a simple repeat run time like
<run_time>
<period repeat="60"/>
</run_time>

then the log of the order is continued on each repeat. As the job chain has orders_recoverable="yes", this growing log will be written to the ORDER_XML column of the SCHEDULER_ORDERS table.
As long as Job Scheduler is not restarted this clob will grow bigger and bigger which will not only result in a high tablespace usage but may also cause problems because:

• tcp Packet size limitations in MySQL
• clob size limitations
• memory problems in the jvm that connects to the db (might even cause a scheduler crash)

Solution: The order log needs to be reset on every repeat of an order