StackOverflowError with DB

[Matthew Jones]

Sorry if this is a duplicate but it didn't look like my E-mailed version appeared.

We have a lift 2.4 application that uses an Oracle database backend. Now the DB has occasional hiccups and that is now causing strange behaviour in our application. We get a StackOverflowError exception which it claims is from at net.liftweb.db.ProtoDBVendor$class.newConnection(DB.scala:1169) (and then 1186) and this appears to be trying to get a new DB connection and failing (not surprisingly as the DB’s gone AWOL) and then immediately recursively calling newConnection again (which I guess is the cause of the StackOverflowError)

 Previously we have had the application lose its DB connection and then successfully reconnect afterwards and we certainly haven’t changed our Lift or scala versions in-between times and we don’t think we’ve changed anything relevant in the app. It could, of course be a different DB error as the recovery was after a scheduled i.e. controlled, DB shutdown and the failures were after unscheduled DB errors.

 I can’t find any other report of this behaviour so is this expected and is there anything we need to do to handle this properly?

 Thanks