Hi Geert,
Geert Bevin wrote:
sadly this isn't the first time the issue was brought up and afaik
it's a problem with MySQL themselves and their view on connection
pooling. More info:
http://article.gmane.org/gmane.comp.java.rife.user/1434
We don't use MySQL in production and rely pretty much on PostgreSQL
and Oracle, where no problems appear wrt at all. RIFE doesn't do
anything that JDBC doesn't allow you. I really would like to find a
way to once and for all find a workaround for this issue. I vaguely
remember that Keith switched to PostgreSQL though.
Hmm, interesting.
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.
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.
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.
Regards,
Stefan :)
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
