|
Hello all, Since the beginning of this week our RT (3.4.4) system
runs really slowly. However, from today on it also gives timeouts, and
doesn’t load pages. I checked where it can be, and one thing I found out
is that when you want to retrieve a ticket, a lock is set during the time the
ticket gets displayed on the screen, for example: | 40456 | rt_user | rtdb.vianetworks.nl:56980 |
rt3 | Query | 8 | User
lock | SELECT
GET_LOCK('Apache-Session-3623293be2c14213fb0441bcba44ccf0',
3600) I suspect that during this time it is impossible to
do anything with RT. I checked this by having to windows open with RT. In
window A I opened a large ticket (time to display around 30 seconds, which is
already too long), and in window B I clicked the home button for RT. In the
mysql administrator I see the above lock, window A is filling up with the
ticket and window B is just hanging. From the moment window A is finished, the
lock is removed and window B immediately shows the main screen. Is it normal behaviour that just wanting to show a
ticket sets a lock on the whole system? We haven’t experienced not
loading of pages because of timeouts before, but that probably has something to
do with the fact that the system also seems slower. We’re running the mysql 5.0.15 on freebsd 5.4 Thanks for any help, Alain Sips |
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
