Hi.
Yes. This was caused by missing session close().
-------------------------- Original message --------------------------
From: Clinton Begin <[email protected]>
Subject: read large result set in Ibatis3
Date: Wednesday, February 24, 2010, 4:05:15 PM
Attachments: <none>
msgid: [email protected]
C> Ibatis shouldn't block that way. Can you confirm that it's not a table lock?
C> On 2010-02-24, Tomáš Procházka <[email protected]> wrote:
>>
>> I don't need expose JDBC. I only continuously read large table as queue and
>> process every item.
>>
>> I already used ResultHandler and ArrayBlockingQueue in handleResult(). If
>> the ArrayBlockingQueue is full reading is stoped until consuper thread
>> process all items.
>>
>> But when ArrayBlockingQueue block reading I can't call another iBatis
>> request. Ibatis are blocked during whole query processing with
>> ResultHandler? I don't use the same Db.getSession();
>>
----------------------- End of original message ----------------------
--
Tomas Prochazka
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
