Wicket users,
We are still investigating, but it's seems to be related to using of
docker image with openjdk over alpine.
If you have similar situation: try to repack under different base
docker image with java.
Thanks,
Ilya
-
Orienteer(http://orienteer
Yes. Pretty sure.
But it might be something indirect: for example, during building of our
next docker image with the newer wicket, some openjdk/maven/libs newer
dependency was picked up as well.
That's something which we are evaluating.
Thanks,
Ilya
-
Or
Hi,
I don't see anything related in the changes from 8.5 to 8.6.1
https://github.com/apache/wicket/blob/wicket-8.x/CHANGELOG-8.x
Are you sure these OOMs didn't happen before?
Sven
On 16.01.20 22:52, Илья Нарыжный wrote:
Sven,
It was 8.5 - so not so far away.
Thanks,
Ilya
-
Sven,
It was 8.5 - so not so far away.
Thanks,
Ilya
-
Orienteer(http://orienteer.org) - open source Business Application Platform
On Thu, Jan 16, 2020 at 11:41 AM Sven Meier wrote:
>
> What was your previous version?
>
> Sven
>
> Am 16. Januar 2020 19
What was your previous version?
Sven
Am 16. Januar 2020 19:27:19 MEZ schrieb "Илья Нарыжный" :
>Hello,
>
>After upgrading to Wicket 8.6.1 we started seeing periodical OOMs in
>logs like below.
>I'm not 100% sure that it's due to Wicket, but we didn't change
>containers parameters and etc - so at
Hello,
After upgrading to Wicket 8.6.1 we started seeing periodical OOMs in
logs like below.
I'm not 100% sure that it's due to Wicket, but we didn't change
containers parameters and etc - so at least it's quite suspicious.
Our startup flags:
-XX:+PerfDisableSharedMem -Xmx4G -Xms4G -XX:MaxDirectMe
