• 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
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

HSQLDB Log Problem

 
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 again,

I've noticed some odd behaviour with JForum's HSQLDB log file. This is with version 2.1.4, running on Tomcat. I realize that the conditions that this bug is happening under are a bit unusual, but I'm hoping that if it is a bug, it is fixable :?

I'm running JForum on a development machine, which has Tomcat being restarted frequently, and over time the HSQLDB log file ballons to an alarming size in a short period of time (> 4 megabytes in one case). When the log file approaches this size, it seems that JForum will not start up anymore because it's taking too long to parse this file.

The problem seems to be, as time progresses, the INSERT INTO JFORUM_SESSIONS and DELETE FROM JFORUM_SESSIONS statements start getting repeated for single log ins. By this I mean, the same exact line will be repeated in the log multiple times (in some cases, this seems to be hundreds of repetitions, if not more).

This behaviour can be repeated easily by doing the following:
On a machine running JForum + HSQLDB log in as any user using Firefox, then log in as the same user under Internet Explorer (this simulates having the user logging in multiple times using different computers, which is what is happening on our test machine). Then, shut down and restart Tomcat, and repeat the above. Do this a few times while watching the contents of the jforum.log file under the hsqldb folder, and you will hopefully notice what I'm talking about.

Thank you for your time,
Colin
[originally posted on jforum.net by Colin Walsh]
 
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
Nice one Marc!

Rafael
[originally posted on jforum.net by Rafael Steil]
 
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
Colin,

It looks like a known hsqldb bug to me. I have had a similar problem with hsldb 1.7.3 for an other application. I have now uploaded the newest hsqldb version 1.8 rc9.

You can get it from

https://jforum.dev.java.net/source/browse/jforum/WEB-INF/lib/

Delete the file hsqldb-1.7.3.jar and restart your forum.

Hope this fixes your problem.
[originally posted on jforum.net by marc]
 
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
Hi Marc,

This seems to have done the trick!

Thanks for the rapid response

-Colin
[originally posted on jforum.net by Colin Walsh]
 
We've gotta get close enough to that helmet to pull the choke on it's engine and flood his mind! Or, we could just read this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic