I am getting below error when deploying our enterprise application's ear on clustered JBoss-5.1.0.GA AS. Our ear consists of one web application and several EJB
(2.x) applications. We are using Spring for instantiating EJB beans and other POJOs and then injecting them into required places.
After analyzing below stack trace I found that before EJB beans gets bound to their JNDI names, Spring context loading starts wherein these EJB beans are looked up through their respective JNDI names and there it fails as EJB beans are yet not bound!
The same ear works fine on a non-clustered JBoss-5.1.0.GA AS. There, observing its console I have found that, it deploys EJB in 3 steps: (1) Installing, (2) Deploying, and (3) Binding to their JNDI name and then the Spring context loading starts so there it is able to successfully lookup EJBs using their respective JNDI names, as shown in below stack trace which I have copied from the console output of when deploying same ear (without clustering changes) on same but non-clustered JBoss-5.1.0.GA AS:
I have gone through JBoss-5.1.0.GA AS release notes, gone through JBoss
Messaging 1.4 User Guide, also searched JBoss Forums and googled a lot but still didn't got solution to it.
Could anyone please help me out in this issue? Thanks in advance for any help.