I am debugging my project and found that in my jboss log, the beans are loaded in this sequence:
14:30:01,015 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=EJB3-JPA2.jar,jar=EJB3-JPA2.jar,name=RecorderBean,service=EJB3 14:30:01,015 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=EJB3-JPA2.jar,jar=EJB3-JPA2.jar,name=RecorderBean,service=EJB3) to KernelDeployment of: EJB3-JPA2.jar
14:38:11,500 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=275-PRJ1.jar,jar=275-PRJ1.jar,name=WeatherDataBeanEJB,service=EJB3 14:38:11,500 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=275-PRJ1.jar,jar=275-PRJ1.jar,name=WeatherDataBeanEJB,service=EJB3) to KernelDeployment of: 275-PRJ1.jar
RecorderBean is a MDB while WeatherDataRecordBean is stateless session bean. MDB is loaded first and then Session Bean.
When checking sequence from the referenced workable version.
Session bean is loaded first, then MDB is loaded.
The MDB receives message from client and has some operation on entity. Also client is calling the session bean remote object and has operation on DataBase.
Running my project, always appear "WeatherDataBean not bound". At the same time, I could not read any message within the MDB onMessage methods. Seems that neither MDB nor session bean is loaded.
Which configuration file decides the sequence of installing/added bean in JBOSS 5.1? I am using queue-service.xml, persistence.xml under Meta-INF within ECLIPSe.