If you issue is the memory, it is time to check the garbage collector you are
using, check that you are not using deprecated JVM flags, IIRC the garbage
collector used by JDK 11 is G1 and should perform better than default JDK8
defaults.
Regards
Ivan Fernandez Calvo
> El 11 jul 2022, a las
ooo... you may have nailed it there. I was definitely over the 75%. I
bumped up my overall system RAM, and then locked in the one site that isn't
used too much to a lower value. Its early, but so far no crashes.
Interesting that Java 8 never had an issue with this, but 11 clearly is.
If there are three different Apache Tomcat instances running three
different services on Java 11, the only explanation to make one crash that
comes to my mind is the resources of the machine, memory in particular.
The recommendation is to not use more than 75% of the memory of the host to
the
Sorry, should have mentioned that.
This is running on RHEL 7, and there are no indications of anything in the
logs. Just an abrupt stop. I could probably turn on some more verbose
logging though.
On Monday, July 11, 2022 at 10:40:08 AM UTC-4 slide wrote:
> Is there any crash log in either
Is there any crash log in either the apache or jenkins logs? I would look
for exception dumps in the logs, it might help narrow down where the issue
is occurring.
On Mon, Jul 11, 2022 at 5:35 AM Matt Wilson wrote:
> For a few years I've been running multiple (independent) Jenkins instances
> on
For a few years I've been running multiple (independent) Jenkins instances
on one server. Each server runs under its own apache instance.
SiteA
SiteB
SiteC
This has worked perfectly fine for a few years with no problems.
Last week I upgraded all three servers to 2.346.1. two of the three
