0 Replies Latest reply on Jun 4, 2008 7:15 PM by Victor Kirk

    Restricting number of invocations on EJB3 stateless session

    Victor Kirk Newbie

      Hi,

      I'm trying to limit the number of concurrent invocations on an EJB. I've done (I believe) the required config to do this (as described in ). However when I start a client that calls a lengthy (30+ secs) operation on the EJB then start a new client that calls another, quicker operation (2-3 secs), the second returns before the first has finished.

      Am I missing something? I'm using jboss-4.2.1

      jboss.xml, located in META-INF:

      <?xml version="1.0" encoding="UTF-8"?>
      <jboss>
       <enterprise-beans>
       <session>
       <ejb-name>TMTFetchDataServiceBean</ejb-name>
       <clustered>${com.serco.tcis.clustered:true}</clustered>
       <aop-domain-name>TMT Fetch Data Service</aop-domain-name>
       </session>
       </enterprise-beans>
      </jboss>



      tmt-fetch-aop.xml located in the root of my jar
      <aop>
       <domain name="TMT Fetch Data Service" extends="Stateless Bean" inheritBindings="true">
       <annotation expr="!class(@org.jboss.annotation.ejb.PoolClass)">@org.jboss.annotation.ejb.PoolClass (value=org.jboss.ejb3.StrictMaxPool.class, maxSize=1, timeout=9999999)
       </annotation>
       </domain>
      </aop>


      My EJB
      @Stateless
      @RemoteBinding( jndiBinding = "TransportFusion/TMTFetchDataService" )
      public class TMTFetchDataServiceBean implements TMTFetchDataServiceRemote {
       // ...
      }


      Thanks, Vic