Java SQL错误：0，SQLState:08006

我有一个与hibernate连接的web应用程序。应用程序正在连接到PostgreSQL数据库。有时我的日志中会出现以下异常

Caused by: **org.postgresql.util.PSQLException: An I/O error occured while sending to the backend.**
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:283)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:353)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:252)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at org.geotools.jdbc.JDBCFeatureReader.<init>(JDBCFeatureReader.java:150)
at org.geotools.jdbc.JDBCFeatureSource.getReaderInternal(JDBCFeatureSource.java:567)
... 101 more
**Caused by: java.io.EOFException**
at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:261)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1620)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)






Caused by: org.postgresql.util.PSQLException: **An I/O error occured while sending to the backend.**
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:283)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:353)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:252)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:208)
at org.geotools.jdbc.JDBCFeatureReader.<init>(JDBCFeatureReader.java:150)
at org.geotools.jdbc.JDBCFeatureSource.getReaderInternal(JDBCFeatureSource.java:567)
... 101 more
**Caused by: java.net.SocketException: Connection reset**
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at org.postgresql.core.VisibleBufferedInputStream.readMore(VisibleBufferedInputStream.java:135)
at org.postgresql.core.VisibleBufferedInputStream.ensureBytes(VisibleBufferedInputStream.java:104)
at org.postgresql.core.VisibleBufferedInputStream.read(VisibleBufferedInputStream.java:73)
at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:259)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1620)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)

我的服务器操作系统是-Red Hat Enterprise Linux 6 64位 和postgreSQL版本-postgreSQL 9.1

根据，您面临连接失败问题。因此请检查以下步骤

将连接配置检查到hibernate中 配置文件

检查数据库连接是否打开

检查您的网络连接

以上不正确，请再次发布您的postgressql日志文件

---

好的，这很有趣：

2014-02-19 07:22:35 IST日志：服务器进程（PID 74813）被信号6终止：中止

这表示PostgreSQL server后端正在崩溃。具体地说，信号6（SIGABRT）是由断言失败触发的，它故意使代码崩溃，因为出现了错误，并且如果不冒数据损坏的风险，它将无法继续

如果您没有运行PostgreSQL版本的最新补丁（您没有提到），请立即更新

（剩下的问题确实更多，但SO的格式有时会使评论过于严格）：

我建议启用带有

log\u line\u前缀的
log\u statement=all
，该前缀至少包括后端pid和事务ID。然后重新加载PostgreSQL以激活设置。当问题再次出现时，请查看查询日志，查看崩溃进程在崩溃时正在执行什么。查看是否在控制台上以交互方式运行相同的语句也会导致崩溃

我还建议为您的PostgreSQL版本启用核心转储文件并下载debuginfo包。这将允许您将调试器附加到一个文件，该文件包含服务器崩溃时的状态，并希望看到出现了什么问题。如何启用核心转储是操作系统/发行版特有的，您还没有提到您的操作系统和版本，因此我无法提供更具体的说明；请参阅Google。
在我的例子中，此错误是由于我对表进行了截断，但没有提交事务而导致的。（我使用了DBeaver工具）
OO，这很有趣，它正在随着SIGABRT而消亡，可能是断言失败。在那次坠机之前日志里有什么东西吗？您使用的是什么PostgreSQL版本<代码>选择版本（）

请。在什么操作系统/版本上？

<property name="hibernate.c3p0.min_size">5</property>
    <property name="hibernate.c3p0.max_size">20</property>
    <property name="hibernate.c3p0.timeout">5000</property>
    <property name="hibernate.c3p0.max_statements">0</property>
    <property name="hibernate.c3p0.idle_test_period">3000</property>

2014-02-19 07:22:35 IST LOG:  server process (PID 74813) was terminated by signal 6: Aborted
2014-02-19 07:22:35 IST LOG:  terminating any other active server processes
2014-02-19 07:22:35 IST WARNING:  terminating connection because of crash of another server process
2014-02-19 07:22:35 IST DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014-02-19 07:22:35 IST HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2014-02-19 07:22:35 IST WARNING:  terminating connection because of crash of another server process
2014-02-19 07:22:35 IST DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014-02-19 07:22:35 IST HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2014-02-19 07:22:35 IST LOG:  all server processes terminated; reinitializing
2014-02-19 07:22:35 IST LOG:  database system was interrupted; last known up at 2014-02-19 07:22:29 IST
2014-02-19 07:22:35 IST LOG:  database system was not properly shut down; automatic recovery in progress
2014-02-19 07:22:35 IST LOG:  record with zero length at 0/16D89BB0
2014-02-19 07:22:35 IST LOG:  redo is not required
2014-02-19 07:22:35 IST LOG:  autovacuum launcher started
2014-02-19 07:22:35 IST LOG:  database system is ready to accept connections


2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection
2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection
2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection
2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection
2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection
2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection
2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection
2014-02-19 11:17:59 IST LOG:  unexpected EOF on client connection