I disagree, IMHO tuned-updates set to false is a lot worse. With
turned-updates turned off, the primary keys of your entity beans get
updated and this basically causes a TABLE lock, at least when using
Oracle.(a read-lock is obtained on the index if another thread is
inserting into the same table). We spent 2 weeks debugging dead-lock
issues causes by this because we didn't know about the tuned-updates
flag and we almost ditched our JBoss effort and switched back to
Weblogic. So far, I think JBoss is a great product and I wouldn't want
a problem like this to turn away any other potential user of JBoss.
Bill
Tobias Frech wrote:
> Hi!
> I'd like to add, that this may break the updates for arrays. Don't ask
> me why, I just noticed this. No problems without tuned updates. Big
> problems with tuned updates turned on.
> Can someone confirm this ?
>
> Only in the case taht someone can confirm this I would suggest to
> think again about changing the default.
>
> Ciao, Tobias
>
> Bill Burke wrote:
>
>> Hey,
>>
>> I have a proposal to make the tuned-updates default of JAWS to be
>> true. I just spent two weeks debugging deadlock problems created by
>> not having tuned-updates set to "true".(FYI, without tuned-updates
>> primary keys get updated when an entity bean is stored in CMP and
>> this can cause deadlock on table indexes.). Of course, this was sort
>> of a RTFM problem, but its hard to absorb everything when you're
>> first using a bit of software.
>>
>> Thanks,
>> Bill
>>
>>
>>
>> _______________________________________________
>> Jboss-development mailing list
>> [EMAIL PROTECTED]
>> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
>
>
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
