Bug #5884
closedReply by email double posting issues
0%
Description
Hi Ray,
Earlier today, I received a double notification for a message posted to a group. Today, I posted to a group using RBE and received a notification of the message posting but also an email saying the message couldn't be posted, which I assume came from a second attempt at posting
Files
Related issues
Updated by Raymond Hoh over 8 years ago
- Status changed from Assigned to Resolved
- Target version set to Not tracked
I disabled RBE to let the duplicate connections run its course and then, I reactivated RBE.
Should be resolved for now, but I'll see what I can do to prevent these duplicate connections some more.
Updated by Matt Gold over 8 years ago
Hi Ray --
Looks like this is still happening. Please see attached
Updated by Matt Gold over 8 years ago
- File Screen Shot 2016-08-16 at 5.19.37 PM.png Screen Shot 2016-08-16 at 5.19.37 PM.png added
- Status changed from Resolved to Assigned
FYI -- still happening. New screenshot attached
Updated by Raymond Hoh over 8 years ago
I deactivated RBE to let the duplicate connections run its duration and reactivated RBE afterwards.
It seems like the new Memcached RBE set up is more prone to duplicate connections. I'll see what I can do to reduce these instances.
Updated by Matt Gold about 8 years ago
Hi Ray -- FYI, this continues to occur
Updated by Raymond Hoh about 8 years ago
Thanks for the report, Matt.
I'm switching back to the filesystem to store the IMAP connection data for now to see what happens. Using memcached to store the IMAP connection data appears to be causing issues that I'm having trouble debugging.
I have another idea I'm thinking about that only starts up the IMAP connection from the admin area. I think combining this with the auto-connect option might also fix the problem with memcached. Will do some local experiments.
Updated by Raymond Hoh over 5 years ago
- Related to Bug #7762: RBE post didn't go through added
Updated by Raymond Hoh over 5 years ago
- Status changed from Assigned to Resolved
Should be resolved in #7762.
Forgot to go back and find all related open issues!