使用Microsoft SQL Server JDBC驱动程序的间歇性连接失败

Question

我一直在使用Microsoft SQL Server JDBC驱动程序遇到间歇性连接失败。我最近将java.util.logging配置添加到系统中，并且能够捕获成功连接和失败连接，两者都使用相同的代码和环境。

在失败的情况下，我看到了这一系列的日志消息：

Jun 01, 2015 3:42:32 PM com.microsoft.sqlserver.jdbc.SQLServerConnection <init>
FINE: ConnectionID:1 created by (SQLServerDriver:3)
Jun 01, 2015 3:42:32 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINER: ConnectionID:1 Start time: 1433173352072 Time out time: 1433173367072 Timeout Unit Interval: 15000
Jun 01, 2015 3:42:32 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINE: ConnectionID:1 This attempt server name: aws-db1-ws2008r2.datical.net port: 1444 InstanceName: null useParallel: false
Jun 01, 2015 3:42:32 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINE: ConnectionID:1 This attempt endtime: 1433173367072
Jun 01, 2015 3:42:32 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINE: ConnectionID:1 This attempt No: 0
Jun 01, 2015 3:42:32 PM com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper
FINE: ConnectionID:1 Connecting with server: aws-db1-ws2008r2.datical.net port: 1444 Timeout slice: 14597 Timeout Full: 15
Jun 01, 2015 3:42:32 PM com.microsoft.sqlserver.jdbc.TDSChannel open
FINER: TDSChannel (ConnectionID:1): Opening TCP socket...
Jun 01, 2015 3:42:34 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 25ce5505-c111-4fde-a135-7a55ce503be7 Requesting encryption level:OFF
Jun 01, 2015 3:42:34 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 25ce5505-c111-4fde-a135-7a55ce503be7 ActivityId ba082894-01df-4c7a-bcd3-8519c6a05d59-1
Jun 01, 2015 3:42:34 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINE: ConnectionID:1 ClientConnectionId: 25ce5505-c111-4fde-a135-7a55ce503be7 Server returned major version:11
Jun 01, 2015 3:42:34 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 25ce5505-c111-4fde-a135-7a55ce503be7 Negotiated encryption level:OFF
Jun 01, 2015 3:42:34 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 25ce5505-c111-4fde-a135-7a55ce503be7 Ignoring prelogin response option:5
Jun 01, 2015 3:42:34 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
FINER: TDSChannel (ConnectionID:1) Enabling SSL...
Jun 01, 2015 3:42:34 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
FINER: TDSChannel (ConnectionID:1) SSL handshake will trust any certificate
Jun 01, 2015 4:04:04 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
FINER: TDSChannel (ConnectionID:1) Starting SSL handshake
Jun 01, 2015 4:04:04 PM com.microsoft.sqlserver.jdbc.TDSChannel write
FINER: TDSChannel (ConnectionID:1) write failed:Connection reset by peer: socket write error
Jun 01, 2015 4:04:04 PM com.microsoft.sqlserver.jdbc.SQLServerException logException
FINE: *** SQLException:ConnectionID:1 ClientConnectionId: 25ce5505-c111-4fde-a135-7a55ce503be7 com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error ClientConnectionId:25ce5505-c111-4fde-a135-7a55ce503be7 Connection reset by peer: socket write error ClientConnectionId:25ce5505-c111-4fde-a135-7a55ce503be7
Jun 01, 2015 4:04:04 PM com.microsoft.sqlserver.jdbc.SQLServerException logException
FINE: com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1654)com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:1805)com.microsoft.sqlserver.jdbc.TDSWriter.flush(IOBuffer.java:3581)com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(IOBuffer.java:3482)com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(IOBuffer.java:3062)com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeOutputStream.endMessage(IOBuffer.java:770)com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.ensureSSLPayload(IOBuffer.java:633)com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.readInternal(IOBuffer.java:708)com.microsoft.sqlserver.jdbc.TDSChannel$SSLHandshakeInputStream.read(IOBuffer.java:700)com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.readInternal(IOBuffer.java:895)com.microsoft.sqlserver.jdbc.TDSChannel$ProxyInputStream.read(IOBuffer.java:883)sun.security.ssl.InputRecord.readFully(InputRecord.java:442)sun.security.ssl.InputRecord.read(InputRecord.java:480)sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1323)com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1618)com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1323)com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012)com.datical.hammer.core.connectionservice.DatabaseBuilder.createDatabaseObject(DatabaseBuilder.java:217)com.datical.hammer.core.connectionservice.DatabaseBuilder.buildDatabase(DatabaseBuilder.java:130)com.datical.hammer.core.connectionservice.DatabaseBuilder.buildConnection(DatabaseBuilder.java:56)com.datical.hammer.integration.TeztUtils.testConnection(TeztUtils.java:704)com.datical.hammer.integration.Databases.printActivatedDbs(Databases.java:219)com.datical.hammer.integration.Databases.<clinit>(Databases.java:193)com.datical.hammer.integration.AllTheseChangeLogsOnExistingDBShouldPassForecastTest.parameters(AllTheseChangeLogsOnExistingDBShouldPassForecastTest.java:94)sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:606)org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)org.junit.runners.Parameterized.allParameters(Parameterized.java:292)org.junit.runners.Parameterized.<init>(Parameterized.java:282)sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)java.lang.reflect.Constructor.newInstance(Constructor.java:526)org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:29)org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:21)org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26)org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:262)org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
Jun 01, 2015 4:04:04 PM com.microsoft.sqlserver.jdbc.SQLServerConnection:1 close
FINER: ENTRY

在成功案例中，我看到了这个序列：

Jun 01, 2015 4:24:42 PM com.microsoft.sqlserver.jdbc.SQLServerConnection <init>
FINE: ConnectionID:1 created by (SQLServerDriver:3)
Jun 01, 2015 4:24:42 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINER: ConnectionID:1 Start time: 1433175882745 Time out time: 1433175897745 Timeout Unit Interval: 15000
Jun 01, 2015 4:24:42 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINE: ConnectionID:1 This attempt server name: aws-db1-ws2008r2.datical.net port: 1444 InstanceName: null useParallel: false
Jun 01, 2015 4:24:42 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINE: ConnectionID:1 This attempt endtime: 1433175897745
Jun 01, 2015 4:24:42 PM com.microsoft.sqlserver.jdbc.SQLServerConnection login
FINE: ConnectionID:1 This attempt No: 0
Jun 01, 2015 4:24:42 PM com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper
FINE: ConnectionID:1 Connecting with server: aws-db1-ws2008r2.datical.net port: 1444 Timeout slice: 14982 Timeout Full: 15
Jun 01, 2015 4:24:42 PM com.microsoft.sqlserver.jdbc.TDSChannel open
FINER: TDSChannel (ConnectionID:1): Opening TCP socket...
Jun 01, 2015 4:24:43 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 15848334-e973-4c17-ad0f-79ebf0f4e9da Requesting encryption level:OFF
Jun 01, 2015 4:24:43 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 15848334-e973-4c17-ad0f-79ebf0f4e9da ActivityId 22b9780e-325e-4057-8a34-845c7024a2eb-1
Jun 01, 2015 4:24:43 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINE: ConnectionID:1 ClientConnectionId: 15848334-e973-4c17-ad0f-79ebf0f4e9da Server returned major version:11
Jun 01, 2015 4:24:43 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 15848334-e973-4c17-ad0f-79ebf0f4e9da Negotiated encryption level:OFF
Jun 01, 2015 4:24:43 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
FINER: ConnectionID:1 ClientConnectionId: 15848334-e973-4c17-ad0f-79ebf0f4e9da Ignoring prelogin response option:5
Jun 01, 2015 4:24:43 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
FINER: TDSChannel (ConnectionID:1) Enabling SSL...
Jun 01, 2015 4:24:43 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
FINER: TDSChannel (ConnectionID:1) SSL handshake will trust any certificate
Jun 01, 2015 4:24:47 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
FINER: TDSChannel (ConnectionID:1) Starting SSL handshake
Jun 01, 2015 4:24:47 PM com.microsoft.sqlserver.jdbc.TDSChannel$PermissiveX509TrustManager checkServerTrusted
FINER: TDSChannel (ConnectionID:1) (PermissiveX509TrustManager): Trusting server certificate
Jun 01, 2015 4:24:47 PM com.microsoft.sqlserver.jdbc.TDSChannel enableSSL
FINER: TDSChannel (ConnectionID:1) SSL enabled
Jun 01, 2015 4:24:47 PM com.microsoft.sqlserver.jdbc.TDSChannel disableSSL
FINER: TDSChannel (ConnectionID:1) Disabling SSL...
Jun 01, 2015 4:24:47 PM com.microsoft.sqlserver.jdbc.TDSChannel disableSSL
FINER: TDSChannel (ConnectionID:1) Closing SSL socket
Jun 01, 2015 4:24:47 PM com.microsoft.sqlserver.jdbc.TDSChannel disableSSL
FINER: TDSChannel (ConnectionID:1) SSL disabled

特别令人愤怒的一件事是，当它失败时，需要很长时间才能失败 - 请注意故障日志中从下午3:42:34到4:04:04的22分钟以上的差距。

修改 我已经决定将调用包装在connect()中的Callable方法中，并使用Guava SimpleTimeLimiter类来防止这种情况长时间挂起。如果它要连接，它将快速连接。我还引入了一个重试循环，因此它将重试连接尝试5次。我今晚会让我的集成测试运行，看看会发生什么。

更新 添加超时和重试逻辑没有帮助。如下面的评论中所述，我注意到当此代码从Jenkins从属进程（作为Windows服务运行，以用户'Jenkins'身份登录）运行时，连接失败〜90％的时间并且接下来的其他10个％。如果我使用远程桌面并以'Jenkins'身份登录，则从命令提示符运行相同的命令，它始终连接没有问题。设置系统属性javax.net.debug=all表示在这两条消息之后发生'挂起'：

trigger seeding of SecureRandom
done seeding SecureRandom

在成功案例中，这些消息之后是与SSL握手相关的消息，包括不可用的密码套件列表和消息Is initial handshake: true