Hi, I have a EJB which depends on a sar service, ejb and sar locate on same ear package file.

ejb deployment description as below:

<session>

         <ejb-name>DomainServiceBean</ejb-name>

         <jndi-name>DomainServiceBean</jndi-name>

         <depends>com.vitria:service=M3OServerApplicationPreconditionStartupService</depends>

         <invoker-bindings>

             <invoker>

                 <invoker-proxy-binding-name>vitria-cluster-invoker</invoker-proxy-binding-name>

             </invoker>

         </invoker-bindings>

         <clustered>true</clustered>

         <cluster-config>

             <home-load-balance-policy>org.jboss.ha.framework.interfaces.RoundRobin</home-load-balance-policy>

             <bean-load-balance-policy>org.jboss.ha.framework.interfaces.RoundRobin</bean-load-balance-policy>

         </cluster-config>

        <method-attributes>

        </method-attributes>

</session>

start jboss, after deploy done (the ejb and sar is visiable in jmx console), using a client to the ejb, while, the ejb call will be hang, in jboss thread dump, we can see the ejb call is hang in here:

"WorkerThread#9[10.101.7.125:39387]" prio=5 tid=3238 WAITING

    java.lang.Object.wait(Native Method)

    java.lang.Object.wait(Object.java:503)

    EDU.oswego.cs.dl.util.concurrent.Latch.acquire(Latch.java:64)

    org.jboss.ha.framework.server.HATarget.invocationsAllowed(HATarget.java:185)

    org.jboss.invocation.unified.server.UnifiedInvokerHA.invoke(UnifiedInvokerHA.java:138)

    org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866)

    org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)

    org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420)

    org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)

with debug jboss src code, I can see HATarget latch is instantiated, while the latch didn't be released (break point never enter). and from the debug code, there is no listener to listening STARTED notification.

BTW, the same package can work fine in no-cluster profiler.

my jboss version is 4.2.2

any