Christopher,
Am 30.10.18 um 18:30 schrieb Christopher Schultz:
> Has anyone ever attacked one of your web applications? There are some
> fun ways to make an application use a huge amount of memory. Just
> because the applications themselves are behaving doesn't mean that all
> the users are behav
Am 30.10.18 um 13:13 schrieb logo:
> Mark,
>
>
>
>>> DEV (one webapp per tomcat)
>>>
>>> - Start-up time of "fat tomcats" multiplies, which leads to worsened
>>> availablity (e.g., our fattest tomcat contains 32 web services. It
>>> takes
>>> 4 minutes to start)
>>
>> You can configure Tomcat to l
ix anymore, applications that get regular feature updates etc.) are
isolated in their own tomcat instances. As soon as those become stable
we can move them to (one of) the fat tomcat(s).
Sounds like something I might get through :-)
Thanks and greetings,
tarek
Am 29.10.18 um 09:00 schrieb Ahmed, Tar
sorry, didn't send this to the list, but to mark's address,
t.
Am 29.10.18 um 10:18 schrieb Mark Thomas:
> On 29/10/18 08:00, Ahmed, Tarek wrote:
>
>> DEV (one webapp per tomcat)
>>
>> - Start-up time of "fat tomcats" multiplies, which leads to worse
Hi all,
TLDR? Do you deploy one web application per tomcat instance or several?
---
The long story:
I'd like to sound out your opinion regarding the number of web
applications deployed in one tomcat instance. The reason is, that at my
place of work the developers prefer one
Hi all,
I have a homegrown annotation @HealthCheck that aggregates @WebListener
like this:
@Target({TYPE})
@Retention(RUNTIME)
@WebListener
public @interface HealthCheck {
...
}
The idea is that classes annotated with this, being web listeners, are
automatically instantiated in a web applicatio
