Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Help Needed for Root cause - Apache & Tomcat Services got stopped
82 views
Skip to first unread message
Sahil Verma
May 11, 2022, 3:20:03 PM5/11/22
to
Hi Team,
We are using both Apache & Tomcat environment. Kindly advise for the below error logs of Apache and Tomcat -
Apache - 2.4.25 version
Tomcat - 8.5.5 version
OS - Linux
Both Apache and Tomcat services got stopped. We have gone through the logs and found errors related to MaxRequestWorkers in Webserver Apache logs.
[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
140464737793792] AH00484: server reached MaxRequestWorkers setting,
consider raising the MaxRequestWorkers setting
And in Tomcat logs, found memory leakage warnings -
05-May-2022 11:28:48.058 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [thq] registered the JDBC driver [com.ibm.db2.jcc.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
05-May-2022 11:28:48.058 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [thq] registered the JDBC driver [com.teradata.jdbc.TeraDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
05-May-2022 11:28:48.063 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [thq] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
05-May-2022 11:28:48.064 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [thq] appears to have started a thread named [Thread-12] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
05-May-2022 11:28:48.065 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [thq] appears to have started a thread named [JMSCCThreadPoolMaster] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
05-May-2022 11:28:48.066 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [thq] created a ThreadLocal with key of type [com.ibm.msg.client.jms.internal.JmsTls$1] (value [com.ibm.msg.client.jms.internal.JmsTls$1@17a957aa]) and a value of type [com.ibm.msg.client.jms.internal.JmsTls] (value [com.ibm.msg.client.jms.internal.JmsTls@10456393]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Regards,
Sahil
We are using both Apache & Tomcat environment. Kindly advise for the below error logs of Apache and Tomcat -
Apache - 2.4.25 version
Tomcat - 8.5.5 version
OS - Linux
Both Apache and Tomcat services got stopped. We have gone through the logs and found errors related to MaxRequestWorkers in Webserver Apache logs.
[Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
140464737793792] AH00484: server reached MaxRequestWorkers setting,
consider raising the MaxRequestWorkers setting
And in Tomcat logs, found memory leakage warnings -
05-May-2022 11:28:48.058 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [thq] registered the JDBC driver [com.ibm.db2.jcc.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
05-May-2022 11:28:48.058 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [thq] registered the JDBC driver [com.teradata.jdbc.TeraDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
05-May-2022 11:28:48.063 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [thq] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
05-May-2022 11:28:48.064 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [thq] appears to have started a thread named [Thread-12] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
05-May-2022 11:28:48.065 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [thq] appears to have started a thread named [JMSCCThreadPoolMaster] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
05-May-2022 11:28:48.066 SEVERE [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [thq] created a ThreadLocal with key of type [com.ibm.msg.client.jms.internal.JmsTls$1] (value [com.ibm.msg.client.jms.internal.JmsTls$1@17a957aa]) and a value of type [com.ibm.msg.client.jms.internal.JmsTls] (value [com.ibm.msg.client.jms.internal.JmsTls@10456393]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
Regards,
Sahil
Thomas Hochstein
May 11, 2022, 5:30:02 PM5/11/22
to
Sahil Verma schrieb:
> Both Apache and Tomcat services got stopped. We have gone through the
> logs and found errors related to MaxRequestWorkers in Webserver Apache
> logs.
>
> [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
> 140464737793792] AH00484: server reached MaxRequestWorkers setting,
> consider raising the MaxRequestWorkers setting
Und, was passierte, nachdem ihr den Wert für MaxRequestWorkers erhöht
hattet?
> Both Apache and Tomcat services got stopped. We have gone through the
> logs and found errors related to MaxRequestWorkers in Webserver Apache
> logs.
>
> [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
> 140464737793792] AH00484: server reached MaxRequestWorkers setting,
> consider raising the MaxRequestWorkers setting
hattet?
Arno Welzel
May 15, 2022, 8:18:01 AM5/15/22
to
Sahil Verma:
> Hi Team,
>
> We are using both Apache & Tomcat environment. Kindly advise for the below error logs of Apache and Tomcat -
>
> Apache - 2.4.25 version
> Tomcat - 8.5.5 version
> OS - Linux
>
> Both Apache and Tomcat services got stopped. We have gone through the logs and found errors related to MaxRequestWorkers in Webserver Apache logs.
>
> [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
> 140464737793792] AH00484: server reached MaxRequestWorkers setting,
> consider raising the MaxRequestWorkers setting
And? Did you try that?
The setting can be found in /etc/apache2/mods-available/mpm_event.conf.
The default value depends on the distribution, but usally it is less
then 300, which might not be enough for sites which have to deal with
hundrets of requests per second.
> And in Tomcat logs, found memory leakage warnings -
>
> 05-May-2022 11:28:48.058 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [thq] registered the JDBC driver [com.ibm.db2.jcc.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
[...]
All this sounds like the server simply can not handle the load any
longer. Besides increasing limits in the configuration you should also
check if there is enough RAM available.
Using Netdata for real time monitoring may help you to understand the
condition of that machine:
<https://www.netdata.cloud>
You don't need to sign up there - you can also use that as an on-premise
service on your server:
<https://learn.netdata.cloud/docs/agent/packaging/installer/>
--
Arno Welzel
https://arnowelzel.de
> Hi Team,
>
> We are using both Apache & Tomcat environment. Kindly advise for the below error logs of Apache and Tomcat -
>
> Apache - 2.4.25 version
> Tomcat - 8.5.5 version
> OS - Linux
>
> Both Apache and Tomcat services got stopped. We have gone through the logs and found errors related to MaxRequestWorkers in Webserver Apache logs.
>
> [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid
> 140464737793792] AH00484: server reached MaxRequestWorkers setting,
> consider raising the MaxRequestWorkers setting
The setting can be found in /etc/apache2/mods-available/mpm_event.conf.
The default value depends on the distribution, but usally it is less
then 300, which might not be enough for sites which have to deal with
hundrets of requests per second.
> And in Tomcat logs, found memory leakage warnings -
>
> 05-May-2022 11:28:48.058 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [thq] registered the JDBC driver [com.ibm.db2.jcc.DB2Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
All this sounds like the server simply can not handle the load any
longer. Besides increasing limits in the configuration you should also
check if there is enough RAM available.
Using Netdata for real time monitoring may help you to understand the
condition of that machine:
<https://www.netdata.cloud>
You don't need to sign up there - you can also use that as an on-premise
service on your server:
<https://learn.netdata.cloud/docs/agent/packaging/installer/>
--
Arno Welzel
https://arnowelzel.de
0 new messages