[Tickets #12837] Re: Imap_Client: Leaking IMAP socket on error

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12837
------------------------------------------------------------------------------
  Ticket             | 12837
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Imap_Client: Leaking IMAP socket on error
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-11-15 10:43) wrote:

I've just quickly hacked together the test script to check if it  
really allocates a socket to the IMAP server when an exception is  
thrown. listMailboxes() was added to do something on the socket.
(I had to "reverse diagnose" the issue since I just saw the server ran  
out of sockets.)

It seems to me the PHP gc does not clean up the $imap object when it's  
still inside the loop.

I'm not sure how I can see what part of horde actually caused the  
problem on a productive box, ActiveSync was not in use and still  
something got stuck in an endless loop. We have an unlimited  
maximum_execution_time and I now changed it to 43200 seconds. That  
should be way enough.

I'll check the Kolab code if it properly reuses the Imap_Client  
object, that's a good hint.