Auto disconnection...

Hello,

I've been having problems with my JDBC connections to MySQL. It seems
that the DB will disconnect my connection after 8 hours of idle time.

This is a pain in the ass and I would like to turn this feature off in
the MySQL configuration file.

Just in case this matters, I'm using the latest and greatest everything
on linux/debian (64-bit). And the config file is located in
'/etc/mysql/my.cfg' (I'm assuming this is a standard cross-platform
file format).

Thanks,

Jeach!

Jeach! wrote:
> Hello,
>
> I've been having problems with my JDBC connections to MySQL. It seems
> that the DB will disconnect my connection after 8 hours of idle time.
>
> This is a pain in the ass and I would like to turn this feature off in
> the MySQL configuration file.

That'd be really nice if there were a way to do it. I haven't found one.

There are bugs at bugs.mysql.com, in which MySQL support staff recommend
that the solution is to code your Java app to catch an exception when
the connection has gone away, and reconnect as needed. :-(

Regards,
Bill K.

"Jeach!" <christian.jean@gmail.com> wrote:
>
> I've been having problems with my JDBC connections to MySQL. It seems
> that the DB will disconnect my connection after 8 hours of idle time.
>
> This is a pain in the ass and I would like to turn this feature off in
> the MySQL configuration file.

mysql> show variables like 'wait%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| wait_timeout | 28800 |
+---------------+-------+

mysql> select 8*60*60;
+---------+
| 8*60*60 |
+---------+
| 28800 |
+---------+


Not just a coincidence. So you cannot turn it off, but you can set
a very long timeout.


XL
--
Axel Schwenke, Senior Software Developer, MySQL AB

Online User Manual: http://dev.mysql.com/doc/refman/5.0/en/
MySQL User Forums: http://forums.mysql.com/

Alright the 'wait_timeout' will only set my problem at a future time,
but I should still expect to see it eventually. At least we know the
MySQL functionality works well

My problem seems to be more of a JDBC/implementation error, so I'll
switch over to another group.

Thanks for your help.

Jeach!