before.
I realized that I could solve my problem by moving the con.close()
into the try-block, but shouldn't closing invalidated connections
still keep them invalidated?
Regards,
Meikel Bisping
-
To unsubscribe, e-mail
Your patch is more elegant and works just fine
Thanks Dirk.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Your patch is more elegant and works just fine
Thanks Dirk.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
();
}
PoolingDriver.setAccessToUnderlyingConnectionAllowed(rememberState);
}
//end patch invalidateConnections
}
Regards,
Meikel Bisping
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
in use, though).
It didn't support read-only mode and threw an SQLException even when
calling setReadOnly(false).
It would be helpful for users if in cases like that the actual
exception would be thrown, pool exhausted didn't help much.
Cheers,
Meikel Bisping
