tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <>
Subject Re: server.xml (with mod_jk configuration) being rewritten
Date Fri, 16 May 2003 00:09:51 GMT

Again, that is somewhat pointless to do because Apache would still have to 
be restarted in order to pick up the changes to mod_jk.conf.  Just add the 
stuff in by hand for all the apps that you forsee using and then start 
Apache... even if they are not yet deployed to Tomcat.  Don't worry about 
the automatic writing of mod_jk.conf anymore.

I'm the wrong person to talk to if you want Tomcat to behave a different 
way.  Post to the dev list or post a bug to apache's bugzilla to get any 
attention to this issue.


At 07:54 PM 5/16/2003 -0300, you wrote:
>hi jake (or jacob ? :)
>The problem is that the tomcat is at the same machine of apache, our 
>production web-server, but maybe i'll change it, for now, i have alreday 
>told the intranet people that we will not depend over apache redirection, 
>although it's there, but will just see the new apps (on porto 80) when 
>apache restarted.
>mybe it could be useful to make tomcat rewrite the mod_conf by demand 
>(when a new app is deployed) or by a manager call. the same goes to 
>mod_jk. Is it possible to make mod_jk (coding of course) to watch for 
>mod_jk.conf change and reread it?
>Jacob Kjome wrote:
>>The ant "deploy" task definitely will cause Tomcat to rewrite the 
>>server.xml. This is to persist the information about the context so it 
>>can serve it up after a restart.  However, the server.xml rewrite 
>>shouldn't remove data (other than comments) from the server.xml.  What it 
>>does seem to do is write each element with every possible attribute, but 
>>that isn't a big deal.  If some of your non-commented elements in 
>>server.xml are being removed upon server.xml rewrite, then you should 
>>report this as a bug to .
>>BTW, using Apache with a context deployed via the ant manager "deploy" 
>>task kind of defeats the purpose of using Apache.  Usually, the idea is 
>>to let Apache serve static content to take the burden off of Tomcat so it 
>>can peacefully serve dynamic content.  However, since context's deployed 
>>via the ant manager "deploy" task are served directly from the .war file, 
>>there is no static content for Apache to serve since Apache requires the 
>>context to be in a directory, not in a .war file.
>>You might want to use the ant manager "install" task instead of the 
>>"deploy" task.  The server.xml will not be rewritten.  However, upon each 
>>restart of Tomcat, you will have to do the install again because it is 
>>not persisted across restarts.
>>At 08:25 PM 5/15/2003 -0300, you wrote:
>>>please, anyone could answer me? i'm without clues. I have to use 
>>>auto-conf of apache and remote deploy of tomcat. but remote-deploy 
>>>changes the server.xml, loosing the configuration of mod_jk (it rewrites 
>>>the server.xml), so the next time i startup apache and/or tomcat, it 
>>>will not get the configuration of mod_jk. Any clue???????????
>>>thanks in advance
>>>Emerson Cargnin wrote:
>>>>when I deploy a new app into tomcat, my server.xml (with mod_jk 
>>>>configuration) is being rewritten, so the next time I restart apache 
>>>>and Tomcat it does not take in account my configuration. I need to 
>>>>change the  server.xml in evert apache and tomcat restart? And the 
>>>>contexts created dnamically through deploy ant taks?
>>>>I need to solve this because feature  ( automatically deploy  4.1) was 
>>>>the reason to use auto-conf of apache-tomcat.
>>>Emerson Cargnin
>>>Analista de Sitemas
>>>Setor de Desenvolvimento de Sistemas - TRE-SC
>>>tel : (048) - 251-3700 - Ramal 3181
>>>To unsubscribe, e-mail:
>>>For additional commands, e-mail:
>Emerson Cargnin
>Analista de Sitemas
>Setor de Desenvolvimento de Sistemas - TRE-SC
>tel : (048) - 251-3700 - Ramal 3181
>To unsubscribe, e-mail:
>For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message