Rainer Jung-3 wrote: > > What do you mean by "losing sessions"? I expect you mean users work in a > session and then they send a request and get a response indicating, that > the requested session has not been found? > > Thats exactly what I meant. > > If so: > > - does it happen in times, when you get errors in the mod_jk-log? Does > it happen at all times, or do you have peaks at special times? > > I can't figure it out, when this happens, but there isn't any special > moment I can observe. > It happens randomly. There isn't any error in mod_jk.log > > - if it happens even when there's no other problem at the same time: > > You can also add a request log to mod_jk, that logs, which worker has > beend chosen for every request. That way you do not rely on your user > feedback, but can measure the problem yourself (how many users/sessions, > what time of day etc.). > > And here I need some help. In mod_jk.log I always see the same worker - > balancer worker, so I don't know which worker has been choosen. How can I > change it ? I assume by adding request log to mod_jk you mean something > like this: > > # JkRequestLogFormat set the request format > JkRequestLogFormat "%w %V %T" > > > >> Of course sticky_session is set to "true". >> Below I paste our config files. Please help if you only can. >> >> Best regards >> Artur >> >> ###Jk status for one day: >> >> Name Type jvmRoute Host Addr Stat D F M >> V Acc Err Wr Rd Busy Max RR Cd >> worker2 ajp13 worker2 localhost:8009 127.0.0.1:8009 OK 0 >> 1 1 2144 824825 >> 512 >> 480M 5.8G 6 138 worker3 > > worker3 is in the original output and has iónly been removed by your > copy&paste? > > Right > > What was happening, when you got these 2144 Errors? The time stamps > should be available from the mod_jk log. > > "Loosing session" occurs even when there arnen't any errors in mod_jk > status manager, it just looks like with next request you have to "log in" > once more. > > >> ###httpd.mpm section: >> # worker MPM >> # StartServers: initial number of server processes to start >> # MaxClients: maximum number of simultaneous client connections >> # MinSpareThreads: minimum number of worker threads which are kept spare >> # MaxSpareThreads: maximum number of worker threads which are kept spare >> # ThreadsPerChild: constant number of worker threads in each server >> process >> # MaxRequestsPerChild: maximum number of requests a server process serves >> >> <IfModule mpm_worker_module> >> StartServers 5 >> MaxClients 448 >> MinSpareThreads 5 >> MaxSpareThreads 25 >> ThreadsPerChild 7 >> MaxRequestsPerChild 0 >> </IfModule> > > Interesting, very few ThreadsPerChild. Not really a problem, but I > wonder if this is efficient. > > We have decresed this value because we thought that maybe Apache is > opening too many threads to Tomcat. We had in Tomcat's log entries saying" > "All threads (500) are curently busy, increase maxThreds". > > Think about using connect_timeout and prepost_timeout. Maybe also set > recovery_options to 3. > > What values do you suggest for above parameters ? > > -- View this message in context: http://www.nabble.com/Mod_jk-balancing%2C-session-problem-tf2073073.html#a5710742 Sent from the Tomcat - User forum at Nabble.com.
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
