On Wed, 2005-12-07 at 21:15 -0500, Perrin Harkins wrote:
> On Wed, 2005-12-07 at 17:41 -0500, Justin Cook wrote:
> > If I change the timeout from 3600(1 hour) to a couple of seconds the
> > app doesn't hang. Is this dumb to leave like this?
>
> Yes. Turn it off completely (by using the NullLocker class) if you
> don't need locking. If you do need locking, don't change this.
I'm not sure if I need locking or not. I think I figured out why my
page request was hanging(due to passing session args in a component call
- ie <& 'comp.mas', $arg => $m->session->{arg} &>), but should I still
turn off locking completely? Is it dependent on how busy the site is
whether or not to have locking turned on?
> > One other thing I
> > notice is that when I find the app hanging(and it seems to hang when it
> > initializes a database connection) I look at mysql running processes
> > and find a couple - one thats doing the GET_LOCK on the session table
> > and another one that's sleeping. When I kill the sleeping one the page
> > then loads. Help!!
>
> That means you have a reference to your Apache::Session object in memory
> somewhere that isn't going out of scope and thus isn't getting cleaned
> up. It will keep the lock until it gets DESTROYed. Fix your scoping
> bug and this will go away.
Could this reference not going out of scope be the session parameter
being used in a component(in the page being requested) call by chance?
Justin
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
