delay-txn and is-modified conflict?

Question

WL 6.1 sp2, Solaris 2.8, JDK 1.3.1_02
I have a bmp ejb and session bean facade. All methods of both are Required.
I defined the is-modified tag and method, and set <delay-updates> to false.
I make a call to a session bean which looks up an entity bean and calls 3
setters:
session.call(){
//find entity
entity.getA()
entity.getB()
entity.getC()
And see ejbStore() being called 3 times. If I set <delay-updates> to true
(or remove it altogether), then I don't see ejbStore() being called at all.
What's going on? Just because I tell the container to call ejbLoad/Store
during the txn does not mean the container SHOULD call ejbStore() when it
doesn't need to, as stipulated by <is-modified>!
Gene

Answer 1

Sorry that the experience has been less than perfect.
The problem this time is that you've specified an is-modified-method in your descriptors that doesn't exist in your bean. Normally,
the ejb compliance checker would have caught it, but we're not doing the compliance check for EJB 2.0 CMP beans since they don't need
this method.
Regardless, the container should have given a reasonable error message. I'll make sure both of these get fixed.
-- Rob
Gene Chuang wrote:
Thanks Rob, turns out I am missing <persistence-use> tag in my descriptor. With this,
and a few other mods, I was about to run ejbc20 on my newly minted CMP. HOWEVER,
when I try to deploy the bean, I get another cryptic error (attached).
This is my first foray into Weblogic CMP (1.1/2.0), and I can honestly say my experience
wasn't pleasant. ejbc20 is just churning one bad error message after another, and
I can't possibly imagine I'm the first person to have seen these. I'm pretty exasperated
myself; I can't imagine how someone with less Weblogic experience can get a CMP
up and running. Perhaps these issues are addressed by 7.0 Workshop, so I guess I'll
give that a shot when we eventually upgrade to 7.x.
Gene
Rob Woollen <[email protected]> wrote:
It's a problem in your descriptors. Most likely you don't have a persistence-use
section, or it's incorrect. As you well know,
ejbc shouldn't be NPEing on this.
-- Rob
Gene Chuang wrote:
PS What would we need to run your beans as CMP 2.0 instead?Well, if you can interpret esteric error messages like the following whenI try to
run ejbc! ;-)
ERROR: Error from ejbc: java.lang.NullPointerException
at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseTypeIdentifier(CompositeMBeanDescriptor.java:1311)
at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:131)
at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:232)
at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:333)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:395)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
at weblogic.ejbc20.runBody(ejbc20.java:358)
at weblogic.utils.compiler.Tool.run(Tool.java:79)
at weblogic.ejbc.main(ejbc.java:21)
Gene
Rob Woollen <[email protected]> wrote:
Hi Gene.
I see the bug. I'm guessing that you're using the 'Exclusive' concurrency
option. (Either you've specified it explicitly or your weblogic-ejb-jar.xml
is
a 5.1 DTD).
The code does appear correct in the default, 'Database' concurrency.
There's a pretty easy work-around. Remove the <is-modified-method> from
your
weblogic-ejb-jar.xml and just change your ejbStore to be:
if (! isModified()) return;
// do db update
Otherwise, go ahead and open a support case so we can fix this one.
-- Rob
PS What would we need to run your beans as CMP 2.0 instead?
Gene Chuang wrote:
WL 6.1 sp2, Solaris 2.8, JDK 1.3.1_02
I have a bmp ejb and session bean facade. All methods of both are
Required.
I defined the is-modified tag and method, and set <delay-updates> tofalse.
I make a call to a session bean which looks up an entity bean and calls3
setters:
session.call(){
//find entity
entity.getA()
entity.getB()
entity.getC()
And see ejbStore() being called 3 times. If I set <delay-updates>
to
true
(or remove it altogether), then I don't see ejbStore() being called
at
all.
What's going on? Just because I tell the container to call ejbLoad/Store
during the txn does not mean the container SHOULD call ejbStore() whenit
doesn't need to, as stipulated by <is-modified>!
Gene--
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Gene.
<p>I see the bug. I'm guessing that you're using the 'Exclusive'
concurrency option. (Either you've specified it explicitly or your
weblogic-ejb-jar.xml is a 5.1 DTD).
<br>
<br>The code does appear correct in the default, 'Database' concurrency.
<p>There's a pretty easy work-around. Remove the <is-modified-method>
from your weblogic-ejb-jar.xml and just change your ejbStore to be:
<p>if (! isModified()) return;
<br>
<br>// do db update
<p>Otherwise, go ahead and open a support case so we can fix this one.
<p>-- Rob
<p>PS What would we need to run your beans as CMP 2.0 instead?
<br>
<p>Gene Chuang wrote:
<blockquote TYPE=CITE>WL 6.1 sp2, Solaris 2.8, JDK 1.3.1_02
<p>I have a bmp ejb and session bean facade. All methods of both
are Required.
<br>I defined the is-modified tag and method, and set <delay-updates>
to false.
<p>I make a call to a session bean which looks up an entity bean andcalls
3
<br>setters:
<p>session.call(){
<br> //find entity
<br> entity.getA()
<br> entity.getB()
<br> entity.getC()
<br>}
<p>And see ejbStore() being called 3 times. If I set <delay-updates>
to true
<br>(or remove it altogether), then I don't see ejbStore() being called
at all.
<p>What's going on? Just because I tell the container to call ejbLoad/Store
<br>during the txn does not mean the container SHOULD call ejbStore()when
it
<br>doesn't need to, as stipulated by <is-modified>!
<p>Gene</blockquote>
<pre>--
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com</pre>
</html>
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
It's a problem in your descriptors. Most likely you don't have a
persistence-use section, or it's incorrect. As you well know, ejbc
shouldn't be NPEing on this.
<p>-- Rob
<p>Gene Chuang wrote:
<blockquote TYPE=CITE>> PS What would we need to run your beans as CMP
2.0 instead?
<p>Well, if you can interpret esteric error messages like the following
when I try to
<br>run ejbc! ;-)
<p>ERROR: Error from ejbc: java.lang.NullPointerException
<br> at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseTypeIdentifier(CompositeMBeanDescriptor.java:1311)
<br> at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:131)
<br> at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:232)
<br> at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:333)
<br> at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:395)
<br> at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
<br> at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
<br> at weblogic.ejbc20.runBody(ejbc20.java:358)
<br> at weblogic.utils.compiler.Tool.run(Tool.java:79)
<br> at weblogic.ejbc.main(ejbc.java:21)
<p>Gene
<br>Rob Woollen <[email protected]> wrote:
<br>>
<br>>
<br>>Hi Gene.
<br>>
<br>>I see the bug. I'm guessing that you're using the 'Exclusive'
concurrency
<br>>option. (Either you've specified it explicitly or your weblogic-ejb-jar.xml
<br>>is
<br>>a 5.1 DTD).
<br>>
<br>>The code does appear correct in the default, 'Database' concurrency.
<br>>
<br>>There's a pretty easy work-around. Remove the <is-modified-method>
from
<br>>your
<br>>weblogic-ejb-jar.xml and just change your ejbStore to be:
<br>>
<br>>if (! isModified()) return;
<br>>
<br>>// do db update
<br>>
<br>>Otherwise, go ahead and open a support case so we can fix this one.
<br>>
<br>>-- Rob
<br>>
<br>>PS What would we need to run your beans as CMP 2.0 instead?
<br>>
<br>>
<br>>Gene Chuang wrote:
<br>>
<br>>> WL 6.1 sp2, Solaris 2.8, JDK 1.3.1_02
<br>>>
<br>>> I have a bmp ejb and session bean facade. All methods of both
are Required.
<br>>> I defined the is-modified tag and method, and set <delay-updates>
to false.
<br>>>
<br>>> I make a call to a session bean which looks up an entity bean and
calls
<br>>3
<br>>> setters:
<br>>>
<br>>> session.call(){
<br>>> //find entity
<br>>> entity.getA()
<br>>> entity.getB()
<br>>> entity.getC()
<br>>> }
<br>>>
<br>>> And see ejbStore() being called 3 times. If I set <delay-updates>
to
<br>>true
<br>>> (or remove it altogether), then I don't see ejbStore() being called
at
<br>>all.
<br>>>
<br>>> What's going on? Just because I tell the container to call
ejbLoad/Store
<br>>> during the txn does not mean the container SHOULD call ejbStore()
when
<br>>it
<br>>> doesn't need to, as stipulated by <is-modified>!
<br>>>
<br>>> Gene
<br>>
<br>>--
<br>>
<br>>----------------------------------------------------------------------
<br>>
<br>>AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
<br>>
<br>>by Michael Girdley, Rob Woollen, and Sandra Emerson
<br>>
<br>>http://learnWebLogic.com
<br>>
<br>>
<br>>
<br>>
<br>><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<br>><html>
<br>>Hi Gene.
<br>><p>I see the bug. I'm guessing that you're using the 'Exclusive'
<br>>concurrency option. (Either you've specified it explicitly or
your
<br>>weblogic-ejb-jar.xml is a 5.1 DTD).
<br>><br>
<br>><br>The code does appear correct in the default, 'Database' concurrency.
<br>><p>There's a pretty easy work-around. Remove the <is-modified-method>
<br>>from your weblogic-ejb-jar.xml and just change your ejbStore to be:
<br>><p>if (! isModified()) return;
<br>><br>
<br>><br>// do db update
<br>><p>Otherwise, go ahead and open a support case so we can fix this
one.
<br>><p>-- Rob
<br>><p>PS What would we need to run your beans as CMP 2.0 instead?
<br>><br>
<br>><p>Gene Chuang wrote:
<br>><blockquote TYPE=CITE>WL 6.1 sp2, Solaris 2.8, JDK 1.3.1_02
<br>><p>I have a bmp ejb and session bean facade. All methods
of both
<br>>are Required.
<br>><br>I defined the is-modified tag and method, and set <delay-updates>
<br>>to false.
<br>><p>I make a call to a session bean which looks up an entity bean
and calls
<br>>3
<br>><br>setters:
<br>><p>session.call(){
<br>><br> //find entity
<br>><br> entity.getA()
<br>><br> entity.getB()
<br>><br> entity.getC()
<br>><br>}
<br>><p>And see ejbStore() being called 3 times. If I set <delay-updates>
<br>>to true
<br>><br>(or remove it altogether), then I don't see ejbStore() being
called
<br>>at all.
<br>><p>What's going on? Just because I tell the container to
call ejbLoad/Store
<br>><br>during the txn does not mean the container SHOULD call ejbStore()
when
<br>>it
<br>><br>doesn't need to, as stipulated by <is-modified>!
<br>><p>Gene</blockquote>
<br>>
<br>><pre>--
<br>>
<br>>----------------------------------------------------------------------
<br>>
<br>>AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
<br>>
<br>>by Michael Girdley, Rob Woollen, and Sandra Emerson
<br>>
<br>>http://learnWebLogic.com"><a
href="http://learnWebLogic.com">http://learnWebLogic.com</a></A></pre>
<br>> </html>
<br>>
<br>></blockquote>
<pre>--
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
<A HREF="http://learnWebLogic.com">http://learnWebLogic.com</a></pre>
</html>
Name: trace
trace Type: unspecified type (application/octet-stream)
Encoding: base64