Thanks guys. These are all helpful suggestions that I will look into.
Geoff
> On 16 May 2019, at 8:59 pm, Dakszewicz Diego <tno...@gmail.com> wrote:
>
> Hi Dmitry!
> Tapestry since 5.3 minify css and js on a fly. That's why your cpu hits
> 100%, at startup when tapestry warm up resources on first request and when
> your site has low traffic.
> A workaround to solve this problem is disable this feature.
> Take a look at your AppModule in
>
> @Contribute(ResourceMinimizer.class)
> public static void
> contributeMinimizers(MappedConfiguration<String, ResourceMinimizer>
> configuration) {}
>
> You can implement your own minimizer or just disable it. I prefer minify my
> resources at deploy time. It's recommended if you have to warm up a lot of
> apps hosted on the same server.
> Cheers,
> Diego
>
> El jue., 16 may. 2019 a las 4:59, Dmitry Gusev (<dmitry.gu...@gmail.com>)
> escribió:
>
>> Hi,
>>
>> I'd also try to collect thread dump when you see this happening to get an
>> idea where the CPU is wasted.
>>
>> On Thu, May 16, 2019 at 10:38 AM Mats Andersson <mats.anders...@ronsoft.se
>>>
>> wrote:
>>
>>> Do you have some scheduled services that could eat memory? I would
>>> suspect that the garbage collector is using most of that CPU. Monitor
>>> the GC and how memory is used over time. Maybe there is a mismatch
>>> between the memory configurations in Docker and the JVM.
>>>
>>> It seems like it is repeatable, that is good for troubleshooting at
>> least.
>>>
>>> Mats
>>>
>>>
>>> On 2019-05-16 03:33, JumpStart wrote:
>>>> Hi all,
>>>>
>>>> My app is working brilliantly under load, but after a quiet time it can
>>> be very slow to respond, leading our first user of the day to tap the
>> same
>>> thing multiple times, and the next thing you know is CPU hits 100% and is
>>> stuck there, and none of those requests returns a response. Nor do any
>> new
>>> requests return a response. Apache logs show that all the requests time
>> out
>>> after 60 secs, unanswered, and the health checkers start messaging the
>>> support staff.
>>>>
>>>> Has anyone else experienced this kind of thing?
>>>>
>>>> Perhaps it’s something to do with our infrastructure? We’re running
>>> Tapestry from an EAR in Wildfly in Docker in an AWS EC2 instance. Also in
>>> that EC2 instance is Apache HTTPD in Docker.
>>>>
>>>> Any thoughts, please! It’s a crazy problem.
>>>>
>>>> Cheers,
>>>>
>>>> Geoff
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>>>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>>>
>>> --
>>> ---------------------- Mats Andersson | Ronsoft AB | +46(0)73 368 79 82
>>>
>>>
>>
>> --
>> Dmitry Gusev
>>
>> AnjLab Team
>> http://anjlab.com
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
