|
Re: EL issues SELECT 1 after every exception [SYBASE] [message #1384854 is a reply to message #1384784] |
Mon, 02 June 2014 14:17 |
Chris Delahunt Messages: 1389 Registered: July 2009 |
Senior Member |
|
|
The "SELECT 1" is issued after exceptions to determine if the exception is a communication exception that would necessitate throwing away the connection. If the test passes, the connection can be reused and placed back in the pool or the query retried. This should not cause a problem, as the select is not issued against a table, so nothing should be locked, and the connection itself should be returned to the connection pool (or released if there was a problem with it). So if you are having issues with connections, you should post the settings you are using to configure your pool, and detail what your issues are. To prevent the select, set the pingSQL in the DatabasePlatform to null using a customizer with the setPingSQL(null) method.
Best Regards,
Chris
[Updated on: Mon, 02 June 2014 14:18] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04267 seconds