]
Dan Hinojosa commented on JBSEAM-2264:
--------------------------------------
BTW, I already tried @Synchronized on this even though I really didn't need to. ;)
@Observer with PostSetVariable produces Concurrent exceptions in a
conversation scoped stateful bean
----------------------------------------------------------------------------------------------------
Key: JBSEAM-2264
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2264
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.GA
Environment: java 6_u03, jboss-4.2.1GA, jboss-seam-2.0.0.GA
Reporter: Dan Hinojosa
A method with an @Observer that listens to a postSetVariable event:
@Name("myModule")
@Scope(ScopeType.CONVERSATION)
@Stateful
public class MyModule implements ModuleLocal, ModuleRemote {
@Observer("org.jboss.seam.postSetVariable.foo")
public void process() {
/* Do something */
}
}
produces a stack trace:
[SeamPhaseListener] uncaught exception
javax.el.ELException: javax.ejb.EJBTransactionRolledbackException: no concurrent calls on
stateful bean 'jboss.j2ee:service=EJB3,name=MyModule' (EJB3 4.3.13)
According to 3.1.10. Concurrency model of the 2.0.0 documentation:
Finally, Seam enforces a single thread /per conversation per process/ model for the
conversation context by serializing concurrent requests in the same long-running
conversation context.
The two 'per' is kind of confusing, but it seems that since Seam is serializing
concurrent requests, this issue should not occur.
Will create demo app shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: