做性能测试, 多次调用springboot-dubbo-seata的/dubbo/buy接口，就报LockConflictException

做性能测试, 多次提交同一个commodityCode 模拟多个用户同时购买同一个商品, 全部报io.seata.rm.datasource.exec.LockConflictException , 看锁是t_storage:1 库存表的id为1的行, 即请求商品库存, 请问怎么加大这个锁的大小,或者改成等待

seata-server v0.6.1

另外,尝试升级到最新0.7.0-SNAPSHOT, DEMO 运行不起来

Start by reproducing concurrent requests to the /dubbo/buy endpoint with the same commodityCode and inspect the LockConflictException on the t_storage row with id 1. Compare behavior between seata-server v0.6.1 and 0.7.0-SNAPSHOT, including why the demo does not run. Done means the supported lock-wait or conflict behavior and any relevant configuration are clearly identified.

Written by the indexing model from the issue text.