Cindy,
On Oct 6, 2011, at 3:05 PM, Cindy Harper wrote:
But can any of you add to my knowledge base here, and tell me:
- is it possible to correct this problem easily in the AT code?
For me, the answer to this is no because I'm not very good at Java. If you're
good at Java or know someone
Hi Cindy,
I getting deja vu from this...we had a similar problem over a year ago. What
happened to us is that our IST dept (who run a mysql service) made some
changes to their load balancer and pooling configuration on their servers.
You might be running into a similar problem. The solution a
Cindy-
I think connectTimeout is used for making the initial connection to the
database. But the error you describe sounds more like the initial connection
succeeds, but then there is a timeout afterwards. I think the socketTimeout
parameter is what would control the timeout during an
Hi - I tried socketTimeout (I don't believe it's set in the SessionFactory
code, but it may be in the hibernate config), and then got a recordlock
error after 5 minutes:
java.lang.NullPointerException
at
