I have a generated
EJB 3.0 QL query
string, that is timing out.
At 5 minutes
JBoss aborted the call with the following :
This is the query that ultimately did me in. I think when the last line is a 'he%' it finishes quickly.
Is there a better way to phrase the EJB QL? (I'm definitely not a under-the-covers SQL expert)
Am I just lucky the over-normalized design didn't splat earlier? (Simpler queries, and fetching has been super fast.)
Is there some way to ask the EJB framework to abort earlier or more cleanly?
Any other advice welcome.
Note: addressUsages is an implementation artifact of a named N-to-M relationship.
The object model is
highly normalized. The queries up to this point have been ok.
entity code snippits:
Addendum: this also caused a
mysqld CPU runaway in JBoss 4.2.2
Edit: added 3.0 clarification
[ August 27, 2008: Message edited by: Bill Shirley ]