View Issue Details

IDProjectCategoryView StatusLast Update
0015533phplist applicationMessage Managementpublic01-11-12 21:45
Reporterh2b2 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2.10.12 
Target Version4.0.xFixed in Version2.11.8 
Summary0015533: Wrong processing time reported after processing requeued message
DescriptionIssue reported by jshel:
===== Start quote =====
when I receive the "PHPlist mailist processing info" system admin message, it is reporting the following...

[Wed 11 Aug 2010 07:33] [X.XXX.90.71] Processing message 12
[Wed 11 Aug 2010 07:33] [X.XXX.90.71] Looking for users
[Wed 11 Aug 2010 07:33] [X.XXX.90.71] Found them: 97 to process
[Wed 11 Aug 2010 07:47] [X.XXX.90.71] Processed 97 out of 97 users
[Wed 11 Aug 2010 07:47] [X.XXX.90.71] It took 47 hours 24 mins 2 secs to
send this message
[Wed 11 Aug 2010 07:47] [X.XXX.90.71] Script stage: 5
[Wed 11 Aug 2010 07:47] [X.XXX.90.71] 97 messages sent in 807.65 seconds
(432 msgs/hr)

===== End quote =====
phpList reports "It took 47 hours 24 mins 2 secs to send this message" while it actually took 14 minutes, if you look at the time stamps.
Additional InformationSeems related to http://mantis.phplist.com/view.php?id=4411 though the fix for that issue (messages php, line 92) is still in place.
TagsNo tags attached.

Relationships

related to 0004411 resolvedmichiel Requeue message uses original time to calculate how long the message took to send. 

Activities

h2b2

22-08-10 15:02

manager   ~0051069

Related forum thread: http://forums.phplist.com/viewtopic.php?f=17&t=32799&start=0

michiel

29-04-11 18:05

manager   ~0051216

hmm, the tricky bit is the mixing of batch processing and the like

if it uses the sendstart per queue run it would basically only give the time of the last batch run.

instead it records the "start" of sending and never touches that again.

this needs a little bit more work to sort out properly, probably by storing start and end times differently.

michiel

01-11-12 21:45

manager   ~0051837

0004411 fixed it for manually requeued messages, but not for automatically requeued messages.

revision 3399