Hi guys, the question I depicted has been solved by myself. I just give some comments for further reference.
The jbpm version that caused the problem was jbpm 5.3. Once I upgraded to 5.4, the question disappeared. But if you upgrade from 5.3 to 5.4, you need to run ant clean.db firstly. otherwise you will encounter very weird transaction issue.