Le 18/01/2013 17:19, David kerber a écrit :
On 1/18/2013 11:06 AM, Mark Thomas wrote:
On 18/01/2013 14:42, David kerber wrote:
On 1/18/2013 9:18 AM, Mark Thomas wrote:
On 18/01/2013 13:33, Alexandre Rubert wrote:
Hello,
I've more than 200app in my webapp directory with symbolic links
in some
images. If I activate allowLinking tomcat crash during startup
because
of out of memory. I'd like to disable automatic start for all
applications except manager. I tried by adding
deployOnStartup="false"
and autoDeploy="false" in my server.xml but with this options I can't
access to manager html.
Add an explicit Context for the manager in server.xml
Mark
So are you saying that this is one of the rare cases where
configuring a
context in server.xml is appropriate?
Yes. It is the only way to start a Context if autoDeploy and
deployOnStartup are disabled.
Thanks. I was wondering why it was left legal when it was so strongly
discouraged in most references and in this list.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
I don't know how to write my new context. Do I have to write it into my
host section where I set deployOnstartUp to false and autoDeploy to
false ?Do you have example ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
