Bug in 3.1.10 (and later?) with setting infinite socket timeouts...

In MysqlIO.java you have:

            if (socketTimeout != 0) {
                try {
                    this.mysqlConnection.setSoTimeout(socketTimeout);
                } catch (Exception ex) {
                    /* Ignore if the platform does not support it */
                    ;
                }
            }

If the socketTimeout value is explicity set (even if its zero) you
should call setSoTimeout.

The problem is that if the VM default (
sun.net.client.defaultReadTimeout ) is not an infinite value and you
want MySQL to use an infinite value there's no way to tell it to do
so.

I'm just going to use 2^31 which is 24 days and plenty of near
infinite timeout but this is still a problem if you want to do it
right........

-- 
Founder/CEO Tailrank.com
Location: San Francisco, CA
AIM/YIM: sfburtonator
Skype: burtonator
Blog: feedblog.org

-- 
MySQL Java Mailing List
For list archives: http://lists.mysql.com/java
To unsubscribe:    http://lists.mysql.com/[email protected]