Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grizzly-jersey and undertow-jersey: MySQL deadlock part 2 #88

Open
zloster opened this issue Jun 12, 2019 · 1 comment
Open

grizzly-jersey and undertow-jersey: MySQL deadlock part 2 #88

zloster opened this issue Jun 12, 2019 · 1 comment
Milestone

Comments

@zloster
Copy link
Owner

zloster commented Jun 12, 2019

Lowering the JDBC pooled connections to 192 haven't resolved the problem. Next steps to try:

  • Lower the thread count in the worker pool;
  • Lower the pooled connections value;

But how the code manages to make 200+ waiting writing transactions with 192 connections?

@zloster zloster added this to the Better Times milestone Jun 12, 2019
@zloster zloster modified the milestones: Better Times, Round 19 Nov 14, 2019
@zloster
Copy link
Owner Author

zloster commented Nov 14, 2019

The mystery is no mystery anymore: I've missed the fact that there IS really a transaction deadlocks. See PR №5239 in the parent repository.

So sorting by id should be added for the update statements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant