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

[Draft] to fix "java.lang.IllegalStateException: Session/EntityManager is closed" #1118

Merged
merged 1 commit into from
Jan 13, 2022

Conversation

Sanne
Copy link
Member

@Sanne Sanne commented Jan 11, 2022

@DavideD
Copy link
Member

DavideD commented Jan 11, 2022

I've tested it and it seems to also fix #1073

@gavinking
Copy link
Member

Oh, right, fine, this undoes the thing I just noticed.

I think we should definitely merge this. If i understand correctly, the change made in https://github.com/hibernate/hibernate-reactive/pull/948/files would cause the Hibernate session and transaction between all threads in a verticle. If that's right, then no wonder users were running into concurrency problems.

@gavinking
Copy link
Member

I'm going to just merge this.

@gavinking gavinking marked this pull request as ready for review January 13, 2022 17:02
@gavinking gavinking merged commit e89a6e4 into hibernate:main Jan 13, 2022
@DavideD
Copy link
Member

DavideD commented Jan 13, 2022

@gavinking, Please, check with us before merging things that are in draft
and assigned to somebody else

@gavinking
Copy link
Member

Um. No, I don't think that's a reasonable thing to yell at me about. The change to use put() and get() instead of putLocal() and getLocal() was clearly wrong, and certainly unintended. I know because this is code I originally wrote and I know what it's supposed to do.

And the change that broke it broke Hibernate Reactive for essentially every user. It's extremely embarrassing that we have not noticed this issue since September, and have had multiple users report multiple bugs that I assume stem from this, and we have not done anything about it until now.

So, yeah, my fault for being swapped out, for sure, but right now we need to prioritize the fuck out of getting this fix out into a release, not keep sitting around fiddling and twiddling our fingers and worrying what process is followed when merging fixes to serious bugs!

@gavinking
Copy link
Member

Seriously, we should have been on top of this way earlier and we weren't.

We need to be feeling quite bad about this right now.

@Sanne Sanne deleted the FixingCloseException branch January 13, 2022 18:37
@Sanne
Copy link
Member Author

Sanne commented Jan 13, 2022

We need to be feeling quite bad about this right now.

Don't worry, I felt quite bad when I realized my mistake.

But there's no reason to rush things as we won't be able to release until tomorrow the earliest.

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.

java.lang.IllegalStateException: Session/EntityManager is closed
3 participants