It is a site specific scenario that those options can not be used.
Just feel having a app specific web.xml in conf dir would be reasoon,
context.xml allow specifying context/app name.
On 10/30/2012 3:45 PM, Pid wrote:
On 30/10/2012 13:29, Ted Smith wrote:
None of these alternatives is
only.
On 10/30/2012 8:22 AM, Daniel Mikusa wrote:
On Oct 29, 2012, at 7:28 PM, Ted Smith wrote:
Hello:
I have several web apps (war files) under single host and webapps dir.
I need to force HTTPS only for one of them and leave others unchanged.
My opinion is that the easiest fix would be to
Hello:
I have several web apps (war files) under single host and webapps dir.
I need to force HTTPS only for one of them and leave others unchanged.
config web.xml does not work as it applies to all apps.
I feel there must be a way to config this using server config instead of
modifying
a war f
/2012 10:46 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ted,
On 10/25/12 7:24 PM, Ted Smith wrote:
After upgrading to 7, deploying a new war file often results in
PermGen error, much more often than in 6.(with identical JVM
settings) I have tried all those JVM
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:123)
On 10/25/2012 7:49 PM, Jordan Michaels wrote:
Can you post the exact error message you are seeing and what your JVM
settings are when you get that error?
Warm Regards,
Jordan Michaels
On 10/25/2012 04:24 PM, Ted S
I am running tomcat 7.0.29, JDK 6.0.30
-XX:MaxPermSize=256m is one of the settings I tried but no help
and others settings that could be found googling.
it occurred in 6 as well, but suddently so often after upgrading to 7
I am curious how many on this list are having the similar issues,
i.e.,
Hello:
After upgrading to 7, deploying a new war file often results
in PermGen error, much more often than in 6.(with identical JVM settings)
I have tried all those JVM settings for perm memory but no help.
Is there any way to reduce the chance of PermGen errors?
such as how deployment should be
Thanks. Does it mean this bug can be "worked around" by
setting its init parameter "useAcceptRanges" to the value of "false"?
BTW
I found the following that is acked by Adobe
http://helpx.adobe.com/acrobat/kb/pdf-files-dont-display-some.html
On 9/24/2012 4:
Hello:
I just upgraded to Tomcat 7.0.29 from Tomcat 6 and encountered the exact
issue as described in
http://comments.gmane.org/gmane.comp.jakarta.tomcat.user/223299
Is there any workaround? I would be fine if there is an option to
disable the range handling function
so that Tomcat would al
