This might be unrelated, but we experience an issue where our apps would periodically freeze. From memory, LIMIT might have been a factor. It was solved by upgrading the mysql-connector-java jar from 3.1.8 to 5.1.16
By examining the state of the hung instance, we saw that the mysql connector class ReadAheadInputStream was just sitting with a constant socketRead.
So, it turned out that it is a problem in the mysql-connector-java-3.1.8.jar See: - http://bugs.mysql.com/bug.php?id=9515 - http://bugs.mysql.com/bug.php?id=31353
Those links describe the bug i.e. Hangs in ReadAheadInputStream.fill()
We upgraded from: mysql-connector-java-3.1.8.jar to mysql-connector-java-5.1.26.jar and the problem went away.
This may also have been the cause of an occasional freezing of our instances (which was happening infrequently and randomly). We had to force-quit them to get them going again.
Mark On 7 Mar 2014, at 18:20, Robin Smith wrote: I'm not sure about fetch plans, all i know at the moment is if i remove the LIMIT query i get millisecond performance on my query but if i include a LIMIT clause i get a full table scan.
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|