[rt-users] RT hangs with 'SELECT GET_LOCK' slow query log entries

[Jesse Vincent]

On Tue, Dec 05, 2006 at 04:18:56PM +0100, Torsten Brumm wrote:
> Hi Jesse,
> 
> if i'm not completly wrong, then i think, we can set this at the
> RT_SiteConfig.pm?

Correct.

> # $WebSessionClass is the class you wish to use for managing Sessions.
> # It defaults to use your SQL database, but if you are using MySQL 3.x and
> # plans to use non-ascii Queue names, uncomment and add this line to
> # RT_SiteConfig.pm will prevent session corruption.
> 
> # Set($WebSessionClass , 'Apache::Session::File');
> 
> So, if i uncomment this, Apache:Session will write the session to the FS and
> not to the DB?!? Or is it only for the session corruption?!?

For all sessions. Be careful. It will log out all current users.

> Torsten
> 
> 2006/12/5, Jesse Vincent <jesse at bestpractical.com>:
> >
> >
> >
> >
> >On Tue, Dec 05, 2006 at 04:04:44PM +0100, Torsten Brumm wrote:
> >> Hi Jesse,
> >>
> >> >
> >> >
> >> >This happens when RT is still serving a page to the user with that
> >> >session and the user requests another page.   Sometimes, switching to
> >> >another Apache::Session backend can help.
> >> >
> >>
> >> What do you mean exactly? another perl module????
> >
> >Apache::Session can store to the filesystem (among other things)
> >perldoc Apache::Session to get started.
> >
> >-j
> >
> >> Torsten
> >
> >--
> >
> 
> 
> 
> -- 
> MFG
> 
> Torsten Brumm
> 
> http://www.torsten-brumm.de

--