As per my project requirements, which is using Weblogic Application Server, it will co-exists with Pro4 Legacy System. But both of them will use the same Oracle database.
Pro4 application locks a record using "SELECT...FOR UPDATE" statement and keep it locked until the end of transaction (at the end of screen).
In the meanwhite, if web application tries to access the same record using JDBC API through IBATIS, it waits indefinetely until record is released (by commit/rollback). This is an undesirable situation where application server should show an error to user that record is locked by legacy system user, not that JSP page will wait forever.
What is the alternative approach or solution to this problem using IBATIS?
In Statement, there is a timeout method stmt.setQueryTimeout(<secs>), which is helpful in this scenario. But I dont have access
to Statement object in IBatis.
Do we need to support this in IBatis??
Alliance Bernstein: Winner of Money Management "FUND MANAGER OF THE YEAR 2005" Member of the Global AXA Group ********************************************************************************* Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this email. If you have received this email in error please notify the sender immediately and delete this email. Any views expressed in this email are not necessarily the views of AXA. Thank you. ********************************************************************************** |
