tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M.H.G. Emmerig" <M.H.G.Emme...@DNB.NL>
Subject seperating content from the application
Date Wed, 21 Apr 2010 08:54:01 GMT


Our current configuration:

We are running tomcat 6.0.16 on windows 2003 enterprise.

We have a website which consists of an application part and a content part.
Both are in the same folder structure, eg.


the application comes as a war file and the content is placed via another

the folder structure is placed on a windows share.

Our current problem:

Whenever there is a problem with the share, the application crashes,
because tomcat can't find the application files anymore.
When the share comes back online, tomcat does not recover from the failure
and a restart is the only option.

Now I have the following questions:

I think separating the application from the content and placing the
application local to tomcat (basically on the same machine)
will solve the recovery issue.
I know placing everything local to the tomcat will be the best way and
gives the best performance, but at the moment that is not an option.

The questions

- Will placing the app local to the tomcat solve the recovery issue?
- Is there an easy way to seperate the app and the content, ie. some sort
of pathsetting ?

regards, Milko

Please consider the environment before printing this email.

De informatie verzonden met dit e-mailbericht is vertrouwelijk en
uitsluitend bestemd voor de geadresseerde. Indien u als niet-geadresseerde
dit bericht ontvangt, wordt u verzocht direct de afzender hierover te
informeren en het bericht te vernietigen. Gebruik van informatie door
onbevoegden, openbaarmaking of vermenigvuldiging  is verboden en kan leiden
tot aansprakelijkheid. De afzender is niet aansprakelijk in geval van
onjuiste overbrenging van het e-mailbericht en/of bij ontijdige ontvangst

The information transmitted is confidential and intended only for the
person or entity to whom or which it is addressed. If you are not the
intended recipient of this communication, please inform us immediately and
destroy this communication. Unauthorised use, disclosure or copying of
information is strictly prohibited and may entail liability. The sender
accepts no liability for improper transmission of this communication nor
for any delay in its receipt.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message