I have this problem, too. If the MySQL server is restarted, glassfish/ejb/jpa
gets mightily confused. Not ok in a production system. Is there a way to
configure the DataSource and/or connection pool so that it reconnects when
possible? It's ok to throw exceptions and rollback while MySql is down, but
when it comes up again, glassfish should work again without needing a
restart. Is this possible?
--
[Message sent by forum member 'tmpsa']
View Post: http://forums.java.net/node/838249