With the Java version of the frontend we planned to switch to PostgreSQL anyways, but for now, we use a homemade database abstraction layer for the frontend. Written by me a long, long time ago, when I didn't see the light. ;)

So, I'll make a Cronjob that tells Tomcat to reload the webapp, until I finish writing a PostgreSQL module for my dba-layer. This will do until we have the purely Java/RIFE-based software ready. Not the sexiest solution, I know, but I don't want to wait for a fix of the MySQL Connector/J.

What I would do is to write a RIFE scheduler task that goes over all the connections in your mysql datasource and issue a "SELECT 0" statement for each one. This task could then be run every hour of so. For details of how use the scheduler you'll probably have to look through some of our real-world app examples (Bamboo, ...) or ask someone here on the list to explain it to you.

Still, that bug should be fixed. Do you know anything else about what Connector/J does wrong? I won't hurt to send a bug report to [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> , which is the list for Connector/J. (Info at http://lists.mysql.com/java ) - You probably have the better understanding for this problem, but if not, I could send the bug report for you, just let me know.

I think that the main problem is (and that's the impression that I'm getting from their replies to these bug reports) that they don't think there's a problem. Basically, they are closing every opened connection automatically after 8 hours of inactivity. They then claim that it's up to the application or the connection pooling layer to check for the error condition that occurs and re-create the connection. This however means that those checks have to be done *everywhere* you use a connection (which is basically all the db- related code). I personally think that this is very invasive for something that I consider to be bad behavior on their behalf.

Simple question, which version of MySQL and Connector/J are you using? Upgrading them to the latest versions might help.

MySQL Connector/J is 3.1.12, which is the latest.

But MySQL itself is version 4.1.10a and it's probably a good idea to update that one anyway. Thanks for the idea.

--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com


_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users

Reply via email to