Dain Sundstrom wrote:
> danch wrote:
>
>> Dain Sundstrom wrote:
>>
>>> Frank Morton wrote:>
>>>
>>>> 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.
>>
>>
>>
>>
>> ? standardjaws.xml is just ignored in jboss3, i'n'it?
>>
>
>
> Ya, didn't read to close.
>
> Change standardjbosscmp-jdbc.xml instead.
>
> -dain
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
In that file, I find <fk-constraint>false</fk-constraint>. Is there a
reason for that to be false as default?
And since this one is there:
<read-ahead>
<strategy>on-load</strategy>
<page-size>1000</page-size>
<eager-load-group>*</eager-load-group>
</read-ahead>
<list-cache-max>1000</list-cache-max>
, shouldn't most uses of CMPs be tuned OK (when using the same
transaction!)?
What does <list-cache-max>, and <time-out>300</time-out> mean?
Marius K
Boostcom.no
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
