[
https://issues.jboss.org/browse/JBAS-9416?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-9416:
------------------------------------
That's required by spec. Session beans are meant to be thread safe. Here's what
the EJB3.1 spec says in section 4.3.14:
{quote}
The container serializes calls to each stateful and stateless session bean instance. Most
containers will
support many instances of a session bean executing concurrently; however, each instance
sees only a
serialized sequence of method calls.
....
By default, clients are allowed to make concurrent calls to a stateful session object and
the container is
required to serialize such concurrent requests. Note that the container never permits
multi-threaded
access to the actual stateful session bean instance.
{quote}
EJB3 SFSB performace problem: parallel calls are sequenced
----------------------------------------------------------
Key: JBAS-9416
URL:
https://issues.jboss.org/browse/JBAS-9416
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.Final
Reporter: Radim Hanus
Attachments: jboss-5.1_server.log, jboss-6.0_server.log, sfsbtest.zip,
thread_dump.txt
When a client looks up more SFSB of given type in dedicated threads and subsequently
calls business methods then such calls are always sequenced.
Works fine in jboss-5.1.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira