No problem... one of the biggest problems most users of WL 4.5.1/5.1 had
was with performance issues and deadlocking, both caused by WL pessimistic
entity locks.
Fortunately, this is a easy problem to solve by analyzing your txn-request
frequencies and adjusting your beans' txn attribrutes to fit your profile.
Furthermore, by moving forward with optimistic locking, which just about
every other vendor uses, WL 6.0 has made this issue moot.
Gene Chuang
Join Kiko.com!
-----Original Message-----
From: Yesudason Paulraj [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 22, 2001 1:22 PM
To: Gene Chuang
Subject: Re: How to set Container transactions
Hi,
Really it works very well than expected .Now it is fast.
Thanks
Regards
Yesudas
----- Original Message -----
From: "Gene Chuang" <[EMAIL PROTECTED]>
To: "'Yesudason Paulraj'" <[EMAIL PROTECTED]>
Sent: Monday, January 22, 2001 2:09 PM
Subject: RE: How to set Container transactions
> for all:
>
> <method-name>*</method-name>
>
>
> -----Original Message-----
> From: Yesudason Paulraj [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 22, 2001 11:06 AM
> To: Gene Chuang
> Subject: Re: How to set Container transactions
>
>
> Hi Gene chuang,
>
> "Set all your entity bean methods to 'Supports' "
>
> Is the above line is for all "Remote " Methods or Both Remote and Home
> Methods?
>
>
> Many Thanks
> Yesudason P
>
> ----- Original Message -----
> From: "Gene Chuang" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, January 22, 2001 1:07 PM
> Subject: RE: How to set Container transactions
>
>
> > If your session beans have heterogenous txn attribs (both read and
> > read/write), but the majority is read-only, then I would do this:
> >
> > Set all your entity bean methods to 'Supports'
> > Set all your session bean read-only methods to 'Not Required'
> > Set all your session bean write methods to 'Required'
> >
> > Accordigin to what you said,your read-only methods take a long time to
> > execute while your write methods are relatively quick; then with the
> above
> > settings, none of your entity beans will be locked 99% of the time, and
> > deadlocks will be minimized.
> >
> > Also, for the above to work, be sure you don't have read-only session
> > methods calling write session methods, or vice versa.
> >
> > Gene Chuang
> > Kiko.com
> >
> >
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Yesudason Paulraj
> > Sent: Sunday, January 21, 2001 1:20 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: How to set Container transactions
> >
> >
> > 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".
> >
>
===========================================================================
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".
