Hi Mark,
Thanks for the info - I think we will focus on migrating to the 8.5.x branch
first. If we experience the same issue on that branch I will restart our
investigation and might come back with additional debugging information to see
if we can identify the root cause.
Thanks for your
On 19/01/2018 14:35, Toom Andreas wrote:
> Hi Mark,
>
> Sorry for the late reply, it has been a couple of busy days.
>
> We are running our application on two nodes and we have seen the issue on
> both nodes. These machines are running quad core cpus. What we have usually
> seen is that the
Hi Rainer,
Thanks for your reply!
We did a restart of the application earlier this week and so far the cpu usage
is at normal levels. If/when the cpu usage goes up I will check with your
suggested parameters!
Best regards,
Andreas
-Original Message-
From: Rainer Jung
Hi Mark,
Sorry for the late reply, it has been a couple of busy days.
We are running our application on two nodes and we have seen the issue on both
nodes. These machines are running quad core cpus. What we have usually seen is
that the application jvm process is consuming 100% (basically one
Hi Greg,
Thanks for looking into this issue. Unfortunately I am 100% sure we are running
Tomcat 8.0.47 so the referenced patch/fix is already applied.
Best regards,
Andreas
-Original Message-
From: Greg Huber [mailto:gregh3...@gmail.com]
Sent: den 18 januari 2018 14:56
To: Tomcat
On 1/18/2018 7:45 AM, Rainer Jung wrote:
Just an addition to one of Mark's questions:
Am 17.01.2018 um 22:20 schrieb Mark Thomas:
Is it always the same threads generating the load or does it move
between threads?
Just in case Andreas is not aware: one can check with "top -H -p ".
Using -H
Following this thread, I run the same setup, apache/mod_jk/ tomcat. There
was a problem a while back where the cpu went to max for me, as my server
is slow and thread blocking more of a possibility.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58151
Although this was in version 8.0.23, are
Just an addition to one of Mark's questions:
Am 17.01.2018 um 22:20 schrieb Mark Thomas:
Is it always the same threads generating the load or does it move
between threads?
Just in case Andreas is not aware: one can check with "top -H -p ".
Using -H lets top show one line per thread instead
On 16/01/18 23:21, Mark Thomas wrote:
> On 16/01/18 09:21, Toom Andreas wrote:
>> Hi Mark,
>>
>> We pulled out a CPU Call Tree using JVisualVM instead of YourKit and I have
>> uploaded a screenshot of it here: https://imgur.com/a/mqYxn
>>
>> There is not much extra information compared to the
On 16/01/18 09:21, Toom Andreas wrote:
> Hi Mark,
>
> We pulled out a CPU Call Tree using JVisualVM instead of YourKit and I have
> uploaded a screenshot of it here: https://imgur.com/a/mqYxn
>
> There is not much extra information compared to the java thread dump in my
> initial post but it
Hi Mark,
We pulled out a CPU Call Tree using JVisualVM instead of YourKit and I have
uploaded a screenshot of it here: https://imgur.com/a/mqYxn
There is not much extra information compared to the java thread dump in my
initial post but it highlights in which code branch/method call most of
Hi.
On 12.01.2018 11:06, Toom Andreas wrote:
Hi André,
Thanks for your reply!
The Tomcat Connector connection_pool_timeout is specified in seconds and the
Tomcat ajp connector connectionTimeout is specified in milliseconds so both
sides have the same value. This is the recommended setting.
Hi Mark,
Thanks for the reply!
We will try got get some additional info and get back to you as soon as
possible!
Best regards,
Andreas
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: den 12 januari 2018 11:27
To: Tomcat Users List
On 12/01/18 06:58, Toom Andreas wrote:
> Hi,
>
> We are having an issue with an application running Apache Tomcat 8.0.47 using
> Oracle Jvm 1.8.0.151 on Linux (RHEL 7). The Tomcat process is consuming cpu
> at a constant high level even though there is a low amount of incoming
> traffic. When
Hi André,
Thanks for your reply!
The Tomcat Connector connection_pool_timeout is specified in seconds and the
Tomcat ajp connector connectionTimeout is specified in milliseconds so both
sides have the same value. This is the recommended setting. See quote from the
link that your provided:
On 12.01.2018 07:58, Toom Andreas wrote:
Hi,
We are having an issue with an application running Apache Tomcat 8.0.47 using
Oracle Jvm 1.8.0.151 on Linux (RHEL 7). The Tomcat process is consuming cpu at
a constant high level even though there is a low amount of incoming traffic.
When
Hi,
We are having an issue with an application running Apache Tomcat 8.0.47 using
Oracle Jvm 1.8.0.151 on Linux (RHEL 7). The Tomcat process is consuming cpu at
a constant high level even though there is a low amount of incoming traffic.
When inspecting the process health using JMX /JVisualVM
17 matches
Mail list logo