We are experiencing unexplainable behavior while executing session beans inside 
our webservices.

Here is an example:
aBean.setA("something");
  | aBean.getA(); <- returns null!      
  | 

but once the transaction is over, the right information is populated in the DB!
Could it have to do with caching? Transaction isolation?

Thx 

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920773#3920773

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920773


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to