-
Notifications
You must be signed in to change notification settings - Fork 11
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
SocketChannel looping infinitely while handling probe interval #28
Comments
Related: This bug was found in Apache MINA 2.1.2 and fixed in 2.1.3. Please see the fix in 2.1.3. |
From the previous MINA issue the fix is shown in the following link. It is a bit disconcerting because the fix is based on MINA's use of Based on the MINA fixes this could be caused by simultaneous use of the same pooled buffer by multiple threads. /cc @buritos |
As far as I know we have addressed this issue in various places by not releasing the buffer when it is handed over to an async operation, expecting that that operation will release when it is done. This is difficult to verify in all places though. Have there been any WARN log entries regarding multiple calls to @danilo-ambrosio Please reply. ^^^ |
@danilo-ambrosio Same thing happened on Tomcat with a fix reference here: |
Thanks for sharing @vaughn Vernon <[email protected]> . I'll take a look.
Em ter., 4 de fev. de 2020 às 15:47, Vaughn Vernon <[email protected]>
escreveu:
… @danilo-ambrosio <https://github.com/danilo-ambrosio> @kbastani
<https://github.com/kbastani> Same thing happened on Tomcat with a fix
reference here:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60578
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGZM7U7RKVIOMQPDEV5SQXLRBGSZRANCNFSM4KNZ2BGQ>
.
|
@danilo-ambrosio Same for Jetty, but apparently not pursued: |
@VaughnVernon @buritos
Some of the mentioned steps affected positively the SocketChannel in my local environment, solving partially or totally the polling lock, but it didn't make any difference on Heroku environment. I'll keep trying. Suggestions are welcome. |
Cross linking to more info provided in a different Issue reported by @fgr |
@fgr I think the following shows the final fixes for Netty: netty/netty#535 (comment) The following is the current https://netty.io/downloads.html Look for
|
@VaughnVernon Thanks for the Netty links and your explanations. Since I know nothing about vlingo-wire (and just reading the source code does not give me enough understanding of the issue), I set up an Eclipse workspace for debugging. If I understand your previous comment correctly, the issue has not been solved for vlingo-wire, but has been solved for Netty and the vlingo team is going to adapt Netty's fix to vlingo-wire. Is my understanding correct? Does it make sense and help you in any way, if I start looking into vlingo-wire as well? I have not neither worked with Java's NIO nor with vlingo internals. But I'm happy to look further into this if you think it makes sense. |
@fgr Yes, it would be great to have your help. If you have a day/time that works well for you I can set up a meeting to discuss. Please let me know by email. You can find my email address on my gh profile. |
@VaughnVernon Thanks. I sent you an email. |
@fgr I didn't receive. Use: vaughn at kalele dot io |
The saga continues, and by saga I don't mean long-running transactions. https://stackoverflow.com/questions/61215854/heroku-h15-errors-using-java-nio-directly-and-netty |
This has been fixed by adding an HttpAgent to VLINGO/HTTP. https://github.com/vlingo/vlingo-http/tree/master/src/main/java/io/vlingo/http/resource/agent |
The SockeChannelSelectionProcessorActor loops infinitely while trying to perform some Rest operations on the calculator app, which is a recent implemented vlingo-xoom example running on Heroku environment.
The following thread dump was captured from Heroku's jStack when the issue occurred.
The app is using Java 8 and running on Ubuntu-based Heroku's OS.
The text was updated successfully, but these errors were encountered: