[imp] Search "entire message" member function fetch() on a non-object

Samuel Wolf samuel at sheepflock.de
Tue Jun 10 10:02:57 UTC 2014


Zitat von Hiromi Kimura <hiromi at tac.tsukuba.ac.jp>:

> From: Samuel Wolf <samuel at sheepflock.de>
> Subject: Re: [imp] Search "entire message" member function fetch()  
> on a non-object
> Date: Mon, 09 Jun 2014 18:57:13 +0000
>
>>
>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>
>>> Quoting Samuel Wolf <samuel at sheepflock.de>:
>>>
>>>> Hi,
>>>>
>>>> at the moment I use IMP-6.2.0beta1* with Horde-5.2.0beta2 and
>>>> Horde_Core-2.12.0beta2 since there are some bugs which affect me in
>>>> IMP-6.2.0beta2.
>>>>
>>>> One of my user can search in the INBOX with "entire message", get the
>>>> search result and can open the message in the preview mode.
>>>> Same user can search in the "Sent" folder with "entire message", get
>>>> the search result but after select a message or double click on it
>>>> Horde show "Error when communicating with the server.".
>>>>
>>>> Horde.log:
>>>> 2014-06-07T13:53:02+00:00 EMERG: HORDE [imp] Call to a member function
>>>> fetch() on a non-object [pid 17325 on line 1616 of
>>>> "/var/www/http/horde/imp/lib/Contents.php"]
>>>>
>>>> POST https://example.com/horde/services/ajax.php/imp/showMessage
>>>> [HTTP/1.0 500 Internal Server Error 297ms]
>>>> "onFailure" {request: Object, transport: XMLHttpRequest, readyState:
>>>> 4, status: 500, statusText: "Internal Server Error", responseText:
>>>> "<html>
>>>> <head><title>Horde :: Fatal Error</title></head>
>>>> <body style="background:#fff; color:#000"><h1>A fatal error has
>>>> occurred</h1><h3>Call to a member function fetch() on a
>>>> non-object</h3><h3>Details have been logged for the
>>>> administrator.</h3></body></html>", headerJSON: null, responseXML:
>>>> null, responseJSON: null}
>>>>
>>>> It works sometimes in sent, but do not found the logic when it works
>>>> an when not. :(
>>>>
>>>> Any ideas?
>>>
>>> Absolutely no clue.  There are only two outcomes to calling fetch() -
>>> it returns a Results object or it throws an Exception.  Neither could
>>> produce this error message.  You will need to debug locally.
>>
>> Get a off list message from another user, which have the same problem.
>> He give me the hint that it is important how much search results I get
>> and he is right.
>> All mailboxes affected, also INBOX!
>>
>> Search result with the following number of messages doesn't work.
>> * 100
>> * 111
>>
>>
>> Search result with the following number of messages work.
>> * 5
>> * 62
>>
>> It looks as if must be something over 100(?) search results.
>>
>>>
>>> michael
>>>
>>> ___________________________________
>>> Michael Slusarz [slusarz at horde.org]
>>>
>>> --
>>> imp mailing list
>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>
> I can reproduce this error if I disable the 'horde cache' in configuration.
> $conf['cache']['driver'] = 'Null';

Make no difference for me, both doesn't work:
$conf['cache']['driver'] = 'Null';
$conf['cache']['driver'] = 'Xcache';

>
> But critical number of messages is different, 200 in my case.

My critical number of messages is reproducible over 68.

Must be a limit of ...?

Debian 7.5

> My server is: FreeBSD, php-5.4.29, dovecot-2.2.12
>
> -=-=-=-=-
> Hiromi Kimura, Tandem Accelerator Complex, University of Tsukuba, JAPAN
>
> --
> imp mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org





More information about the imp mailing list