> -----Original Message-----
> From: Mark Thomas <ma...@apache.org>
> Sent: Friday, November 20, 2020 3:17 AM
> To: users@tomcat.apache.org
> Subject: Re: Weirdest Tomcat Behavior Ever?
>
> On 19/11/2020 16:03, Mark Thomas wrote:
> > On 19/11/2020 15:55, Eric Robinson wrote:
>
> <snip/>
>
> >> Unfortunately, the tomcats get restarted every night, so I'll have to watch
> closely for the error to happen today and I will do a thread dump as close as
> possible to the time of the error.
> >
> > Sounds good. Tx.
> >
> > My guess based on what I saw in the strace is that the thread will be
> > something database related. Which database and which database driver
> > (version number etc) is in use? In particular, are there any native
> > components to the JDBC driver?
>
> Morning Eric,
>
> I got the latest logs. Unfortunately, it looks like the file descriptor 
> information
> wasn't included in the strace output. I'm not seeing any calls to close a file
> descriptor.
>

My fault again. I'll make sure it gets in there next time.

> The thread dump looks good. I can map information from strace to the
> thread dump successfully.
>
> It looks like you are using MySQL from the data in the strace log. Is that
> correct? What I really need to know is which version of the MySQL JDBC
> driver (Connector/J) are you using? I'm trying to figure out where the root
> cause might be (or if it is a known issue fixed in a later release).
>

Yes, MySQL 5.6.41.

Now sure how to tell the JDBC version. I unzipped the tomcat-jdbc.jar file and 
inspected the MANIFEST file, which shows the following. Is that what you need?

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.7
Created-By: 1.6.0_45-b06 (Sun Microsystems Inc.)
Export-Package: org.apache.tomcat.jdbc.naming;uses:="javax.naming,org.
 apache.juli.logging,javax.naming.spi";version="7.0.72",org.apache.tom
 cat.jdbc.pool;uses:="org.apache.juli.logging,javax.sql,org.apache.tom
 cat.jdbc.pool.jmx,javax.management,javax.naming,javax.naming.spi,org.
 apache.tomcat.jdbc.pool.interceptor";version="7.0.72",org.apache.tomc
 at.jdbc.pool.interceptor;uses:="org.apache.tomcat.jdbc.pool,org.apach
 e.juli.logging,javax.management.openmbean,javax.management";version="
 7.0.72",org.apache.tomcat.jdbc.pool.jmx;uses:="org.apache.tomcat.jdbc
 .pool,org.apache.juli.logging,javax.management";version="7.0.72"
Bundle-Vendor: Apache Software Foundation
Bundle-Version: 7.0.72
Bundle-Name: Apache Tomcat JDBC Connection Pool
Bundle-ManifestVersion: 2
Bundle-SymbolicName: org.apache.tomcat.jdbc
Import-Package:  javax.management;version="0", javax.management.openmb
 ean;version="0", javax.naming;version="0", javax.naming.spi;version="
 0", javax.sql;version="0", org.apache.juli.logging;version="0"


> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org

Disclaimer : This email and any files transmitted with it are confidential and 
intended solely for intended recipients. If you are not the named addressee you 
should not disseminate, distribute, copy or alter this email. Any views or 
opinions presented in this email are solely those of the author and might not 
represent those of Physician Select Management. Warning: Although Physician 
Select Management has taken reasonable precautions to ensure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage arising from the use of this email or attachments.

Reply via email to