I had read all the JNDI &
JDBC Official & Unofficial documentation but & only
found than you MUST close the connections. There insn't references to where to declare variables. Declaring into local scope forces that you have pass by reference the connection, statement and resultset in every function that handle the pool os use a class to handle the connection itsef.
El 15/12/2011 13:40, Mark Thomas escribió: On 15/12/2011 12:12, Aitor Garcia | Tempel.es wrote:I don't know if this is a tomcat bug.This is clearly not a Tomcat bug. This comes under the category of "user error".Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org |
- Re: dbcp is mixing up connections Mark Thomas
- Re: dbcp is mixing up connections Aitor Garcia | Tempel.es
- Re: dbcp is mixing up connections Pid
- Re: dbcp is mixing up connections Konstantin Kolinko
- Re: dbcp is mixing up connections Christopher Schultz
- Re: dbcp is mixing up connections Terence M. Bandoian
- Re: dbcp is mixing up connections Terence M. Bandoian
- Re: dbcp is mixing up connections Mark Eggers
- Re: dbcp is mixing up connection... Aitor Garcia | Tempel.es
- Re: [OT] dbcp is mixing up ... Christopher Schultz
- Re: dbcp is mixing up connection... Pid *
- Re: dbcp is mixing up conne... Terence M. Bandoian