Re: Tomcat problems every morning.

[Hemendra Rana]

The traces that I put yesterday did indeed show that it is the MySQL 
database driver that times out the connection. I have added 
autoReconnect=true to the URL. Lets see if that works. Following is the 
stack trace of the exception that I got:

java.sql.SQLException: Communication link failure: java.io.IOException
       at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:1606)
       at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:886)
       at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:945)
       at com.mysql.jdbc.Connection.execSQL(Connection.java:1809)
       at 
com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1458)
       .....

Thanks,
Hemendra
Paul (BRI) wrote:

My comment won't be that helpful - but I started out at the same place -
each morning I came in a got a call from staff saying the pages with
content pulled from the dbase was down. 

One thing I know, as others suggested, it has to do with the
JDBC/connection - in our case it happens when the network connection
between our linux box and our sql box os broken at some point - I think
the ISP does late night maintenance on the line (this is setup on an
office DSL line). We are still working to isolate the problem - but it
does seem to be JDBC related. I have tried simply pulling the cable on
the back of one box for a few seconds and the connection does die and
will not reconnect.
I plan to post back to the group when we get a better sense of the
problem - we are still fooling with it. In our case we are using MSSQL
with the MS JDBC driver. I thought I saw a post somewhere that said the
mySQL driver had a autoReconnect=true setting - I think I saw it on the
Apache site.
I hope you figure things out.

Paul

-----Original Message-----
From: Hollerman Geralyn M [mailto:[EMAIL PROTECTED] 
Sent: Sunday, June 01, 2003 9:07 PM
To: Tomcat Users List
Subject: Re: Tomcat problems every morning.

On Sun, 01 Jun 2003 18:14:05 -0700, Hemendra Rana wrote
 

Are you using mysql database on the backend too. Someone here
pointed out that by default, mysql driver times out after every 8 
hours. I still needs to verify whether that is the cause of my 
problem though. Will let you know of my finds.
   

Why, yes, I am. And I thought perhaps MySQL was the problem - but I was
told by some people using Oracle and PostgreSQL databases that they'd
seen the problem as well. I tried putting in some code to set the driver
time-out value, but evidently I didn't do it correctly, as the problem
persisted. I don't see the error with versions of Tomcat previous to
4.1.x, tho.
Lynn Hollerman.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]