As you see below, something seems....whacked. A simple loop with an unpooled connection (code provided below) often gives an exception when connecting. The Thread.sleep statement has been made as high as 5000 ms, and exceptions still sporadically occur.
I don't know if this is a JDBC driver issue or core server issue. Or something here. But the code is so simple....
