If you are running with commit-option 'A', then the lock will occur in
jboss.
Bill
James Cook wrote:
> They only "lock" if the container implements there transaction isolation (not to
> be confused with the database's) in a pessimistic manner. It used to be that
> only WebLogic took this route, and I don't believe the jBoss folks are doing
> this.
>
> In the optimistic scheme, a bean with identical pks are instantiated to handle
> each concurrent client request.
>
> jim
>
> ----- Original Message -----
> From: "Bill Burke" <[EMAIL PROTECTED]>
> To: "JBoss-User" <[EMAIL PROTECTED]>
> Sent: Friday, March 09, 2001 11:43 AM
> Subject: [jBoss-User] "readonly" entity beans and transactions/deadlock
>
>
>> I'm running JBoss Final-2.0 on Linux, with Oracle and Container Managed
>> Persistence with JAWS.
>>
>> We have a bunch of global EntityBeans that are "readonly". By this I
>> mean they are never created or modified.
>>
>> EntityBeans are locked if they become a part of a transaction, right? I
>> want to avoid locking these global "readonly" EntityBeans. Can I do
>> this by declaring their transaction-attributes to be NotSupported?
>>
>> Thanks in advance,
>>
>> Bill
>>
>>
>>
>>
>> --
>> --------------------------------------------------------------
>> To subscribe: [EMAIL PROTECTED]
>> To unsubscribe: [EMAIL PROTECTED]
>>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
>
>
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
