Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Hibernate JIRA by Sven Henckel, 2 years ago
You can't operate on a closed connection!!!
via hibernate.org by Unknown author, 2 years ago
via Hibernate JIRA by Sven Henckel, 1 year ago
You can't operate on a closed connection!!!
via incubator-groovy-users by Christian Paulsen, 4 months ago
You can't operate on a closed ResultSet!!!
via Stack Overflow by Unknown author, 2 years ago
An attempt by a client to checkout a Connection has timed out.
java.sql.SQLException: You can't operate on a closed connection!!! at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:68) at com.mchange.v2.c3p0.impl.NewProxyConnection.getAutoCommit(NewProxyConnection.java:815) at org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:132) at org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:100) at de.company.product.tools.DDLManager.main(DDLManager.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78)Caused by: java.lang.NullPointerException at com.mchange.v2.c3p0.impl.NewProxyConnection.getAutoCommit(NewProxyConnection.java:809) ... 8 more