[fix] - JedisException when test ends #629
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This fix is not with the 0.6 version (built much earlier than this fix) of the plugin. Can you share the latest artefact location? |
I have just released the new version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing the Exception: redis.clients.jedis.exceptions.JedisException: Could not return the broken resource to the pool
Which is triggered when jmeter calls testEnded() method.
Evidence below:
I added a log to show the total number of idle connections before calling
pool.destroy()attestEnded(String host)and noticed that the number of idle connections was equal to the number of exceptions. As we can see here:Then I forced JMeter to consume all the connections before calling
pool.destroy().I know the problem is in Jedis itself, as it was already addressed in redis/jedis#3353. The other possible solution would be updating the Jedis version, but I don't know if that would lead to any compatibility issue.