• 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 in production?

 
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What are your thoughts on using HSQLDB in production. We recently had some people from our office take a class that was taught by someone from JBoss. This person flat out told them that they should NOT use HSQLDB in production. If I'm not mistaken doesn't JBoss use HSQLDB to store its JMS queue?

This seems to be a contradiction.

Frank
 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Don't use hsqldb in production.
We found it out the hard way when using JMS. We even had JBoss lock up entirely a few times. Now we're using oracle and everything runs smoothly.
 
Frank Malinowski
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Henk O:
Don't use hsqldb in production.
We found it out the hard way when using JMS. We even had JBoss lock up entirely a few times. Now we're using oracle and everything runs smoothly.



So you're using Oracle over the network for your JMS queue? My concern was that we would notice a performance hit if we had to write all of our JMS stuff over the network as opposed to in memory on the server as is the case when using HSQLDB.

We use Oracle for all of our normal application data.

Frank
 
Frank Malinowski
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Wiley Snyder:
HSQLDB

Is used to setup a demonstration or demo database that is setup within jboss quickly.

for sh*ts and giggles

If you want to use a production database you should consider finding one for jboss to use and that suits your particular projects needs.



I'm not talking about using it to store application data. I'm simply talking about the default setup of JBoss to use it to store the JMS messages.

Frank
 
Author
Posts: 67
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
One of my clients had serious issues with using the default HSQLDB for storing JMS messages. There were alll kinds of timeouts because HSQLDB isn't production-quality. It didn't seem to handle high volumes/concurrency very well. I would suggest using a better DBMS for storing JMS messages in production. Oracle, Sybase, SQL Server, Postgres, MySQL, <add-yours>, will all do nicely.

Tom
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic