为什么我们的连接池关闭？(Why is our Connection Pool Closing?)

 我们有一台运行在Windows Server 2008 R2上运行的Apache Tomcat 7.0.54上的JSF2.0网络服务器。 我们在运行的计算机上安装了2台SQL服务器，另一台托管了我们的库存软件。 我们网页的一部分是验证PartNumbers被添加。 在阅读了Connection Pools是与SQL服务器交流的最佳实践之后，我们创建了一个并用它来对我们的库存软件进行一些验证。 
 
 因为我想要一种方法来检查连接池的健康状况，我使用ViewScoped支持bean创建了一个测试页面，验证2个已知的良好部件号。 今天是本周第二次出现错误消息“连接已关闭”。 由于我是新手，并且似乎无法找到关于此的任何信息，所以我对我们没有设置正确的东西感到困惑。 我刚刚重置了Apache服务器，并且它已备份并正在运行。 所以..要创建我们的连接池，我在应用程序的META-INF / context.xml中添加了一些代码。 
 
    <Resource type="javax.sql.DataSource"
        name="jdbc/FOODB"
        factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
        driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
        url="jdbc:sqlserver://Foobar\Inventory;databaseName=FooInventory;user=johnDoe;password=astrongpassword;"
    />
 
 我必须使用ConnectionPool的基本概念是我有一个名为SqlAccessCommand的接口。 它或多或少是一种适配器模式。 在我的测试页面中，我使用RunUnsafe方法，以便可以显示错误消息。 所以这里是RunUnsafe方法。 
 
protected static DataSource getDataSource() throws NamingException {
    Context context = (Context) new InitialContext().lookup("java:/comp/env");
    DataSource ds = (DataSource) context.lookup("jdbc/FOODB");
    return ds;
}
public static <T> T RunUnsafe(SqlAccessCommand<T> command) throws NamingException, SQLException {
    try {
        DataSource ds = getDataSource();
        try (Connection connection = ds.getConnection();
                PreparedStatement statement = connection.prepareStatement(command.getSqlStatement())) {
            command.prepareStatment(statement);
            try (ResultSet rs = statement.executeQuery()) {
                return command.getResults(rs);
            }
        }
    } catch (NamingException | SQLException e) {
        Logger.getLogger(AOSqlInformationHolder.class.getName()).log(Level.SEVERE, null, e);
        throw e;
    }
}
 
 正如你所看到的，我使用了试用资源，它应该在使用后关闭我的连接，无论如何。 就像try / catch /最后一样，只是更清洁（IMO）。 所以当我的连接打开时，这工作得很好。 到目前为止2x现在我不得不重新启动服务器（因为我不知道如何以其他方式重新打开连接）我错过了什么？ 如果需要拼图的更多部分给我留言，我会发布我能做的。 谢谢。 
 
 编辑 
 
 只是看了看日志文件，今天早上抛出了这个异常 
 
 com.microsoft.sqlserver.jdbc.SQLServerException：由peer重置的连接：套接字写入错误 
 
 根据迄今为止的评论，它被假定为暂停。 这个错误信息仍然指向那个方向吗？ 

We have a JSF2.0 webserver running on Apache Tomcat 7.0.54 running on Windows Server 2008 R2. We have 2 SQL servers on on the machine this is running on, and another which hosts our inventory software. One part of our webpage is validation of PartNumbers being added. After reading that Connection Pools are best practice for talking with SQL servers we created one and used it for some of the validation against our inventory software.
 
Because I wanted a way to be able to check the health of the connection pool I created a test page with a ViewScoped backing bean that validates 2 known good part numbers. Today is the second time this week that the error message "Connection is closed" appeared. Since i'm new to conenction pools and can't seem to find any information regarding this I'm baffled as to what we didn't setup right. I just now reset the Apache server and it is back up and running. So.. to create our connection pool I added some code to the app's META-INF/context.xml.
 
    <Resource type="javax.sql.DataSource"
        name="jdbc/FOODB"
        factory="org.apache.tomcat.jdbc.pool.DataSourceFactory"
        driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
        url="jdbc:sqlserver://Foobar\Inventory;databaseName=FooInventory;user=johnDoe;password=astrongpassword;"
    />
 
The basic concept that I have to use the ConnectionPool is that I have an interface called SqlAccessCommand. It is more or less an adapter pattern. In my test page i use the RunUnsafe method so that I can display the error message. So here is the RunUnsafe method.
 
protected static DataSource getDataSource() throws NamingException {
    Context context = (Context) new InitialContext().lookup("java:/comp/env");
    DataSource ds = (DataSource) context.lookup("jdbc/FOODB");
    return ds;
}
public static <T> T RunUnsafe(SqlAccessCommand<T> command) throws NamingException, SQLException {
    try {
        DataSource ds = getDataSource();
        try (Connection connection = ds.getConnection();
                PreparedStatement statement = connection.prepareStatement(command.getSqlStatement())) {
            command.prepareStatment(statement);
            try (ResultSet rs = statement.executeQuery()) {
                return command.getResults(rs);
            }
        }
    } catch (NamingException | SQLException e) {
        Logger.getLogger(AOSqlInformationHolder.class.getName()).log(Level.SEVERE, null, e);
        throw e;
    }
}
 
As you can see i use the try with resources which is supposed to close my connections after use no matter what. Much like the try/catch/finally does, just cleaner (IMO). so when my connection is open this works just fine. so far 2x now I have had to restart the server (since I don't know how to re-open said connection any other way) what am I missing? If more parts of the puzzle are needed leave me a comment and I will post what I can. Thank you.
 
EDIT
 
just looked into the log files and this morning there was this exception thrown
 
com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error
 
According to the comments thus far it was assumed a timeout. Does this error message still point in that direction?

原文：https://stackoverflow.com/questions/27024861