[SERVER-43983] No Such Transaction Created: 14/Oct/19 Updated: 06/Dec/19 Resolved: 06/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | yeongseok kim | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Start a transaction in java application using java mongo driver's method session.startTransaction() and then stop the application process on purpose in the middle. and then restart the app and start another transaction. and the abort transaction happens automatically, |
| Participants: |
| Description |
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 08/Nov/19 ] | |||||||||||||||||||||||||||||||||||||||||
|
yeongseok.kim@bespinglobal.com, are you still having this issue? If so, could you please provide the information I requested in my last comment? | |||||||||||||||||||||||||||||||||||||||||
| Comment by Danny Hatcher (Inactive) [ 21/Oct/19 ] | |||||||||||||||||||||||||||||||||||||||||
|
Due to not having the full context of the code base, I can't run your code locally thus cannot reproduce the issue. Can you place some debug statements in your code at every step of the error process you are reporting? Then run the application and provide the Java output as well as the mongod logs for the full process. I'd like to see the first transaction being started on the mongod, the second transaction being started, and that second transaction being aborted, all in the Java and the mongod logs. | |||||||||||||||||||||||||||||||||||||||||
| Comment by yeongseok kim [ 18/Oct/19 ] | |||||||||||||||||||||||||||||||||||||||||
|
for more information, I have implemented the job in Spring Batch framework. and transaction is being handled in the provided method runBillingJobPerCompany. | |||||||||||||||||||||||||||||||||||||||||
| Comment by yeongseok kim [ 18/Oct/19 ] | |||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||
| Comment by Danny Hatcher (Inactive) [ 17/Oct/19 ] | |||||||||||||||||||||||||||||||||||||||||
|
I'm unable to reproduce the issue you're reporting. If you provide the actual Java code that you are using to encounter the problem I can take a look. | |||||||||||||||||||||||||||||||||||||||||
| Comment by yeongseok kim [ 15/Oct/19 ] | |||||||||||||||||||||||||||||||||||||||||
|
To Solve the problem, I temporarily deleted the collection. and then it worked. But, this workaround will affect service in production environment. So, I need to know what's root cause of this error. | |||||||||||||||||||||||||||||||||||||||||
| Comment by yeongseok kim [ 15/Oct/19 ] | |||||||||||||||||||||||||||||||||||||||||
|
Java driver version is the latest one. 3.11 sync version. ClientSession session = client.startSession() | |||||||||||||||||||||||||||||||||||||||||
| Comment by Danny Hatcher (Inactive) [ 14/Oct/19 ] | |||||||||||||||||||||||||||||||||||||||||
|
Can you please provide a reproduction in Java code as well as the Java driver version you are using? |