Bugs item #910911, was opened at 2004-03-06 15:33
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=910911&group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Konstantin Sobolev (eprst)
Assigned to: Nobody/Anonymous (nobody)
Summary: EntitySynchronizationInterceptor bug(?)

Initial Comment:
Hi all,

I've encountered a problem with jboss 3.0.7, but
according to CVS
the same would be in latest release. I've got BMP
entity bean, standard
configuration. Two clients access the same bean
instance without
transaction context. I see the following in the log:

client1: EntitySynchronizationInterceptor.invoke,
ctx.isValid == false
client1: ejbLoad started
client1: ejbLoad finished, ctx.isValid == false
client2: EntitySynchronizationInterceptor.invoke,
ctx.isValid == false
client2: ejbLoad started
client1: ctx.isValid == true
client1: business method

Here my business method fails because ejbLoad in
another thread (client2) is modifiyng bean's internal
state. I thought that container should
serialize calls to the same bean instance, but I'm not
sure that
this is the only possible spec. interpretation. As for
me, I'd put ejbLoad call in
EntitySynchronizationInterceptor.invoke into
synchronized(ctx) block.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=910911&group_id=22866


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to