John, The top two processes are:

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
19360 tomcat    20   0 3302144  42560  18944 R 99.9  0.5  46:02.37 java
19363 tomcat    20   0 3302144  42560  18944 R 98.4  0.5  45:48.50 VM Thread

I tried kill -3 on both of them, plus the java process ID I see from a "ps"
command, several seconds apart.  The only logs created are these, and they
are still all empty after the kill -3:
-rw-r--r--   1 tomcat tomcat    0 Jul  1 10:22 catalina.2020-07-01.log
-rw-r--r--   1 tomcat tomcat    0 Jul  1 10:22 host-manager.2020-07-01.log
-rw-r--r--   1 tomcat tomcat    0 Jul  1 10:22 localhost.2020-07-01.log
-rw-r--r--   1 tomcat tomcat    0 Jul  1 10:22 manager.2020-07-01.log

Any other ideas?

On Wed, Jul 1, 2020 at 12:09 PM <john.e.gr...@wellsfargo.com.invalid> wrote:

> Sean,
>
> > -----Original Message-----
> > From: Sean Neeley <sean.nee...@producepro.com>
> > Sent: Wednesday, July 01, 2020 11:15 AM
> > To: users@tomcat.apache.org
> > Subject: Having trouble with tomcat 7 installation on RHEL 7.8 power pc
> >
> > I just installed tomcat 7 on a Red Hat Enterprise Linux Server 7.8,
> power pc
> > system.  As soon as the service starts, the java process uses 100% cpu.
> > Logs get created in /var/log/tomcat, but they all have size 0 bytes.  I
> have not
> > modified the standard configuration (tomcat.conf, server.xml, etc).  The
> > tomcat packages that are installed are:
> >
> > tomcat-7.0.76-12.el7_8.noarch
> > tomcat-jsp-2.2-api-7.0.76-12.el7_8.noarch
> > tomcat-el-2.2-api-7.0.76-12.el7_8.noarch
> > tomcat-lib-7.0.76-12.el7_8.noarch
> > tomcat-servlet-3.0-api-7.0.76-12.el7_8.noarch
> >
> > Are there any tricks I can use to troubleshoot what is going wrong?
> > Without any logs being created, it seems impossible to determine the
> > problem.  Thanks for helping.
> >
> > Sean
>
> Use kill -3 to take several thread dumps about 5-10 seconds apart.  They
> will probably end up in catalina.out.
>
> You can also use top -H to see what individual threads are using CPU.
>
>

Reply via email to