Nope, it appears t be the database is Corrupt.
Main Topics
Browse All TopicsThis software was working great,
I restared it because I thought it was having a problem.
it is running on a windows box, Windows version
It connects to our LDAP service running on another computer
Again it was working fine, and I rebooted it
so the config for LDAP is correct.
This is the line from the error log (the first line)
[org.jivesoftware.database
] Could not load JDBC driver class: org.hsqldb.jdbcDriver
There are many other errors but I think they stem from here.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Which exception is giving you this idea? If you post some more lines around the error, it might help - from the only line you have - the Driver class is not in the classpath
But if you already found out what had happened, post back here so the next person that see such an exception can think of the same thing
Once wildfire started up, the classpath in the JVM is set. And once it loads the jdbc driver, similarly it's in memory.
So either (1) the jdbc driver has been corrupted or (2) (IMHO more likely) the classpath was changed for something else installed on the box after wildfire was started up.
You can fix (1) by reinstalling the driver.
Fix (2) by analyzing the classpath and making sure that all the pieces of wildfire are still included.
-----Burton
Business Accounts
Answer for Membership
by: VenabiliPosted on 2008-09-15 at 12:23:05ID: 22481999
Rebooted?
What this sounds like is classpath issue -- during the reboot something had modified the classpath.
This is not an LDAP issue - the class just cannot be loaded when needed