• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JDBC close() exception?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JDBC close() exception?


  • Subject: Re: JDBC close() exception?
  • From: Amiel Montecillo <email@hidden>
  • Date: Wed, 2 Sep 2009 10:46:07 +0800

Hello Bill,

Did you find a solution to this? I'm afraid I am also being killed by this.

Could it be a timeout problem and MySQL is closing the connection? There is a MySQL option "autoReconnect" but I don't feel comfortable with it.

Thanks,
Amiel

On Wed, Aug 19, 2009 at 12:54 AM, William Hatch <email@hidden> wrote:
Sorry for the repost, this exception is now randomly showing up, still causing problems eventually. What should I look for as possible causes to this?

Bill



On Aug 14, 2009, at 11:32 PM, William Hatch wrote:

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@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden



--
socket error: unable to connect to 127.0.0.1
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: JDBC close() exception?
      • From: Chuck Hill <email@hidden>
    • Re: JDBC close() exception?
      • From: William Hatch <email@hidden>
    • Re: JDBC close() exception?
      • From: Andrew Lindesay <email@hidden>
  • Prev by Date: Re: Snow Leopard Development and Deployment
  • Next by Date: Re: Nested WOSwitchComponents
  • Previous by thread: Re: WO Deployment [was:A WebObjects article on Appleinsider]
  • Next by thread: Re: JDBC close() exception?
  • Index(es):
    • Date
    • Thread