| Author |
CMP Locking order.
|
|
| Makoto Shibata 2004-01-28, 2:33 pm |
| Hi.
WebLogic8.1 can control locking order for CMPs.
like
<lock-order>1</lock-order>
in weblogic-cmp-jar.xml.
Can WebSphere control locking order ?
Any solution for deadlock.?
<order-database-operations>True</order-database-operations>
<enable-batch-operations>True</enable-batch-operations>
select for update
<use-select-for-update>True</use-select-for-update>
Isolation level. WAS can this.
<isolation-level>TransactionReadCommittedForUpdate</isolation-level>
Locking order by bean.
<lock-order>1</lock-order>
---
Makoto Shibata
| |
| Wayne Beaton 2004-01-29, 12:34 am |
| I'm assuming that you're using WebSphere Application Server 5.0.
I think that "Access Intents" are what you are looking for. These are used
to indicate what kind of locking you want on EJB calls.
They're documented in the InfoCenter.
Wayne
--
Wayne Beaton
http://www.rokc.ca/wayne
"I believe that the world needs more Canada" - Bono
"Makoto Shibata" <ugya@hotmail.com> wrote in message
news:bv9u77$4kpo$1@news.boulder.ibm.com...quote:
> Hi.
>
> WebLogic8.1 can control locking order for CMPs.
> like
> <lock-order>1</lock-order>
> in weblogic-cmp-jar.xml.
>
> Can WebSphere control locking order ?
> Any solution for deadlock.?
>
> <order-database-operations>True</order-database-operations>
>
> <enable-batch-operations>True</enable-batch-operations>
>
> select for update
> <use-select-for-update>True</use-select-for-update>
>
> Isolation level. WAS can this.
> <isolation-level>TransactionReadCommittedForUpdate</isolation-level>
>
> Locking order by bean.
> <lock-order>1</lock-order>
>
> ---
> Makoto Shibata
>
| |
| Makoto Shibata 2004-02-01, 5:33 pm |
| WebLogic controls locking order only cuscade delete situation...
Sorry this is fake function...
http://edocs.beasys.com/wls/docs81/...ar.html#1113798
#Function
#Use this flag to specify the database locking order of an entity bean
#when a transaction involves multiple beans and exclusive concurrency.
#The bean with lowest number is locked first.
#
#This flag should only be used to prevent a deadlock situation and,
currently,
#only applies when a transaction performs cascade deletes.
#This flag is only used for cascade delete currently.
"Wayne Beaton" <waynebeaton99@yahoo.com> wrote in message
news:bvb48r$44fk$1@news.boulder.ibm.com...quote:
> I'm assuming that you're using WebSphere Application Server 5.0.
>
> I think that "Access Intents" are what you are looking for. These are used
> to indicate what kind of locking you want on EJB calls.
>
> They're documented in the InfoCenter.
>
> Wayne
> --
> Wayne Beaton
> http://www.rokc.ca/wayne
>
> "I believe that the world needs more Canada" - Bono
> "Makoto Shibata" <ugya@hotmail.com> wrote in message
> news:bv9u77$4kpo$1@news.boulder.ibm.com...
>
>
|
|
|
|