Frank Morton wrote:

>>Use a transaction or turn off read ahead.  You are basically reading
>>ahead data, tossing the read-ahead information out, and then repeating.
>>
>>-dain
>>
> 
> Thanks for your response.
> 
> Sorry for my confusion, but I am. Your doc states to use <read-ahead>
> with the <strategy>on-load</strategy> for this exact case, but doesn't
> seem to make a difference at this point. You are saying strategy=none
> is the right thing to do?


No, it is just one of the two (good) options.

> I tried that, too, which doesn't appear to make
> any difference. Please clarify this. There is a lot of contradictory
> info on the web about this. I also tried setting <read-ahead> in
> standardjaws.xml to true and false, neither of which seemed to
> make any difference.


That won't work.  It shouldn't even boot.  Check the dtd.

> Seems no matter what I do, I get the
> same behavior, so I must be missing something.


Start a transaction, do your work, commit the transaction.


> While I'm irritating you, can you explain exactly how or refer me to
> someplace that explains exactly how to use a transaction to speed up
> reading Collections.


Depends where this code is.  If it is in an EJB, just set the method to 
Required.  If it is in a web app, lookup the user transaction in jndi, 
start it, and commit it.  Try the book at theserverside.com, or search 
google for "ejb user transaction".


> Thanks. I'm guessing I'm not the only one that needs to know about this.


You are about the 10th this week.  We need a FAQ, but I'm to busy to 
write it, so I'm not allowed to complain.

 

-dain



_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to