如何在Spring/OpenJPA 1中重新创建select更新行锁定1
问题描述:
我需要在Spring/OpenJPA 1应用程序中不允许同时使用相同的确认代码。我们决定使用select来更新策略,所以我们创建了表AdmissionLock(id,Confirmation_Code,Terminal)。
单独的示例JDBC应用程序可以很好地与此策略配合使用。它允许同时处理不同的确认码,并且不允许同时处理相同的确认码。请参阅下面的示例代码:如何在Spring/OpenJPA 1中重新创建select更新行锁定1
线程代码:
conn.setAutoCommit(false);
long retId = Util.lockBySelectUpdate(conn, threadName, terminalCode, confNumber);
Util.updateConfCode(conn, threadName, terminalCode, confNumber);
conn.commit();
主程序代码:
String confCode1 = "21";
String confCode2 = "22";
String terminalCode1 = "10";
String terminalCode2 = "11";
Connection conn1 = Util.getNewConnection();
Connection conn2 = Util.getNewConnection();
AdmissionThread admissionThread1=new AdmissionThread(terminalCode1, conn1, confCode1, "Thread1", 10);
AdmissionThread admissionThread2=new AdmissionThread(terminalCode2, conn2, confCode2, "Thread2", 0);
admissionThread1.start();
Thread.sleep(2000);
admissionThread2.start();
SQL:
"SELECT * FROM ADMISSIONLOCK WHERE CONFIRMATION_CODE=? FOR UPDATE"
"update ADMISSIONLOCK set CONFIRMATION_CODE=? where TERMINAL_SERIAL_NUMBER=?;";
由于我们的应用程序是春/ OpenJPA的1我需要在Spring/OPenJPA 1代码中加入这个想法。所以,我创建了这个简化代码的服务:
@Transactional
public void processAdmissionLock (String terminalSerialNumber, String confirmationCode){
AdmissionLock admissionLock = new AdmissionLock(terminalSerialNumber, confirmationCode);
query = entityManager.createNativeQuery(SQL_LOCK_STRING);
entityManager.lock(admissionLock, LockModeType.READ);
query.setParameter(1, confirmationCode).getResultList();
if(isEntityPersistent(admissionLock)) {
admissionLock = entityManager.merge(admissionLock);
} else {
entityManager.persist(admissionLock);
}
}
AdmissionLock实体:
@Entity
@Table (name = SdiAdmissionLock.TABLE_NAME)
public class SdiAdmissionLock extends AbstractEntityImpl {
private static final long serialVersionUID = 1L;
private long uidpk;
private String terminalSerialNumber;
private String confirmationCode;
private Date createdDate;
public static final String TABLE_NAME = "SDIADMISSIONLOCK";
...
}
我的问题是,这个代码不作任何锁定。两个具有相同验证码的同时线程都通过
答
我最终使用了与JDBC应用程序中相同的本机查询。一个重要的区别 - 起始事务(“START TRANSACTION”)和提交(“COMMIT”)被转移到MYSQL本身并由JDBC executeUpdate()方法调用。