Hi Guys,
Because of some reasons , we are not immediately moving to WLS 6.
We have 5.1 , any idea how to manage these kind of problems in wls 5?
Hi kirk,
Can you throw some light on , how to implement in w-w conflict management?
Regards
Yesudason Paulraj
---------- Original Message ----------------------------------
From: Kirk Pepperdine <[EMAIL PROTECTED]>
Reply-To: A mailing list for Enterprise JavaBeans development
Date: Sun, 21 Jan 2001 05:14:16 -0800
>but then you have to manage w-w conflict management
>your self.
>
>Kirk
>----- Original Message -----
>From: "Avi Kivity" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Sunday, January 21, 2001 3:05 AM
>Subject: Re: How to set Container transactions
>
>
>> You've hit WebLogic's pessimistic locking, I believe. Accesses from
>multiple
>> clients or multiple transactions will block, and are therefore
>> deadlock-prone. You should use an application server that provides
>> optimistic locking. WebLogic 6.0.0 provides that.
>>
>> - Avi
>> --
>> And now for something completely different.
>>
>> > -----Original Message-----
>> > From: Yesudason Paulraj [mailto:[EMAIL PROTECTED]]
>> > Sent: Sunday, January 21, 2001 07:23
>> > To: [EMAIL PROTECTED]
>> > Subject: How to set Container transactions
>> >
>> >
>> > Dear friends,
>> > I am facing a problem related to the EJB Transactions in my project.
>> > Let me give a brief introduction about what I have and I am
>> > trying to do.
>> > we have 20 entity beans and an session bean. All the entity
>> > bean methods are wrapped within the session bean to provide
>> > meaningful business methods for the clients. I have 18
>> > methods in the session bean and out of 18 , 11 methods are
>> > only read operation ( Like retriving result from the DB for
>> > some queries). Now the problem is that , I have a very big DB
>> > and obviuosly it takes some time for the query.But the write
>> > operations work very fast( because creating 2-5 records in
>> > some tables).
>> >
>> > But I have set <trans-attribute> (Trasaction attribute) for
>> > all the methods in the session bean that "RequiresNew" and
>> > all the remote methods in the EntityBeans that "Required".
>> >
>> > Problem is , I am getting the primaryKeyLockedException
>> > frequently than expected. I am sure this is because of some
>> > problems in setting the transaction attribute for the Session
>> > bean methods.
>> >
>> > Questions are :
>> >
>> > What transactional attribute I have to set for the Entity
>> > EJB's remote methods?
>> >
>> > I am sure the write operations in the session bean definitely
>> > needs a new transaction.
>> > What sort of trasactional-attribute I have to specify in the
>> > Read methods (Query methods) in the session beans. Now as I
>> > have given "RequiresNew" for this methods also ,it locks the
>> > rows when it reads some data so many times I am getting the
>> > "PrimaryKeyLocked" exception.(I guess)
>> >
>> > I am using WLS5.1 on win2k.
>> > Hope I will get a confidence boosting answer.
>> >
>>
>>
>===========================================================================
>> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
>body
>> of the message "signoff EJB-INTEREST". For general help, send email to
>> [EMAIL PROTECTED] and include in the body of the message "help".
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
