userkdg opened a new issue #14541:
URL: https://github.com/apache/shardingsphere/issues/14541


   ### Which version of ShardingSphere did you use?
   5.1.0-GA
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   Proxy
   
   ### Expected behavior
   update, delete, add sql will throw read only Exception.
   
   ### Actual behavior
   from application log: 
   
![image](https://user-images.githubusercontent.com/21057449/148184941-732e7d80-6679-474d-b753-c197b7f4ee00.png)
   
   from proxy log:
   
![image](https://user-images.githubusercontent.com/21057449/148190966-bb4ad579-f14a-438e-a58d-5a07b9d9ff99.png)
   
   
   remark:  two case are transaction issues.
   
   ### Reason analyze (If you can)
   In the application connection agent, if transaction operations are 
performed, such as (batch) new addition, (batch) modification, (batch) 
deletion, exceptions will occur
   feature:
   - Occasionally
   - Prone to happen under multithreading
   - Transactional
   
   remark: Personal level is limited, unable to locate specific code issues for 
transaction issues, But this is more important for application . 
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   single transaction sql
   application env:
   - druid pool (default transaction config)
   - spring transaction 
   proxy env:
    ``` - !TRANSACTION
     defaultType: XA | LOCAL
     providerType: Atomikos | null ``` 
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to