Bean passivation not completed

Question

Environment: WLS 6.1 SP2 on NT
Hi,
I am loading 50 entities (EJB 2.0 BMP) and playing with WLS configuration
to force the container to passivate them.
I set max-beans-in-cache to 100, idle-timeout-seconds to 10 seconds
and concurrency-strategy to Database.
In addtion, I set the passivation-strategy to transaction to make sure
the container will passivate the bean after every transaction.
I ran my test to list the details of my 50 objects. 50 local entities
are indeed created, but none are passivated.
I would have expected the container to passivate them after 10 seconds
given my idle-timeout-seconds value. My passivation-strategy being set
to transaction, I would have expected the container to passivate them
straight away anyway.
If I change max-beans-in-cache to 30, the container passivates 20 entities
(activation count 50, passivation count 20, idle beans count 20, beans in
use count 30)
If I run it again the values change as expected to
activation count 70 (50+20), passivation count 40 (20+20), idle beans count
20, beans in use count 30.
My questions are:
Is idle-timeout-seconds working ?
Is passivation-strategy working ?
Is the console displaying the right information?
Could someone tell me what is the best practice for passivation policy?
It is not normal that my 50 entities will sit there for the whole day even
if there are not used.
They should be passivated shouldn't they?
Cheers
Arnaud

Answer 1

Arnaud wrote:
Environment: WLS 6.1 SP2 on NT
Hi,
I am loading 50 entities (EJB 2.0 BMP) and playing with WLS configuration
to force the container to passivate them.
I set max-beans-in-cache to 100, idle-timeout-seconds to 10 seconds
and concurrency-strategy to Database.
In addtion, I set the passivation-strategy to transaction to make sure
the container will passivate the bean after every transaction.
Passivation-strategy was deprecated in 6.0. It doesn't do anything in
6.0 or later. Actually it never really worked correctly even in 5.1.
idle-timeout-seconds is not used for entity bean passivation. That
parameter is only used for session beans.
I ran my test to list the details of my 50 objects. 50 local entities
are indeed created, but none are passivated.
I would have expected the container to passivate them after 10 seconds
given my idle-timeout-seconds value. My passivation-strategy being set
to transaction, I would have expected the container to passivate them
straight away anyway.
If I change max-beans-in-cache to 30, the container passivates 20 entities
(activation count 50, passivation count 20, idle beans count 20, beans in
use count 30)Right
If I run it again the values change as expected to
activation count 70 (50+20), passivation count 40 (20+20), idle beans count
20, beans in use count 30.
My questions are:
Is idle-timeout-seconds working ?
Is passivation-strategy working ?See above
Is the console displaying the right information?
Could someone tell me what is the best practice for passivation policy?
It is not normal that my 50 entities will sit there for the whole day even
if there are not used.
They should be passivated shouldn't they?
It depends on your usage. The better solution is in 7.0 where you can
configure application caches that will hold many different types of
EJBs. They're better able to handle mixed EJB loads.
-- Rob
Cheers
Arnaud