Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Corruption - after restart, getting HTTP 500

 
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Rafael,

First off, let me say what a great product! Nice and tight (not a lot of overly-impregnated options to get hung up on for the users, etc.) and very good usability.

Ok, that said, we've encountered our first problem with a new install of v2.1.4 (using the "Automatic" method/default file base). It seems that somewhere during the use phase of the application, the native data became corrupted, and upon restarting it in Tomcat, we now get the following 500 error:

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Servlet.init() for servlet jforum threw exception
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
java.lang.Thread.run(Thread.java:534)


root cause

net.jforum.exceptions.DatabaseStartupException: Error while trying to start the database: java.sql.SQLException: The database is already in use by another process: org.hsqldb.NIOLockFile@16d777ab[file =/var/jakarta-tomcat-5.0.28/webapps/JForum-2.1.4/WEB-INF/config/database/hsqldb/jforum.lck.lck, exists=true, locked=false, valid=false, fl =null]: java.lang.Exception: checkHeartbeat(): lock file [/var/jakarta-tomcat-5.0.28/webapps/JForum-2.1.4/WEB-INF/config/database/hsqldb/jforum.lck.lck] is presumably locked by another process.
net.jforum.ForumStartup.startDatabase(ForumStartup.java:82)
net.jforum.JForum.init(JForum.java:95)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
java.lang.Thread.run(Thread.java:534)


note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs.


--------------------------------------------------------------------------------

Apache Tomcat/5.0.28


One idea that our Open Source Guru had was to reinstall JForum using MySql as the database - do you think this is a valid approach, or have you seen a similar situation that could help us debug this?

Best Regards,


-Spencer
[originally posted on jforum.net by Anonymous]
 
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yep, MySQL is a better shot. HSQLDB will be OK for hotsites, that just run for a few days and don't have tons of messages.

Anyway, this lock problem you can solve by deleting the lock file from WEB-INF/config/database/hsqldb.

And, btw, thanks a lot for the good feedback. Let me you any suggestions you may have.

Rafael
[originally posted on jforum.net by Rafael Steil]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic