[
http://jira.magnolia-cms.com/browse/MAGNOLIA-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka reopened MAGNOLIA-821:
----------------------------------
Assignee: (was: Sameer Charles)
> two entries in server.xml with webapps as root cause lost data
> --------------------------------------------------------------
>
> Key: MAGNOLIA-821
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-821
> Project: Magnolia
> Issue Type: Bug
> Security Level: Public
> Components: build
> Affects Versions: 2.1.5
> Reporter: Boris Kraft
> Priority: Major
>
> Hi Everyone,
> we ran into a pretty little disaster with our magnolia installation, and I
> wanted to share that so nobody else has to replicate our experience.
> We run two Magnolia instances on a tomcat server, author and public
> instances, original tomcat 5.0.28 pre setup from the magnolia website.
> Everything worked fine, so after half the work was done we copied it from our
> dev server to the online server. Edited the server.xml a bit (hosts) and
> configured the apache to route certain subdomains to the tomcat. Everything
> up and running in no time, working fine. Now after further development on the
> websites we restarted the tomcat and afterwards everything in the repository
> is gone back to the moment we copied the files from dev to online server. I
> have traced the reason (and this may answer an earlier thread in this list?
> The only similar thing I could find in the archives..) We inadvertently
> copied (instead of replaced) the entry in the server.xml for the hosts,
> creating TWO entries with webapps as the root:
> <Host name="localhost" debug="0" appBase="webapps" ...>
> ...
> </Host>
> <Host name="cms.project.de" debug="0" appBase="webapps" ...>
> ...
> </Host>
> This diligently starts magnolia FOUR times, author and public once per host.
> This we did not notice in the logfile, the only warning really that this is
> the situation.
> This situation REPRODUCABLY causes all data to be lost on restart.
> Our investigation into jackrabbit sources and magnolia sources leads us to
> beliebe that when you stop the tomcat ALL Magnolia instances synchronize
> their repositories with the filesystem and the one filled with the new data
> writes contents to disk, then the other instance writes the old unchanged
> (original) state over the newer version.
> But this is our guess - fact is that this a minor misconfiguration on our
> side leads to this situation where everything SEEMS fine, until you restart
> the tomcat and lose all changes.
> Maybe this helps someone to avoid this scenario. :)
> Regards,
> Martin Friedel
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
