For those of you out there unfortunately enough to run DB2 I have the solution to this problem.
The solution to the problem as suggested in http://jira.jboss.com/jira/browse/JBAS-1891 (and parent) do not work with DB2. Setting fetch direction, concurrent read mode or fetch size will not let you load the JBoss messaging service with a large number of messages in a single queue. The proposed solution http://jboss.org/index.html?module=bb&op=viewtopic&t=46186 wouldn't work either since you still try to load all messages in a destination in a single sql. In DB2 memory for LOB records are freed only when the statement handle is dropped. This meens that you have to split the fetch sequence into several sqls where each sql only return a smaller amount of messages (In my case less than 1600 messages). However it is an obscure workaround for this problem. Setting the patch2=50 in your db2cli.ini solves these issues. By setting this you tell DB2 to free memory after each fetch. This file really is an ODBC config file. Go figure. Se http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/ad/c0007882.htm for further explanation on this and other obscure settings. I hope no one else have to use as much time as me on this issue. Oystein View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3909328#3909328 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3909328 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
