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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.