Just for the reference - I found what it was. The database was on the same box, but it was routed via an external IP address, and when the router glitched, the connection went down with it. Solved by using internal ip address (localhost would do, too, of course)
On Fri, Sep 24, 2010 at 9:01 AM, Thomas Mueller < [email protected]> wrote: > Hi, > > > Maybe, but who and why would close a localhost connection? > > Maybe the server was stopped, or the connection was closed > (java.sql.Connection.close was called). > > > Do you feel it's > > a hibernate problem? > > No, I think your application closed the connection or stopped the server. > > Regards, > Thomas > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<h2-database%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/h2-database?hl=en. > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
