new deployment box, cloned from existing box, now seeing this
exception on every request:
INFO Exceptions - Database Exception occured: Connection.close() has
already been called. Invalid operation in this state.at
sun.reflect.GeneratedConstructorAccessor83.newInstance(Unknown Source)
at
sun
.reflect
.DelegatingConstructorAccessorImpl
.newInstance(DelegatingConstructorAccessorImpl.java:45) at
java.lang.reflect.Constructor.newInstance(Constructor.java:532) at
com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at
com.mysql.jdbc.Util.getInstance(Util.java:381) at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:985) at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:957) at
com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927) at
com.mysql.jdbc.ConnectionImpl.getMutex(ConnectionImpl.java:3015) at
com.mysql.jdbc.ConnectionImpl.rollback(ConnectionImpl.java:4526) at
com
.webobjects
.jdbcadaptor.JDBCContext.rollbackTransaction(JDBCContext.java:488) at
com
.webobjects
.jdbcadaptor.JDBCChannel._evaluateExpression(JDBCChannel.java:340) at
com.webobjects.jdbcadaptor.JDBCCh
any ideas on what system or configuration option could be causing
this? I don't see it on the much busier production server, but after
a while, this appears to be killing the app. And then pingdom and
insanity begin to kick in...
Thanks.
Bill
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
