-
-
Notifications
You must be signed in to change notification settings - Fork 271
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
[bug] error deallocating object already removed from the pool #535
Comments
We did fix some issues recently that seem similar to what you're describing. The issues occurred in an upstream library used by the batch-module (generic-object-pool, clustered-object-pool and smtp-connection-pool, which all form a chain of dependencies). It might be worth to try 8.11.1. I have a feeling this has been solved already (but these things are always difficult to pinpoint). |
Thanks for the feedback. I will define the version 8.11.1 in the next website update, and will see if the issue is solved. |
@bbottema I updated the website with the version
It seems an error about sending a specific email, which could be fine, the issue is that it logs the error instead of just throwing an exception that can be caught after calling This is not about the original error of this issue, but the original error (dealocating) only happened rarely, some days it didn't even happen, so I wait a few days to see if that error happens. But regarding this new error, is there something that I can do so that it's not directly logged as error, and just throw an exception that I can handle when calling |
@bbottema Another exception that happened after updating (
The main issue is that I can't handle these errors. I send lots of emails every day and it's expected that some of them fail, so is there a way to make it just throw the error so that I can handle it instead of logging the error and bloating our error logs? (maybe changing some setting to not log errors and just throw them or something similar) |
Yes, I will give it some thought. It will take at least a week or two to come up with a fix, since I'm on (a short) vacation starting this weekend. |
@bbottema Ok, thanks! |
Hi, we started using this library for some weeks after upgrading to Java 20 and it is working fine so far (thanks), except for an error that happens a few times a day (normally between 2 and 5 times).
Our mailer configuration is:
With the properties:
And the libraries versions:
We sometimes, almost every day, see the error in the logs:
We can't even process those errors like we do for every other error log in our application because it doesn't happen when sending emails (
Future<Void> future = mailer.sendMail(email); ... future.get()
), it happens in background, probably in some background process that manages the email connection pool, so we can't format the error the way we want to show in the logs.We send about 100.000 to 200.000 emails per day (SES), and I see that this error is more common in periods with more emails sent at the same time (although it might be this way because the chance for triggering this error increases when sending more emails).
Any suggestions on how to fix it?
The text was updated successfully, but these errors were encountered: