quick suggestion that may be way off the mark but such behavior would occur as a result of ejb instances not having their member values re-initialised when retrieved from the instance pool.
eg> 1. retrieve instance of company bean from pool and populate with company A data. 2. passivate and return bean to instance pool 3. retrieve instance of company bean (previously populated with company A data) and populate with company B data. if company B data partial, and subject to incorrect ejb coding, company bean B will have old values still populated from previous company A population. This will be seen after some time as bean instances within the pool are re-used. Why u wouldn't see this b4 under web logic don't know. If this is the fix let me know. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872037#3872037 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872037 ------------------------------------------------------- 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
