It happens ckokotsis is correct. Our problem was due to an incorrect ejbLoad() coding where we did not refresh state after the first time the EJB was loaded.
The reason this incorrect ejbLoad() caused our symptom is that when user of companyA signed in, JBoss went to cache/bean pool to get one existing instance. It happened that there was a companyEJB available but it was used as companyB before with companyB data. To change it to companyA, JBoss fired ejbActivate() which in our code correctly assigned it the primary key of companyA. Then JBoss fired ejbLoad() which in our code incorrectly refused to reload data (because it loaded data once when it was first used as companyB). Even though the key is companyA, the data is companyB! The reason why this code had been working on the Weblogic side was likely due to differences in EJB container implementation between the two application servers. It seems like Weblogic does not trust programmers refreshing the state in ejbLoad() that it resets all instance variables when it trys to reuse an EJB from cache/bean pool. Anyway, if we would have coded ejbLoad() correctly this symptom should have happened. I fixed this problem on April 1st by forcing ejbLoad() to reload data everytime. We tested it many times since and the symptom had disappeared. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875141#3875141 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875141 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
