Our app mixes EJB 2.1 CMP and straight SQL over JDBC. Reason for using SQL is that some queries involve some complicated table joins.
Unfortunately the SQL queries sometimes do not see the most uptodate data. This happens when - within the same transaction - the data is first written using CMP, and then queried using SQL. BTW, this only happens when we use EJBs to update data, not when we create new EJB instances. We are using commit option A. We have tried other commit options, did not make any difference. We are using JBoss 4.02 on Linux, Oracle 10. Is there any way to force an EJB update to go to the DB even before the transaction is ultimately committed, such that SQL queries over straight JDBC can see the data? Thanks Dirk View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921822#3921822 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921822 ------------------------------------------------------- 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
