java - MyEclipse 8.5 调试模式停止时，线程无法终止，再次开启调试，直接会跳到上次停止时线程执行的地方，这是怎么回事？

Question

另外，线程中开启了事务，停止后再次执行，一直报错说事务已经存在，无法创建新事务，但是把事务注解注释掉再调试，还是会打印事务日志，怀疑是上个线程的事务。

Answer 1

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 2

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 3

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 4

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 5

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 6

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 7

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 8

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 9

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.

Answer 10

In addition, when a transaction is started in a thread and executed again after stopping, an error is always reported saying that the transaction already exists and a new transaction cannot be created. However, after commenting out the transaction annotation and debugging again, the transaction log is still printed. It is suspected that it is a transaction of the previous thread.