On 04/10/2010 08:27, Mladen Turk wrote:
On 10/03/2010 03:02 PM, Mark Thomas wrote:
I've seen the shut down issues reported in [1] with the 1.1.20 native
connector on Windows, Linux and OSX. Has a bug crept in here or do the
changes to the shut down code mean we need to release 1.1.21?
On 10/04/2010 10:34 AM, Mark Thomas wrote:
On 04/10/2010 08:27, Mladen Turk wrote:
On 10/03/2010 03:02 PM, Mark Thomas wrote:
I've seen the shut down issues reported in [1] with the 1.1.20 native
connector on Windows, Linux and OSX. Has a bug crept in here or do the
changes to the shut down
On 10/03/2010 03:02 PM, Mark Thomas wrote:
I've seen the shut down issues reported in [1] with the 1.1.20 native
connector on Windows, Linux and OSX. Has a bug crept in here or do the
changes to the shut down code mean we need to release 1.1.21?
Nope.
The fix in Java side (I did with 992211
On 10/04/2010 10:34 AM, Mark Thomas wrote:
On 04/10/2010 08:27, Mladen Turk wrote:
On 10/03/2010 03:02 PM, Mark Thomas wrote:
I've seen the shut down issues reported in [1] with the 1.1.20 native
connector on Windows, Linux and OSX. Has a bug crept in here or do the
changes to the shut down
On 10/04/2010 10:34 AM, Mark Thomas wrote:
That's likely my bad then. I'll take a look. Thanks for the confirmation.
Fixed. It was getSocketProperties().getSoTimeout() returning -1
causing exception
Now it defaults to 2 seconds, which means that in the
worse case it'll be called 30 times for
On 04/10/2010 10:27, Mladen Turk wrote:
On 10/04/2010 10:34 AM, Mark Thomas wrote:
That's likely my bad then. I'll take a look. Thanks for the confirmation.
Fixed. It was getSocketProperties().getSoTimeout() returning -1
causing exception
Now it defaults to 2 seconds, which means that in
I've seen the shut down issues reported in [1] with the 1.1.20 native
connector on Windows, Linux and OSX. Has a bug crept in here or do the
changes to the shut down code mean we need to release 1.1.21?
Cheers,
Mark
[1] https://issues.apache.org/bugzilla/show_bug.cgi?id=49923