Hmmm, probably
JDBC driver specific.
Is there no driver generated error code further down the stack trace ?
I /think/ I've had such a response when there was no data available (but not because of an empty result set).
Thus, I suspect a programming/configuration error (as opposed to an SQL error).
Check that you've a valid connection, that the statement is correctly setup and that you're executing the statement correctly.
If you can't see anything wrong, take a few steps back - simplify things (e.g. remove any bind variables) and get that working. Then re-introduce one thing at a time.