> If you look at doGet() and follow the code you should be able to figure
out what you need to change to get things working in 8.5.x.
Thanks Mark, that did the trick, serveResource calls getRelativePath(request,
true) now where we were overriding getRelativePath(request)
Chris, the Filter idea
getRelativePath is never called and the browser gets a 404 error for
"my-site.css".
Anyone know what I need to change to restore the behavior as it was in Tomcat
6? I'm afraid I inherited this code so it's hard to say why it was done this
way.
trying to solve
the original technique.
--
Daryl Stultz
Principal Software Developer
_
OpenTempo, Inc
http://www.opentempo.com<http://www.opentempo.com/>
mailto:daryl.stu...@opentempo.com<mailto:daryl.stu...@opentempo.com>
hange our process a bit by turning on auto deploy and moving
the temporary directory into the webapps directory. That seems to be working
but I'm wondering if anyone has seen this problem and what we might be doing
wrong.
Thanks.
--
Daryl Stultz
Principal Soft
> As per the docs[1], this only works for a previously-deployed
> application. Deploying a new application requires additional parameters.
It's not super clear in the docs, the section "Deploy a previously deployed
webapp" is the first item under the header "Deploy A New Application from a
Loc
5.29) - Manager App
HOW-TO<https://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html#Deploy_a_Directory_or_WAR_by_URL>
tomcat.apache.org
If you have Tomcat configured to support multiple virtual hosts (websites) you
would need to configure a Manager for each. There are three ways to use th
of
> improvements since 2.2.2. Since you can't upgrade, would you consider
> switching to using mod_jk, which is available
> independently?
I switched to mod_jk-1.2.23 and I am pleased to say the 503 errors have gone
away! Thanks for the suggestion.
--
Daryl Stultz
er
> switching to using mod_jk, which is available independently? The
> configuration is a bit more involved, but you may get better results.
Thanks Chris, I'll look into it.
--
Daryl Stultz
_
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:da...@6degrees.com
of the user hitting the
"stop" button.
Is there a preferred alternative to connecting Apache and Tomcat? Or is
mod_proxy the best?
Thanks for the help.
P.S. I know the system is old, and you might be inclined to tell me to
upgrade but I don't have that option at t
ceful restart. So the system is stable though not behaving the
way I think it should. Not sure which part made the difference. I haven't
gotten to trying worker MPM yet. I tried dropping ttl to 300 with no
apparent difference in behavior.
Thanks for your help.
--
Daryl Stultz
_
Odd, though, the original poster switched
from worker to prefork as a workaround and I'm considering the opposite, so
probably not the solution for me. Comments?
This is starting to look more like an Apache issue, maybe I should move to
that list...
--
Daryl Stultz
__
e an Apache issue, maybe I should move to
that list...
--
Daryl Stultz
_
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:da...@6degrees.com
in the mod_proxy documentation and an
> additional connectionTimeout for Tomcat.
>
This is the part where expert advice comes in. I don't have any idea what
"reasonable timeouts" are and the docs don't give a decent way to calculate
it.
Thanks.
--
Daryl Stultz
_
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:da...@6degrees.com
ul restart of Apache after 300
connections. Can anyone shed some light on this or point me to some other
resource for help?
Thanks.
--
Daryl Stultz
_
6 Degrees Software and Consulting, Inc.
http://www.6degrees.com
mailto:da...@6degrees.com
14 matches
Mail list logo
