I assume you mean your DB connection settings and not the actual DB tables?
The latter one I can't help with.. but the former is because the the war deployment system is really designed for inital application deployment and not general maintenance. (unless it's a code only web-app with no custom properties, etc).
The problem is probably this. With Tomcat, when you delete or move the war file out of the webapp directory or redeploy the same war file, it will also delete the matching application directory.
This application directory contains the jForum configuration information, as well as user uploaded info like avatars and attachments. So, redeploying a "stock" war file will reset the configuration info to the initial state.
If you need to use war files to deploy code changes, etc.,
you should base that war file off the current state of the production webapp directory. This will ensure that all user uploaded content and configuration info is there. Plus this distro should be created either with the webapp shutdown to prevent users from uploading things or created in and deployed in a short time frame.
Of course, you can also drop the automatic war deployment and manually extract it to the webapps directory. This will update code and the like but preserve the config file and user info (because they don't exist in the war file).
E.g., when you initiallyif you deploy a jForum.war, a jForum subdirectory is created. Removing the jForum.w
[originally posted on jforum.net by monroe]
