[jboss-jira] [JBoss JIRA] Commented: (JBAS-1443) Add a flag to allow concurrent calls on stateful session beans

c c (JIRA) jira-events at lists.jboss.org
Tue Feb 20 11:16:36 EST 2007


    [ http://jira.jboss.com/jira/browse/JBAS-1443?page=comments#action_12353651 ] 
            
c c commented on JBAS-1443:
---------------------------

hold/queue requests cannot be used in all the problems

Take the case where there is recursive use of a function and the recursive function is called through the Remote Interface which again goes through JBoss Layer and so thus this hold/queue will not hold.

So there has to be way by which some beans have to be allowed to make concurrent calls

Bye for now

CSJakharia

> Add a flag to allow concurrent calls on stateful session beans
> --------------------------------------------------------------
>
>                 Key: JBAS-1443
>                 URL: http://jira.jboss.com/jira/browse/JBAS-1443
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: EJB2
>    Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
>            Reporter: Scott M Stark
>            Priority: Minor
>
> Weblogic has an allow-concurrent-calls proprietary tag for stateful session beans. The allow-concurrent-calls specifies whether a stateful session bean instance will allow concurrent method calls. The value of this element may be either "True" or "False". The default value is "False". When a stateful session bean instance is currently in a method call and another (concurrent) method call arrives on the server, the EJB specification requires that the server throw a RemoteException. By default, allow-concurrent-calls is false, and the EJB container will follow the EJB specification. When this value is set to true, the EJB container will block the concurrent method call and allow it to proceed when the previous call has completed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list