Re: MySQL communication link failure

[Stijn de Witt]

Martin Kal�n wrote:
So you should never combine autoReconnect for MySQL JDBC URL and 
testOnBorrow
for a Commons Pool-based Connection pool (like OJB's default- and 
DBCP-based
pools). If you do, you will just create additional overhead by 
checking the
same things twice.

The advantage of mastering the Commons Pool options is that this will 
work
with all database servers that OJB supports, not just MySQL.

Do you know if the autoReconnect=true option alone will fix it? I have 
seen mention of autoReconnectForPools option? We are not planning on 
migrating away from MySql anytime soon. As I understand it, I shouldn't 
'play it save' and use autoReconnect=true in combination with the 
Evictor thread solution?

Could you review these settings for the evictor thread solution? Do you 
think these settings are ok?

validationQuery="select 1"
minEvictableIdleTimeMillis="60000"
timeBetweenEvictionRunsMillis="120000"
numTestsPerEvictionRun="10"
testWhileIdle="true"
testOnBorrow="false"
testOnReturn="false"
Could I combine these with autoReconnect="true"? Would that be useful?
Which of the two options would you use?
Hope this was not too much info and that it did not confuse you more!
Regards,
 Martin

Definitely not too much info, thank you very much!
-Stijn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]