Reputation
Top tag
Next privilege 50 Rep.
Comment everywhere
Badges
11
Impact
~10k people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Jan
30
awarded  Popular Question
Jan
16
awarded  Popular Question
Aug
22
comment multiple webapps in tomcat — what is the optimal architecture?
It's all rather modest: 6 low traffic apps on our production server. On my development laptop I'm running 12 apps (allocating 4G for Tomcat) without problems.
Aug
18
comment multiple webapps in tomcat — what is the optimal architecture?
I've settled for option [2]. Meanwhile, we've switched to a decent server with lots of available RAM, so (so far) we haven't had any memory issues.
Sep
25
awarded  Supporter
Jul
19
awarded  Popular Question
Jan
31
comment java 7: should users be aware of changes in heap memory handling?
Thanks for your suggestions. I was aware of the limited memory available. Still, the same memory settings that work with JDK-1.6 produce heapspace errors when Tomcat is launched with JDK-1.7. That's why I'm wondering if memory requirements / handling has changed between these Java versions.
Jan
22
asked java 7: should users be aware of changes in heap memory handling?
Aug
22
awarded  Popular Question
Apr
20
awarded  Teacher
Apr
19
accepted adding a global URI prefix for Tomcat web apps
Apr
19
answered adding a global URI prefix for Tomcat web apps
Apr
17
answered Serving Tomcat under a sub-URI
Apr
17
awarded  Student
Apr
17
asked adding a global URI prefix for Tomcat web apps
Apr
12
accepted mod_proxy: pass path from original request to proxied app
Apr
11
comment mod_proxy: pass path from original request to proxied app
do you happen to know how the tomcat apps can be made available under an 'extra' folder? In (my understanding of) standard Tomcat terms, this would involve wrapping the contents of the ${catalina_home}/webapps/ in an intermediary 'apps' folder: ${catalina_home}/webapps/apps/ in which the different apps reside?
Apr
11
revised mod_proxy: pass path from original request to proxied app
edited title
Apr
11
comment mod_proxy: pass path from original request to proxied app
Ok, thanks for the clarification. That's probably the more sensible option: I had come up with a (perhaps clumsy) workaround: adding an additional proxy rule for requests containing '/webstart/' somewhere in the URL: ProxyPassMatch /webstart/ http://localhost:8082/. Though I'm aware that this is an ad-hoc approach which probably misses other situations that rely on the backend's interpretation of the request URL.
Apr
11
asked mod_proxy: pass path from original request to proxied app