probably a log level FINE or DEBUG might help if the app had any,and you might be able to turn on debug level log with your JDBC driver,so that you could capture SQLs.after all this ,you got lots of info with timestamps,those might help you find the problem.
it might have a SQL performance problem,a memory usage efficiency problem or a virtual machine performance problem.... hope it helps a little On Fri, Aug 31, 2012 at 2:01 PM, David A. Rush <da...@rushtone.com> wrote: > We've got two different machines (both Windows Server something) running > Tomcat 7.0.22, and each running a webapp that uses user authentication. > We're using a couple of different schemes (LDAP and database using > JDBCRealm with hashed pwords, just database with hashed pwords). > > When no one has logged in for a while (90 minutes seems to do the trick), > the next login takes almost exactly 40 seconds on one host and almost > exactly 20 seconds on the other one. > > Hitting a page in one of the webapps that hits the database for > application data, without requiring login, works fast even if it's been > idle for hours. But then try to login and I get a 40 second delay after > whacking the "Log in" button on the login form. Looking at it in more > detail, the host and app with a 40-second delay has two JDBCRealms > configured, both inside of a combined realm. > > Are we seeing a 20-second delay in getting authentication via JDBCRealm? > > Suggestions on troubleshooting this? > > David > > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tomcat.**apache.org<users-unsubscr...@tomcat.apache.org> > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Never trust your computer.
