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

PAYARA-3487 Race condition in ConnectionPool #3924

Merged

Conversation

Cousjava
Copy link
Contributor

@Cousjava Cousjava commented May 1, 2019

When a connectionpool is closed it now logs an error rather than throwing an exception.

A multiexception is printed, showing both the current stack trace and the trace of where
the resource was previously closed.

…wing an exception.

A multiexception is printed, showing both the current stack trace and the trace of where
the resource was previouslt closed.
@Cousjava Cousjava added this to the 5.192 milestone May 1, 2019
@Cousjava
Copy link
Contributor Author

Cousjava commented May 1, 2019

Jenkins test please

@@ -67,6 +69,20 @@ public boolean isBusy() {

public void setBusy(boolean busy) {
this.busy = busy;
if (!busy) {
busyException = new TwiceBusyException();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be controlled by a system property? I believe there is significant overhead in collecting stacktrace at every connection close.

@Cousjava
Copy link
Contributor Author

Cousjava commented May 9, 2019

Jenkins test please

@Cousjava Cousjava requested a review from pdudits May 9, 2019 09:52
@Pandrex247 Pandrex247 merged commit 071ef7a into payara:master May 14, 2019
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

Successfully merging this pull request may close these issues.

4 participants