tim_west
|
Posted: November 16, 2009 00:49 by tim_west
|
|
G'day Bill and all, It looks like there is a small bug - or a piece of incorrect documentation, in IMAPStore. Specifically, beginning at line 312: // check if the default client-side timeout value is overridden int connectionPoolTimeout = PropUtil.getIntSessionProperty(session, "mail." + name + ".connectionpooltimeout", -1); if (connectionPoolTimeout > 0) { clientTimeoutInterval = connectionPoolTimeout; if (debug) out.println("DEBUG: mail.imap.connectionpooltimeout: " + clientTimeoutInterval); } else clientTimeoutInterval = 45 * 100; // 45 seconds In the final line above, 45 * 100 = 4500 milliseconds = 4.5 seconds, not 45 seconds. This will lead to unexpected behavior if the clientTimeoutInterval is not overridden - sessions will be closed far more frequently than expected, and so more LOGINs will be required. Clearly, this is a low-priority issue, as the workaround is obvious: set mail.imap.connectionpooltimeout manually. Cheers, -Tim |
IMAP store clientTimeoutInterval - default value apparently incorrect
2 posts
Replies: 1 - Last Post: November 17, 2009 05:09
by: shannon
by: shannon
showing 1 - 2 of 2
Replies: 1 - Last Post: November 17, 2009 05:09
by: shannon
by: shannon
