| Additional Information | Our investiagtion in the PHP code discovered the cause of the problem (or the sympton?): The embargo is set to either old_embargo + frequency or now() + frequency on the end of the queue run. based on a flag isfuture, the decision is wrongly made for the second option, as the condition "date_add(embargo,interval repeatinterval minute) > now() as isfuture" is always true. newembargo is calculated: "date_add(embargo,interval repeatinterval minute)", and newembargo2 as "date_add(now(),interval repeatinterval minute)"
then there are some lines not connected with this code, finally:
# correct some values
if (!$msgdata["isfuture"]) {
$msgdata["newembargo"] = $msgdata["newembargo2"];
this is bad coding style, not connected with the first few lines which actually calculate these values, and the whole construct is simply not correct. The clause should be IMHO "date_add(embargo,interval repeatinterval minute) < now()", then an incorrect embargo would be detected, and the normal case would be handled as it should be.
thanks for reading up to here.
|
Relationships 
Relationships 