I found the error description in the http://ora-01002.ora-code.com/

<code>
ORA-01002:
	fetch out of sequence
Cause:
	In a host language program, a FETCH call was issued out of sequence. A
successful parse-and-execute call must be issued before a fetch. This
can occur if an attempt was made to FETCH from an active set after all
records have been fetched. *This may be caused by fetching from a SELECT
FOR UPDATE cursor after a commit*. A PL/SQL cursor loop implicitly does
fetches and may also cause this error.
Action:	Parse and execute a SQL statement before attempting to fetch the
data.
</code>

I had seen the same problem. I've added the following line to make sure
that no transaction has been commited in middle of my sequence of work.
I hope this help you.

sess.connection().setAutoCommit(false);