connection timeout problem with j/connector

I'm not subscribed to this listserv - I'm just posting this email to
describe the bug I ran across and if the developer needs more
information, I'd be happy to answer them via an e-mail reply.

I developed an webapp on my development machine (OSX 10.2.6 w/ Tomcat
4.1.26 and the earlier mysql connector (latest 2.x). After deploying
it on the production server (RH 7.3, Apache 2.0.46, Tomcat 4.1.24 and
mod_jk2) , things ran just fine without an hitch, then sometime last
week I deployed a new version of the webapp that I developed which
included an upgrade to the j/connector 3.0.8 as well. I started
having timeout issues like if the site was not accessed overnight. I
figured it was the mysql 8hour timeout problem. After some
configuration fiddling with Apache's DBCP settings, I was still getting
the timeout issues.

The reason I'm not using autoReconnect=true is because I'm setting
defaultAutoCommit to false (which the documentation says will not work
with autoReconnect set to true. So I'm using Apache's DBCP pool to
manage the connections and remove stale connections that may be dropped
and stuff.

Well, after much testing on my development machine, which the webapp
worked just fine, even after resuming it after over 8hrs of inactivity.
So I deployed it to the production server and I still had the same
connection timeout errors being thrown.

After some dinking around, and all that, I decided to try downgrading
the j/connector to the latest 2.x binary, and now everything works just
fine. No problems w/ timeouts.

So in short, the 3.0.8 connector works fine on my OSX development
machine - but deploying the exact same webapp on my production server
will cause the issue to arise, and that this problem does not exist if
I'm using the 2.x release of j/connector. So I'm assuming it's some
obscure bug arising from the interaction that particular OS, JVM and
whatnot. Since I'd like to continue using future 3.x versions of
j/connector - I assume I'll need to give (you) developers more
information about how to track down the source of this problem. Let me
know what additional information you need, if you believe this issue
merits looking into.

-tim


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: connection timeout problem with j/connector

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim Kettering wrote:

> I'm not subscribed to this listserv - I'm just posting this email to
> describe the bug I ran across and if the developer needs more
> information, I'd be happy to answer them via an e-mail reply.
[snip]
> So in short, the 3.0.8 connector works fine on my OSX development
> machine - but deploying the exact same webapp on my production server
> will cause the issue to arise, and that this problem does not exist if
> I'm using the 2.x release of j/connector. So I'm assuming it's some
> obscure bug arising from the interaction that particular OS, JVM and
> whatnot. Since I'd like to continue using future 3.x versions of
> j/connector - I assume I'll need to give (you) developers more
> information about how to track down the source of this problem. Let me
> know what additional information you need, if you believe this issue
> merits looking into.
>
> -tim

How are you ensuring that connections are 'valid'? Are you using any of
the stale connection checks (on reserve or release), idle timeouts in
DBCP or via something custom in your code?

-Mark



- --
For technical support contracts, visit https://order.mysql.com/?ref=mmma

__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mark Matthews
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, SW Dev. Manager - J2EE/Windows
/_/ /_/\_, /___/\___\_\___/ Flossmoor (Chicago), IL USA
<___/ www.mysql.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/C4KztvXNTca6JD8RAiIWAKCnTtFBFxYtE1rPVn6GR/27BJAXQwCd Esef
uLt9OazxWKz9F2FTuba14m4=
=Y5ao
-----END PGP SIGNATURE-----


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org