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

See mailing list [1], there is a problem with IMP (?) and se

Sat, 14 Jun 2014 07:04:17 +0000

See mailing list [1], there is a problem with IMP (?) and search results. Hiromi Kimura found out [2] that the root cause is the maxsize in Horde/Core/Cache/Session.php Increase this value to open more messages of an search result in IMP. [1] http://marc.info/?t=140215085400002&r=1&w=2 [2] http://marc.info/?l=imp&m=140262211703797&w=2

Increase my xCache size to the following values and enable x

Wed, 18 Jun 2014 18:03:17 +0000

Increase my xCache size to the following values and enable xCache in horde. xcache.size = 512M xcache.var_size = 512M $conf['cache']['driver'] = 'Xcache'; Works now with over 15 000 messages.

> Hiromi Kimura found out [2] that the root cause is the max

Wed, 02 Jul 2014 21:07:19 +0000

> Hiromi Kimura found out [2] that the root cause is the maxsize in > Horde/Core/Cache/Session.php This should be irrelevant. The "solution" in there does nothing more than store more information in the session rather than offloading to the cache backend. The only thing I can think of is that your cache backend is broken. (You are not using SQL as a cache backend are you?)

>> Hiromi Kimura found out [2] that the root cause is the ma

Thu, 03 Jul 2014 01:39:20 +0000

>> Hiromi Kimura found out [2] that the root cause is the maxsize in >> Horde/Core/Cache/Session.php > > This should be irrelevant. The "solution" in there does nothing more > than store more information in the session rather than offloading to > the cache backend. > > The only thing I can think of is that your cache backend is broken. > (You are not using SQL as a cache backend are you?) I said in ML, "I can reproduce this error if I disable the 'horde cache' in configuration. $conf['cache']['driver'] = 'Null';". If I enable the cache, the search works fine. I tested NoSQL(mongodb) and local file system backends.

> The only thing I can think of is that your cache backend i

Thu, 03 Jul 2014 10:56:43 +0000

> The only thing I can think of is that your cache backend is broken. > (You are not using SQL as a cache backend are you?) Use a MySQL DB, if the DB is also used when $conf['cache']['driver'] = 'Null'; yes.

There's your problem. IMP requires a Horde_Cache driver.

Thu, 03 Jul 2014 20:45:45 +0000

There's your problem. IMP requires a Horde_Cache driver.

> There's your problem. IMP requires a Horde_Cache driver.

Thu, 03 Jul 2014 20:49:38 +0000

> There's your problem. IMP requires a Horde_Cache driver. In this case close the ticket (sorry), using now xCache.

>> There's your problem. IMP requires a Horde_Cache driver.

Thu, 03 Jul 2014 21:19:46 +0000

>> There's your problem. IMP requires a Horde_Cache driver. > In this case close the ticket (sorry), using now xCache. It sounds like the problem here is that people are confused about what cache to use. Which is a documentation issue xCache is NOT useful as a Horde_Cache backend, since it is neither persistent and/or isn't large enough to be useful on even a smallish (25+ users) installation.

Changes have been made in Git (FRAMEWORK_5_2): commit 85d37

Thu, 03 Jul 2014 21:43:36 +0000

Changes have been made in Git (FRAMEWORK_5_2): commit 85d37ae6672436acbfe6bb42a41af9938bbdcf42 Author: Michael M Slusarz Date: Thu Jul 3 15:36:35 2014 -0600 Bug #13264: Better documentation on good cache backend drivers horde/config/conf.xml | 20 +++++++++++++++++--- 1 files changed, 17 insertions(+), 3 deletions(-) http://github.com/horde/horde/commit/85d37ae6672436acbfe6bb42a41af9938bbdcf42

Changes have been made in Git (master): commit e6536d65627e

Thu, 03 Jul 2014 21:43:58 +0000

Changes have been made in Git (master): commit e6536d65627ea4fb0351692fe430333f6ad46733 Author: Michael M Slusarz Date: Thu Jul 3 15:36:35 2014 -0600 Bug #13264: Better documentation on good cache backend drivers horde/config/conf.xml | 20 +++++++++++++++++--- 1 files changed, 17 insertions(+), 3 deletions(-) http://github.com/horde/horde/commit/e6536d65627ea4fb0351692fe430333f6ad46733

Changes have been made in Git (master): commit ba60daa40ae7

Thu, 03 Jul 2014 21:44:00 +0000

Changes have been made in Git (master): commit ba60daa40ae7b63879812dbf7917d1f008d1ddc0 Author: Michael M Slusarz Date: Thu Jul 3 15:42:10 2014 -0600 Keep data in session storage if using a Null cache driver with Horde_Core_Cache_Session Bug #13264 It makes zero sense to run IMP (or any Horde app) with a null cache driver, but I guess we need to support those broken configs. framework/Core/lib/Horde/Core/Cache/Session.php | 9 +++++++-- 1 files changed, 7 insertions(+), 2 deletions(-) http://github.com/horde/horde/commit/ba60daa40ae7b63879812dbf7917d1f008d1ddc0

Increase the xCache is also NOT RECOMMENDED?

Thu, 03 Jul 2014 21:52:02 +0000

Increase the xCache is also NOT RECOMMENDED?

xCache is not recommended in general. There is NO reason

Thu, 03 Jul 2014 21:55:13 +0000

xCache is not recommended in general. There is NO reason to not be using, e.g., file-based cache instead.

> There is NO reason to not be using, e.g., file-based cache

Fri, 04 Jul 2014 00:35:45 +0000

> There is NO reason to not be using, e.g., file-based cache instead. file-based cache is faster than I thought, also faster than xCache, thanks for the hint michael!

>> There is NO reason to not be using, e.g., file-based cach

Tue, 08 Jul 2014 06:03:40 +0000

>> There is NO reason to not be using, e.g., file-based cache instead. > file-based cache is faster than I thought, also faster than xCache, > thanks for the hint michael! There's very little difference between a file-based cache and an "in-memory" cache on any recent OS since the contents of the file are almost certainly residing in memory buffers anyway (assuming, as is true for most modern boxes, that you have sufficient memory).

I'm afraid that your changes didn't really fix this issue. F

Thu, 21 Aug 2014 14:03:07 +0000

I'm afraid that your changes didn't really fix this issue. From my debug-logging, I see that the 'cache' parameter always is of the Horde_Cache type, regardless of the cache driver/backend. I can successfully use large search results (with and without caching) with the attached patch.

> I'm afraid that your changes didn't really fix this issue.

Thu, 21 Aug 2014 16:44:25 +0000

> I'm afraid that your changes didn't really fix this issue. From my > debug-logging, I see that the 'cache' parameter always is of the > Horde_Cache type, regardless of the cache driver/backend. This is incorrect. testReadWrite() should NOT be used in a production environment first of all (brutal performance hit). And regardless - this exists to catch permission issues when running Horde scripts from the command line. More important: this just masks the configuration problem of "why is your cache backend not working in the first place"? Any cache backend other than Null should obviously be read/write to Horde. Or else what's the point of defining a cache driver if you can't use it?

>> I'm afraid that your changes didn't really fix this issue

Thu, 21 Aug 2014 16:54:29 +0000

>> I'm afraid that your changes didn't really fix this issue. From my >> debug-logging, I see that the 'cache' parameter always is of the >> Horde_Cache type, regardless of the cache driver/backend. > > This is incorrect. testReadWrite() should NOT be used in a production > environment first of all (brutal performance hit). And regardless - > this exists to catch permission issues when running Horde scripts > from the command line. I almost guessed that testRW() was suboptimal, but can you please check/verify that param['cache'] is always Horde_Cache and the branching in the constructor has to depend on its _storage? > More important: this just masks the configuration problem of "why is > your cache backend not working in the first place"? Not working or not configured. Perhaps it would make sense to document the consequences of using NOT RECOMMENDED" settings?

Changes have been made in Git (FRAMEWORK_5_2): commit 2b93f

Thu, 21 Aug 2014 23:25:30 +0000

Changes have been made in Git (FRAMEWORK_5_2): commit 2b93fe89922bf97bb84f15765b53063f1257c22f Author: Michael M Slusarz Date: Thu Aug 21 17:13:14 2014 -0600 [mms] Ensure that search/POP3 mailbox listings are saved even if there is an issue with the underlying cache backend. See Ticket #13264 imp/docs/CHANGES | 2 + imp/lib/Factory/MailboxList.php | 69 ++++++++++++++++++++++++++------------ imp/package.xml | 2 + 3 files changed, 51 insertions(+), 22 deletions(-) http://github.com/horde/horde/commit/2b93fe89922bf97bb84f15765b53063f1257c22f

I added code to IMP 6.2.2 to ensure that cache backend failu

Thu, 21 Aug 2014 23:26:16 +0000

I added code to IMP 6.2.2 to ensure that cache backend failures will not cause a mailbox rebuild, which may in certain cases cause issue with UID mis-mappings.

Changes have been made in Git (master): commit 5fe2f8f15b9f

Thu, 21 Aug 2014 23:35:08 +0000

Changes have been made in Git (master): commit 5fe2f8f15b9f83719cec4159b073e90299811a4f Author: Michael M Slusarz Date: Thu Aug 21 17:13:14 2014 -0600 [mms] Ensure that search/POP3 mailbox listings are saved even if there is an issue with the underlying cache backend. See Ticket #13264 imp/docs/CHANGES | 2 + imp/lib/Factory/MailboxList.php | 78 ++++++++++++++++++++++++++++----------- imp/package.xml | 1 + 3 files changed, 59 insertions(+), 22 deletions(-) http://github.com/horde/horde/commit/5fe2f8f15b9f83719cec4159b073e90299811a4f