[opencms-dev] Error 127 on DB access puts opencms *** OUT OF THE QUESTION ***

[Niklas Eklund]

Well, I don't know what went wrong, but you shouldn't have to restart 
Tomcat. It normally only requires reloading the opencms webapp.

For speed reasons an application sometimes has to cache stuff in memory, 
and when one manually change data in the database, the application still 
has it's old cached data in memory which could cause errors. When errors 
are detected some apps flush the caches for the involved objects for 
them to be reread, but that does not seem to be the case here.
But, if the installation is correct, ie the db user has all the 
necessary permissions the cache and db will never be out of sync 
(hopefully ;). Since that was not the case here, as you indicate in your 
first post, I think it seems a bit unfair to say that opencms is not for 
you since you've tried it on a misconfigured installation...

Regards,

  Niklas

Willem Grooters wrote:

> A week ago, I made a call for an explanation of an error occuring on my
> opencms installation (Error 127 on DB access) and found something I'm not at
> all pleased of.
> It turned out that although none of the tables had an error (checked and
> repaired when applicable), and the project did indeed no longer exist in the
> databse, the project kept showing up in opencms's projectlist and caused
> error 127 on databse access time after time.
> Stopping mysql did not solve the problem, this was part of the repair cycle,
> both the project and the error kept showing up.
> I also observered that, after I left opencms, a large number of database
> connections of opencms are left open - appearently in SLEEP state. This
> could perhaps lead to let this error reappear in a new session.
> Yesterday I had to reboot - so everything was restarted. Now, the situation
> is as it should be: the project does no longer show up, and the error did no
> longer return.
> 
> So now I have the impression that, if there's something wrong in the
> database, you have to restart Tomcat.
> 
> On my system, this behaviour is intolerable.
> 
> I won't say it makes it unusable completely, just for the kind of
> environment I intended to use it in. My guess is I can use openCMS but it
> should be on a more or less standalone machine, where restart of any
> component has no influence on other applications. This would mean I need to
> setup (and maintain) yet another machine, just for opencms? NO, THANK YOU.
> 
> I'll have to look for alternatives.
> 
> Willem Grooters
> e-mail: Willem at Grootersnet.nl
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev