-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Kafka consume stopped without any exception log #27265
Comments
/cc @alesj, @cescoffier, @ozangunalp |
@liuzhaozhao I've been looking at your issue to reproduce it and get back to you on the upstream project. |
Okay, thanks |
Hello. I am experiencing similar issue as @liuzhaozhao described. It happened once I update quarkus version from 2.9.2 to 2.11.2 (also with 2.12.0). |
Hi, I tried to reproduce this without success a couple of weeks ago but was sidetracked. I know it is hard in these cases but a reproducer would be awesome. |
I believe I found what the problem was, and fixed with smallrye/smallrye-reactive-messaging#1895. It is released on reactive messaging 3.19.1 and will arrive in Quarkus shortly |
closed by #28117 |
Describe the bug
This problem was reported in the smallrye-reactive-messaging open source project, but the activity is not as good as that of quarkus (slow response), we may have it once every 1-2 days in production, and the node must be restarted to solve it. I hope the quarkus team can help follow up on this question.
smallrye/smallrye-reactive-messaging#1811 (comment)
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.7.6.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: