Hi, I have one or two queries (well, 2 :-) about JRun and connection pooling that someone may be able to shed some light on. 1. When a Connection is returned to the pool, is there any attempt by the pool to reset it to a "default" state. e.g if someone's code has set the autocommit flag to be false and forgotten to reset it, will it still be false (and hence screw up) when the next piece of code (possibly from a different app) is handed out the connection and assumes that autocommit will be on? 2. The article on connection pooling on the allaire site says "All operations are wrapped in a "try/catch/finally" block. The finally block is guaranteed to execute even if an exception is thrown. We will close the Connection inside the finally block, which will release it back into the pool. Note that if you opened any JDBC Statements or ResultSets, you MUST close them as well (ResultSets first, then Statements, then the Connection). " The JDK 1.3 docs claim that closing a Statement automatically closes any open result sets which are open on it. This implies that it isn't necessary to close the ResultSets explicitly with Java 2 ... Is this the case? All the best, Luke. -- Luke Taylor. PGP Key ID: 0x57E9523C ------------------------------------------------------------------------------ Archives: http://www.egroups.com/group/jrun-interest/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
