Re: Tomcat 6.X and MySQL connection pooling issue

Changing testOnBorrow = true has not changed the situation with the connection pool failing -can anyone suggest anything? Thanks. Martin. MartinOShea wrote: Hello I wonder if anyone can advise me on this issue. I have a Tomcat 6.X Java / JSP application which uses connection pooling

Re: Tomcat 6.X and MySQL connection pooling issue

SIGNED MESSAGE- Hash: SHA1 Martin, On 10/1/2009 3:47 AM, MartinOShea wrote: Changing testOnBorrow = true has not changed the situation with the connection pool failing -can anyone suggest anything? Are you sure you are configuring the right connection pool? Can you turn-on query

Re: Tomcat 6.X and MySQL connection pooling issue

Chris Many thanks. I'll be trying these out over the next few days. Martin O'Shea. Christopher Schultz-2 wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin, On 10/1/2009 12:53 PM, MartinOShea wrote: private static DataSource dataSource = null; I wouldn't recommend

Tomcat 6.X and MySQL connection pooling issue

Hello I wonder if anyone can advise me on this issue. I have a Tomcat 6.X Java / JSP application which uses connection pooling to access a MySQL database but, if the application is left for up to eight hours, one of the pages fails to display the contents of a dataset upon loading. Looking

Re: Tomcat 6.X and MySQL connection pooling issue

such as validationQuery = select now() always returning the date / time? validationQuery = select now() markt-2 wrote: MartinOShea wrote: But I think what is happening after eight hours of inactivity, is that the system is trying to reuse a connection pool object that MySQL has closed down

Re: Tomcat 6.X and MySQL connection pooling issue

So select now() is fine. Thanks. markt-2 wrote: MartinOShea wrote: Thanks for the reply. Setting testOnBorrow to true is something I'll try but according to: http://commons.apache.org/dbcp/configuration.html If testOnBorrow is set to true, the validation query must be set

Re: Tomcat 6.X and MySQL connection pooling issue

The query has been changed to select 1. Thanks. Pid-6 wrote: On 30/09/2009 13:38, MartinOShea wrote: So select now() is fine. (Where fine is defined as not what you were advised to use, for sound reasons that are require a longer explanation than was necessary at the time.) p

Re: Programmatically detecting login or logout events

Chris Thanks for the reply. In the various servlets making up this application, I don't currently have a user object in every request but tend to use request.getRemoteUser() where necessary. This also to minimizes traffic. But what you've suggested is good. Thanks Martin O'Shea. -- View this

Programmatically detecting login or logout events

Hello I'm trying to find a way to detect the events caused when a user logs into or logs out of an application I'm working on. I want to record these events so that I know the exact steps a user has taken through the application's JSPs and servlets. I want to do this without reference to the

Re: Programmatically detecting login or logout events

markt-2 wrote: MartinOShea wrote: I have used request.getRemoteUser() at various points in the application to identify the current user when they are authenticated by Apache Tomcat. However, request.getRemoteUser() does not tell me when the user logged in or off