Surprisingly after about a year of faithful services, I noticed this evening that Subsonic wasn't starting anymore.
Luckily, I had a filesystem snapshot both before and after the crash, so I didn't lose anything. I kept the full logs and crashing database for troubleshooting. Details are below, but does anyone know what is causing this?
The most interesting part of the stack traces :
- Code: Select all
java.sql.SQLException: error in script file line: 67 out of memory
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
at org.hsqldb.jdbcDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:174)
at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:165)
at org.springframework.jdbc.datasource.AbstractDriverBasedDataSource.getConnectionFromDriver(AbstractDriverBasedDataSource.java:149)
at org.springframework.jdbc.datasource.AbstractDriverBasedDataSource.getConnection(AbstractDriverBasedDataSource.java:119)
at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:113)
at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:79)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:577)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:792)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:850)
at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:858)
at net.sourceforge.subsonic.dao.AbstractDao.update(AbstractDao.java:81)
at net.sourceforge.subsonic.dao.PlayerDao.deleteOldPlayers(PlayerDao.java:132)
at net.sourceforge.subsonic.service.PlayerService.init(PlayerService.java:56)
I've of course tried increasing -Xmx to 1G, but that didn't do anything -- it has no reason to, really, it was working fine before and I didn't even update the library between the working and crashing version of the database.
Not sure if that's related, but the line number in the stack trace references the following line in the db/subsonic.script file in the crashing database :
- Code: Select all
SET TABLE MEDIA_FILE INDEX'9196271 9744512 9744512 9210241 8958518 9617614 8852229 10007627 9642798 9558316 8891893 9168223 8865474 25025'