Luke Opperman wrote:
> Geoff wrote:
> > Servlet caches are _definitely_ cleared on appserver restart because the
> > servlet cache is entirely in memory.  What is it that's leading you to
> > believe otherwise?
> 
> I'm only thinking this based on the Admin/ServletCache page. 
> 
>   Up Since:  Wed Aug 14 03:34:41 2002 
> 
> SiteContent.py - ...\staff\Content  
>   created  1  
>   instances  Queue: []  
>   lock  <lock object at 01A9D6C8>  
>   path  ...\staff\Content\SiteContent.py  
>   reuseable  0  
>   threadsafe  0  
>   timestamp  Tue Aug 13 18:41:25 2002 (1029282085)  
>                  ^^^^^^^^^^^^^^^^^ 
> 
> Unless something funky is going on with Webware running as a 
> Service, this 
> really caught my eye.
> 

The "timestamp" is actually the modification time of the file itself, so you
shouldn't expect it to change unless the servlet code changes.  And this
example shows "instances" as an empty Queue which means that it's an empty
servlet cache, which is what you'd expect if CanBeReused is False.  Every
time this servlet is accessed a new servlet instance will be created since
there are no instances in the cache.

(In the latest Webware from CVS you'll notice that the servlet cache is no
longer a Queue -- it's a python list instead.  This fixed some rare but
serious problems with the use of non-blocking operations on Queue.  Also,
the "created" count is no longer there because it wasn't needed with the new
code.)

- Geoff


-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to