2

首先看一下下面的代码，当其他进程想要使用这些模型时，我有三个主要模型来管理StoreHouse和StoreHouseInvetory's 并且有其他模型被命名StoreHouseInventoryLock为临时锁定/解锁一些数量的's：StoreHouseInvetory

public class StoreHouse {
    private String  name;
    private Double  currentAmount;
}

public class StoreHouseInventory {
    private StoreHouse  storeHouse;
    private Good        good;
    private Double      amount;
}

public class StoreHouseInventoryLock {
    private StoreHouseInventory     inventory;
    private Double                  amount;
}

@Service
public class PermitService implements IPermitService {

    @Autowired
    private IStoreHouseInventoryLockService storeHouseInventoryLockService;

    @Autowired
    private IStoreHouseService storeHouseService;

    @Override
    @Transactional
    public void addDetailToPermitFromStoreHouseInventory(long permitId, long storeHouseId, long inventoryId, double amount) {

        // do some business logic here

        /* save is simple method
         * and uses Session.save(object)
        */
        storeHouseInventoryLockService.add(inventoryId, +amount);

        // do some business logic here
        storeHouseService.syncCurrentInventory(storeHouseId);   
    }
}

@Service
public class StoreHouseService implements IStoreHouseService {

    @Autowired
    private IStoreHouseInventoryService storeHouseInventoryService;

    @Autowired
    private IStoreHouseInventoryLockService storeHouseInventoryLockService;

    @Transactional
    public void syncCurrentInventory(storeHouseId) {
        /* is a simeple method that use query like below
         * select sum(e.amount)
         *   from StoreHouseInventory
         *  where e.storeHouse.id = :storeHouseId
         */
        Double sumOfInventory = storeHouseInventoryService.sumOfInventory(storeHouseId);
        /* is a simeple method that use query like below
         * select sum(e.amount)
         *   from StoreHouseInventoryLock
         *  where e.storeHouseInventory.storeHouse.id = :storeHouseId
         */
        Double sumOfLock = storeHouseInventoryService.sumOfLock(storeHouseId);

        // load method is a simple method to load object by it's id
        // and used from Session.get(String entityName, Serializable id)
        StoreHouse storeHouse = this.load(storeHouseId);
        storeHouse.setCurrentAmount(sumOfInventory - sumOfLock);

        this.save(storeHouse);
    }
}

问题是当storeHouseInventoryService.sumOfLock被调用时StoreHouseService.syncCurrentInventory，它不知道storeHouseInventoryLockService.add方法中PermitService.addDetailToPermitFromStoreHouseInventory方法的变化，并且错误地计算了锁的总和。

我认为这是因为我打电话时没有刷新会话storeHouseInventoryLockService.add。如果是真的，为什么休眠在此更改期间不刷新会话？如果没有，我该怎么办？

4

2 回答 2

0

如果当前执行的查询不与未刷新的表语句重叠，则可以安全地忽略刷新。

于 2017-02-21T13:22:35.677 回答
0

从IStoreHouseInventoryLockService.add已经附加了事务的方法中调用，然后将相同的事务传播到该方法，因此在外部完成add之前不会发生刷新。addDetailToPermitFromStoreHouseInventory

一个快速的解决方案是add使用 REQUIRES_NEW 事务传播类型标记该方法：

@Transactional(propagation=Propagation.REQUIRES_NEW)
public void add(..){..}

现在，在该方法完成后，即使有外部事务，所有持久性更改都将在退出时刷新到数据库。

于 2017-02-21T11:14:44.417 回答