Cursor stream support through session bean

Question

we use toplink wrapped in a session bean to do database queries. we want the query results returned in a cursor stream way. since we make the session bean's transaction attribute as 'required'(kinda required by toplink), we ran into some problems:
* in websphere, the second time we do getNextResults(int) from the cursor stream, we get the error saying the ResultSet has been closed.
* in weblogic, similar problem existed with version 6, but now everything works fine with version 7.
i understand this is likely caused by the container managed transaction(commited or something). but any tricks to get this arround? or by design, there is a better way to handle this kind of cursor stream query in general?
thx.

Answer 1

You could try holding the transaction open until the client is finished with the cursor. You could do this through only using the cursor within the SessionBean's transactional method, or through begining a JTS transaction from the client of the SessionBean to wrap the cursor usage.
Switching to use TopLink's internal connection pooling may also be another workaround, but this may conflict with your app server/JTS usage.