> Thanks All for the input. 
> 
> Sorry for the delay in response, had to leave early Friday. 
> Guess everyone is gearing for the Super Bowl today so will 
> catch replies on Monday. 
> 
> Let me clarify some issues:
> 
> 1. I am using jBoss2.0 FINAL (Windoze 2000 development - Red 
> Hat Linux Production )
> 2. The two 'LOCKING-WAITING entity beans' in question are 
> [Person] and [InternalAccount]. Person is a light-weight 
> entity bean for getting the name of an account holder (As I 
> learn more about EJB architecture I realize I probably don't 
> need the Person bean ) BTAIM InternalAccount uses Person to 
> get the name of the account holder. Person bean NEVER 
> accesses InternalAccount, so no dead lock possible there.
> 3. I checked with our resident Oracle guru to find out if any 
> person or account rows were locked while the 
> 'LOCKING-WAITING' was in progress. NONE were, and no other 
> rows for that matter. Oracle did reveal a single, non 
> blocking, pending transaction at time of 'LOCKING-WAITING'.
> 4. I am NOT using threaded clients. The problem however ONLY 
> occurs when two clients access the application simultaneously 
> - I guess equivalent to having a threaded client.
> 5. My design is such that I have a 'main' account, which 
> always gets accessed whenever there is some financial 
> transaction - The Bank as it were. ( I should improve my 
> design here I know ). So yes the 'main' [InternalAccount] 
> bean is being accessed frequently. This is the one ( 
> com.uni.account.AccountPK@0 ) on which the 'LOCKING-WAITING' 
> is occurring.
> 5. I checked the jBoss server.log and there are a number of 
> 'LOCKING-WAITING' messages scattered throughout the file 
> which 'caused no problem'. At some point though several 
> 'LOCKING-WAITING' messages are printed and jBoss waits.... 
> jBoss then  recovers when Oracle times out the transaction. 
> Things then go there merry way until the next 'LOCKING-WAITING'.
> 6. The problem is repeatable - run two clients 
> simultaneously, after 5 to 10 smooth running transactions, boom.
> 7. I have made all entity beans reentrant JUST for testing, 
> still the same thing.
> 8. My transaction settings seem correct, as I say with a 
> single client things work fine, and even for multiple client 
> for a while. Data is committed or rolled-back correctly.
> 
> Andrew
> 
> 
> > -----Original Message-----
> > From: marc fleury [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, January 27, 2001 2:33 PM
> > To: jBoss
> > Subject: RE: [jBoss-User] LOCKING-WAITING (TRANSACTION)
> > 
> > 
> > hey,
> > 
> > 
> > I would have to look at it.  Probably an exotic exception 
> > that goes through
> > the container and the instance remains in cache with a 
> > transaction... don't
> > know, can you really reproduce it or is it that you are just 
> > banging on the
> > cache with many clients (in which case it is normal and it 
> > would explain the
> > "recovery")
> > 
> > 
> > marc
> > 
> > 
> > |-----Original Message-----
> > |From: [EMAIL PROTECTED]
> > |[mailto:[EMAIL PROTECTED]]On Behalf Of Tobias Frech
> > |Sent: Friday, January 26, 2001 11:01 AM
> > |To: jBoss
> > |Subject: Re: [jBoss-User] LOCKING-WAITING (TRANSACTION)
> > |
> > |
> > |Hi Andrew!
> > |I know that problem. From time to time we see it too. But 
> > after an awful
> > |long time (in measures of CPU time) the container recovers 
> > somehow. To
> > |help to pin down that problem we could collect all the 
> > information about
> > |when this occurs.
> > |
> > |Which version of JBoss are you using ?
> > |
> > |Can you reproduce this error or does it happen "randomly" ?
> > |
> > |Do you know if [InternalAccount] has just been called, was 
> > called before
> > |or is not involved in any transaction at the time this 
> happens ? I am
> > |not sure, but the later could be the case for me.
> > |
> > |Cheers,
> > |Tobias
> > |
> > |"Nortje, Andrew" wrote:
> > |>
> > |> What does LOCKING-WAITING (TRANSACTION) mean?
> > |>
> > |> 1. Does it mean the row in the database is locked? OR
> > |> 2. Access to the particular entity bean is locked - the
> > |non-reentrant bean
> > |> thing.
> > |>
> > |> Some notes -
> > |> - I have no reentrant entity beans
> > |> - Application works fine for one customer buy transaction
> > |> - Application works fine, for a while, with multiple customer buy
> > |> transactions - then I get the LOCKING-WAITING 
> > (TRANSACTION) - forever
> > |> - Seems like a deadlock
> > |>
> > |> Any ideas?
> > |>
> > |> Thanks
> > |>
> > |> Andrew
> > |>
> > |> [InternalAccount] Transaction insert() called  
> > Transaction: ID 0 Debit 0
> > |> Credit 65 Amount 2.5 Parent 6192
> > |> [InternalAccount] SQL: Insert into TRANSC ( TRANSC_ID, 
> > PARENT_TRANSC_ID,
> > |> DEBIT_ACCOUNT_ID,  CREDIT_ACCOUNT_ID, TRANSC_DATE,
> > |EFFECTIVE_DATE, AMOUNT,
> > |> STATUS, DESCRIPTION, TRANSC_TYPE_ID ) values ( 6195, 6192, 0, 65,
> > |> to_date('2001-01-26 02:41:02','YYYY-MM-DD HH24:MI:SS'),
> > |to_date('2001-02-25
> > |> 02:41:02','YYYY-MM-DD HH24:MI:SS'), 2.5, 1, 'COMMISSION', 5 )
> > |> [InternalAccount]  Transaction: ID 6195 Debit 0 Credit 65 Amount
> > |2.5 Parent
> > |> 6192 Transaction amount = 2.5
> > |> [InternalAccount] Updating account balance
> > |> com.uni.account.InternalAccountBean@34cdfc
> > |> For entity with ID 0
> > |> Account ID 0
> > |> Balance = 856.2 +
> > |> 
> -2.5##############################################################
> > |> [Person] LOCKING-WAITING (TRANSACTION) for id
> > |> com.uni.entity.myaccount.PersonPK@4a7c ctx.hash 6146369
> > |> tx:TransactionImpl:XidImpl:[B@7fb9e1
> > |> [InternalAccount] LOCKING-WAITING (TRANSACTION) for id
> > |> com.uni.account.AccountPK@0 ctx.hash 4092026
> > |> tx:TransactionImpl:XidImpl:[B@49e87
> > |> [Person] LOCKING-WAITING (TRANSACTION) for id
> > |> com.uni.entity.myaccount.PersonPK@4a7c ctx.hash 6146369
> > |> tx:TransactionImpl:XidImpl:[B@43e93d
> > |>
> > |> --
> > |> --------------------------------------------------------------
> > |> To subscribe:        [EMAIL PROTECTED]
> > |> To unsubscribe:      [EMAIL PROTECTED]
> > |> List Help?:          [EMAIL PROTECTED]
> > |
> > |
> > |--
> > |--------------------------------------------------------------
> > |To subscribe:        [EMAIL PROTECTED]
> > |To unsubscribe:      [EMAIL PROTECTED]
> > |List Help?:          [EMAIL PROTECTED]
> > |
> > 
> > 
> > 
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > List Help?:          [EMAIL PROTECTED]
> > 
> 


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]

Reply via email to