CMP EJB lifecycle questions

Question

Specs say, "RuntimeException thrown from a create method of the bean class results
in transition to a "does not exist" state and the container must not invoke any
method on the instance after a Runtimeexception has been caught"
When and how does weblogic ultimately dispose off that bean? Does it hog up an
"active bean" from the pool meanwhile ? Does it cause a "leak" ?
Can we turn off the stack trace for application exceptions re-thrown by the container?
If the container doesn't maintain a pool for beans (max_beans_in_cache=0), then
is the number of instances that can be active unlimited or limited only by memory
available ? (in short can I turn cache off?)
are the objects returned by Finder methods activated by the weblogic container
which commit strategy is used by weblogic (from spec --> optionA optionB or optionC
or another one )?

Answer 1

Chetan Desai wrote:
Specs say, "RuntimeException thrown from a create method of the bean class results
in transition to a "does not exist" state and the container must not invoke any
method on the instance after a Runtimeexception has been caught"Yes
>
When and how does weblogic ultimately dispose off that bean?It becomes garbage and will be collected by gc.
Does it hog up an
"active bean" from the pool meanwhile ?No
Does it cause a "leak" ?
No
>
Can we turn off the stack trace for application exceptions re-thrown by the container?
The container logs system exceptions. It does not log application exceptions.
>
If the container doesn't maintain a pool for beans (max_beans_in_cache=0), thenmax-beans-in-pool equal to 0 or max-beans-in-cache = 0?
>
is the number of instances that can be active unlimited or limited only by memory
available ? (in short can I turn cache off?)Are you trying to turn max-beans-in-cache off? I don't understand the question or what
you're trying to achieve?
>
are the objects returned by Finder methods activated by the weblogic container
By default, CMP beans will prefetch the associated data. You can disable this by turning
finders-load-beans to false, but this is usually a bad idea.
>
which commit strategy is used by weblogic (from spec --> optionA optionB or optionC
or another one )?All 3 are possible. I'd suggest that you take a look at the documentation for the
Database and Exclusive concurrency options.
There are also Read-Only entity beans.
-- Rob
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
[att1.html]