Re: After OS update from RHEL 6.3 to 6.10 seeing 503 error

.x86_64 Thanks Satish From: Satish Chhatpar 02 Sent: Friday, July 31, 2020 1:49 AM To: Tomcat Users List Subject: Re: After OS update from RHEL 6.3 to 6.10 seeing 503 error Hi Chris, Thanks for replying. No updates/changes done to Tomcat. Yes with OS

Re: After OS update from RHEL 6.3 to 6.10 seeing 503 error

or open attachments unless you recognise the sender and know the content is safe. If suspicious, report via the Report Message/Phishing button. On Wed, Jul 29, 2020 at 4:41 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Satish, > > On 7/29/20 2:56 PM, Satish Ch

After OS update from RHEL 6.3 to 6.10 seeing 503 error

After OS update from RHEL 6.6 to 6.10, seeing 503 error. Need help to fix this. 503 Service Temporarily Unavailable Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Additionally

Re: No entries being written to catalina.out !!!

Try this 1. stop tomcat 2. take backup of all logs 3. deleted all logs 4. start tomcat Regards Satish Chhatpar From: Praveen KC Sent: Thursday, March 1, 2018 3:30:51 PM To: users@tomcat.apache.org Subject: No entries being written to catalina.ou

Re: Tomcat 8.5.23

Which operating system? Did you check the logs? Sent using OWA for iPhone From: Lawrence Lim Sent: Thursday, February 15, 2018 11:09:54 PM To: users@tomcat.apache.org Subject: Tomcat 8.5.23 Hi, I just installed tomcat 8.5.23. I am having problems deploying web

Which one is used by Default on Apache 2.4.6 ? MPM worker or MPM prefork

We have are using Apache 2.4.6 on Red Hat Enterprise Linux Server release 7.2 (Maipo) My objective is to find out the default values for maxrequestworkers, as we have not configured any specific value. and Also we have not configured any specific MPM, so My question is Which one is used by

Re: A fatal error has been detected by the Java Runtime Environment libjvm

Hi Vijay I have encountered same error for jre version 1.7.0_21. This is a known bug in Java and it has been fixed in JRE version 1.7.0_80. Sent using OWA for iPhone From: Vijay Kumar Sent: Tuesday, March 14, 2017 6:39:52 AM To: Tomcat Users List Subject: A fa

Re: Apache Tomcat/7.0.39 crashed with fatal error

: Tomcat Users List Subject: Re: Apache Tomcat/7.0.39 crashed with fatal error -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Satish, On 1/26/17 3:42 PM, Satish Chhatpar 02 wrote: > Thanks Chris. I appreciate your help. > > All 4 tomcats are on diff machines. One on each, with same tomcat

Re: Apache Tomcat/7.0.39 crashed with fatal error

, 2017 1:52:47 AM To: Tomcat Users List Subject: Re: Apache Tomcat/7.0.39 crashed with fatal error -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Satish, On 1/26/17 2:28 PM, Satish Chhatpar 02 wrote: > we are using Apache Tomcat/7.0.39 for our java application. I highly recommend an upgrade

Apache Tomcat/7.0.39 crashed with fatal error

Hi, we are using Apache Tomcat/7.0.39 for our java application. There are 4 tomcat instances using same tomcat version and java version. yesterday all 4 tomcats crashed with below error in hs_err_pid log file. This log file was created for all 4 tomcats. Its very peculiar behaviour that all 4