It can be something as dump as a badly passivated bean
Look at the jbossstandard.xml, find the line that says "LRU" replace it by
the class that says NoPassivation (find it under org.jboss.ejb.plugins I
think)
If not I believe the online doco (advanced configurations) describes that.
If all else fails, wake up the Italian dude and bang on his head till he
tells you how to configure his caches :)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Nortje, Andrew
|Sent: Tuesday, January 30, 2001 3:16 PM
|To: 'jBoss'
|Subject: RE: [jBoss-User] LOCKING-WAITING (TRANSACTION)
|
|
|Marc
|
|How do I set up "nopassivation" caches? I'll give it a go.
|
|BTW out of sheer exasperation I spent the day deploying my
|application under
|Weblogic 5.1, and it works just fine, no deadlocks.
|
|Now I know that doesn't necessarily mean jBoss has a bug, but it sure looks
|like it at this stage. I am relatively new to J2EE but I have checked my
|design and code pretty thoroughly. I am also following best practices, no
|reentrant beans, access entities via session, proper transaction
|control etc
|
|
|I still want / need to get my app working under jBoss so would appreciate
|any input.
|
|
|> -----Original Message-----
|> From: marc fleury [mailto:[EMAIL PROTECTED]]
|> Sent: Tuesday, January 30, 2001 12:33 PM
|> To: jBoss
|> Subject: RE: [jBoss-User] LOCKING-WAITING (TRANSACTION)
|>
|>
|> That sounds like a bug with passivation...
|>
|> Can you run exactly the same test with "nopassivation" caches.
|>
|> Simone can you do a load test (jbosstest) over night with the
|> passivation
|> caches?
|>
|> It was an old bug in the caches and I wonder if it is not a cousin
|>
|> marc
|>
|>
|> |-----Original Message-----
|> |From: [EMAIL PROTECTED]
|> |[mailto:[EMAIL PROTECTED]]On Behalf Of Nortje, Andrew
|> |Sent: Tuesday, January 30, 2001 4:36 AM
|> |To: 'jBoss'
|> |Subject: RE: [jBoss-User] LOCKING-WAITING (TRANSACTION)
|> |
|> |
|> |Sorry to bash this LOCKING-WAITING (TRANSACTION) thing.
|> (Nooooo I'm not
|> |worried about the message... I'm worried about why there
|> should be any
|> |waiting of any kind in the case I discovered today )
|> |
|> |I let my app run over night with clients making requests. As
|> before the app
|> |runs smooth for a while, then a few LOCKING-WAITING messages
|> scattered
|> |about, then a whole bunch of them in a row and so on...
|> |
|> |This morning:
|> |- Don't restart the app
|> |- No one else using the app or the database
|> |- App is idle i.e. all beans are idle (Lots of "Passivated
|> |overaged bean..."
|> |messages )
|> |- Database is idle, nobody else using it
|> |- Do select * from dba_dml_locks; on Oracle to check for
|> locked rows - none
|> |- I make a single client request - boom LOCKING-WAITING.
|> |
|> |Run exactly the same client request on its own( i.e. no
|> concurrent client
|> |request, so no LOCKING-WAITING messages ), a thousand times at server
|> |start-up and it will be fine.
|> |
|> |Is there a possiblity there may be bug in jBoss here somewhere.
|> |
|> |> -----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]
|> |
|>
|>
|>
|> --
|> --------------------------------------------------------------
|> 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]
