The 'cacheFor' and 'cacheForUnit' parameters are from the alpha period
of 1.6. So no, that is not supported since it was never part of an
official release (other than a nightly early on).
Here's the doco:
https://greatbiztoolsllc.trac.cvsdude.com/mach-ii/wiki/IntroToCaching#TimeSpanCache
If you had it set to "cacheFor" than the default of "1 hour". However,
I beleive I see a defect in the code where the last cleanup timestamp is
stored in the CFC variables scope. This works fine for application or
server scopes, but when using sessions -- it's being single threaded and
may be the cause of your problem.
Let me investigate that a bit further. If it is an issue, I can get
that squared away in the 1.8.1 maintenance release. That release is
just for bug fixes for 1.8.0 so you will be able to upgrade without fear
of major changes impacting something.
HTH,
.Peter
Bryan M said the following on 30/03/10 10:47:
Hi Peter, appreciate the quick reply. I upgraded the software to
1.8.0.8 and made your other suggested changes. I think between the
upgrade and looking at TimeSpanCache and refactoring my arguments it
works. A question for you, is cacheFor supported? From what I can tell
of the TimeSpanCache it is not. This may have played a part in the
issue also.
<key name="cacheFor" value="12" />
<key name="cacheForUnit" value="hours" />
vs.
<key name="timespan" value="0,12,0,0" />
thanks again.
On Mar 30, 11:32 am, "Peter J. Farrell"<[email protected]> wrote:
First, I'd upgrade to 1.8.0 final (the version number would read 1.8.0.8).
Second, if you are reading the stats from the dashboard when the caching
scope is "session" than it won't be accurate. However, there might be a
defect when using the time span cache with sessions. I'll look into it.
Third, just for fun. You can use the new shortcuts for the "type". All
built-in caching strategies can be shortcut (as well as logging):
<parameter name="user_short_life">
<struct>
<key name="type" value="TimeSpanCache" />
<key name="scope" value="session" />
<key name="timespan" value="0,0,5,0" />
<key name="cachingEnabled" value="true" />
<key name="cleanupIntervalInMinutes" value="3" />
</struct>
</parameter>
HTH,
.Peter
Bryan M said the following on 30/03/10 08:09:
Hi All -
I know that the cache strategy must be working because others are
using it. However for awhile now I have been noticing this bug so I
thought I would post and see if anyone had guidance for me.
I define my cache strategy as:
<parameter name="user_short_life">
<struct>
<key name="type" value="MachII.caching.strategies.TimeSpanCache" />
<key name="scope" value="session" />
<key name="timespan" value="0,0,5,0" />
<key name="cachingEnabled" value="true" />
<key name="cleanupIntervalInMinutes" value="3" />
</struct>
</parameter>
The cache strategy is then injected via coldspring into my cfc's. The
actual work of putting and getting into the cache is working great,
however it never expires. I let the application sit for long lengths
of time and the objects in user_short_life never get reaped. Any
advise on this would be appreciated.
Mach II Version:
Version: 1.8.0.4 (Simplicity)
Built-on: 2009-12-27 16:42:13
CF 7
--
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/
Wiki / Documentation / Tickets:
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/
To unsubscribe from this group, send email to
mach-ii-for-coldfusion+unsubscribegooglegroups.com or reply to this email with the words
"REMOVE ME" as the subject.
