2 Replies Latest reply on Oct 14, 2003 5:39 PM by aubourg

    Interrupted while requesting permit!

      Hi,
      I'm getting the following exception when multiple threads call finder methods.
      Looking at the Jboss dev forum archives it looks as though this was an issue in version 3.0 and was addressed for later versions. I am encountering it now using version 3.2.1.

      Any insights?
      kv.


      javax.ejb.FinderException: Find failed: org.jboss.util.NestedSQLException: Interrupted while requ
      esting permit!; - nested throwable: (javax.resource.ResourceException: Interrupt
      ed while requesting permit!)
      at nl.imsystems.ejb.fwbiz.comp.util.dataaccess.EJBDataAccessBean.find(EJ
      BDataAccessBean.java:317)
      at sun.reflect.GeneratedMethodAccessor110.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(S
      tatelessSessionContainer.java:629)
      at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invo
      ke(CachedConnectionInterceptor.java:186)
      at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInte
      rceptor.java:84)
      at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxI
      nterceptorBMT.java:144)
      at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:6
      2)
      at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(Stat
      elessSessionInstanceInterceptor.java:72)
      at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.
      java:117)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
      at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFacto
      ryFinderInterceptor.java:122)
      at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessi
      onContainer.java:322)
      at org.jboss.ejb.Container.invoke(Container.java:674)
      at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
      nDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)

      at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.jav
      a:83)
      at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.
      java:46)
      at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:4
      5)
      at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessi
      onInterceptor.java:100)
      at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
      at $Proxy155.find(Unknown Source)
      at nl.imsystems.util.security.ClientLoginDataAccess.find(ClientLoginData
      Access.java:159)
      at nl.imsystems.util.db.CacheingPageBuffer.fetchPages(CacheingPageBuffer
      .java:124)

        • 1. Re: Interrupted while requesting permit!

          Ok an update on this.
          The problem only occurs when any CMP methods are marked as read-only in jboss.xml.

          It'd be nice to know if this can be avoided by some config tweaking.
          I started marking my getter and finder methods as read-only so as to avoid some deadlock conditions that were arising.
          This did the trick except I started getting the above exception which happened when threads were concurrently calling finder methods that returned large (>7k rows) results.
          I have now had to overcome the deadlock by using instance per tx container config but at some cost in performance.

          kv.

          • 2. Re: Interrupted while requesting permit!
            aubourg

            Hi,

            I got the same problem, I removed all the read-only attributes, and it's still there.
            It happens when jboss is in heavy load.

            Eric