4 Replies Latest reply on Jun 14, 2006 3:06 AM by ramesh s

    no concurrent calls on stateful beans exception

    mcdan Newbie

      Hi,

      we use JBoss 3.0.4 and I get the following EJBException: no concurrent calls on stateful beans, but this exception is thrown inside of JBoss. Ok, I know that concurrent calls on stateful beans are not allowed, but where is the bad code that raise this exception? Any hints to look at to find the bad code?

      Greetings

      Dan

      javax.ejb.EJBException: Application Error: no concurrent calls on stateful beans
       at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:249)
       at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:204)
       at org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:380)
       at org.jboss.ejb.Container.invoke(Container.java:712)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
       at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:382)
       at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
       at sun.rmi.transport.Transport$1.run(Transport.java:148)
       at java.security.AccessController.doPrivileged(Native Method)
       at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
       at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
       at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
       at java.lang.Thread.run(Thread.java:536)