[Tickets #10776] Re: cpu usage is high (~ 100%)

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10776
------------------------------------------------------------------------------
  Ticket             | 10776
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | cpu usage is high (~ 100%)
  Queue              | IMP
  Version            | 5.0.14
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-12-12 15:47) wrote:

>> You need to provide IMAP debug logs, so we can see if we are able to
>> workaround the broken server.

This log makes no sense.  It is impossible given the current state of  
the code.

> C: 1 STARTTLS
> S: 1 OK Begin TLS negotiation now.

This is correct.

> C: 2 STARTTLS
>>> ERROR: IMAP read/timeout error.

There's no way the code could get here.  Either the original STARTTLS  
command failed and would throw an Exception (which would be logged),  
or else we move to login commands.  There simply is no way for  
consecutive STARTTLS commands to be sent.  It is an either/or - we  
attempt TLS negotiation exactly once.

My reaction is that your PHP appears badly broken.  Unless proven  
otherwise, this is the only conclusion (the IMAP server appears fine).  
  The only way I could even imagine this happening is if a single PHP  
process was somehow multi-threaded and two threads were trying to  
initiate the imap client at the same time (and if this is happening,  
your PHP is beyond badly broken).