Is there a setting in WebLogic 7.0 that will cause database updates to be written to the buffer pool before the transaction is committed so that other threads/transactions can do a dirty/uncommitted read of the uncommitted data? The system basics are Java/WebLogic front end, connecting to a legacy mainframe that houses a DB2 database. The problem is that the front end updates a table before starting a CICS transaction on the mainframe. Once inside the transaction in CICS a COBOL program tries to do an uncommitted read of that table and gets a row not found. At the end of the web transaction a tx.commit is executed and then the data can be read by any application. If anyone has any ideas that would be great.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
WebLogic 7.0 and Entity Beans
- Thread starter JDawg012
- Start date
Similar threads
- Locked
- Question
- Locked
- Question