That is kind of what I was expecting. The API Docs say that Execute returns
false if the execute is an Update or if the Query returns does not return a
result set. Not returning a results set is different than a query that returns
an empty result set. Can you explain what this SP is trying to do ?

I took a look at the 2.5.1 code and I see a subtile difference in how the
Query is executed. In 2.5.1 we were using executeQuery and not execute.

Can you try the following mod:
Orig Code:
m_Statement = conn.createStatement();
if (! m_Statement.execute(m_QueryParser.getSQLQuery()))

Yes the change (executeQuery) works for all the situations I tested.
Nearly all our stored procedures move data between a set of normalized tables of
permanent data and another set of denormalized tables with temporary data. A
whole bunch of overhead SQL is called as well, but no result sets are returned.
Separate queries select the temporary data.

Is the difference between execute and executeQuery going to break someone else's
use?