-
Notifications
You must be signed in to change notification settings - Fork 818
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
Periodic failure #844
Comments
@Tong-07 your description is not enough to reproduce or investigate the issue. Please provide a reproducer or some useful logs when the issue manifest. However, I would check the memory status of the JVM process, in particular the direct memory, used by the network stack (MQTT Netty codecs). |
An error is reported in this circled method, because when an exception occurs, the subsequent log is not printed, the captured error has no stack information, just NPE {}, Capture the information is a Java. Lang. NullPointerException: null 。and the client cannot connect, and the data sent on the connection will be NPE is reported at the location in the figure, and there will be this log, WARN 12938 --- [lettuce-eventExecutorLoop-1-4] i.n.u.c.SingleThreadEventExecutor: Unexpected exception from an event executor: java.lang.OutOfMemoryError: GC overhead limit exceeded |
Which version of moquette are you using? From the fact that you use All version prior to 0.17 have known memory leaks, so Out Of Memory Errors are to be expected. Try upgrading to the latest version. |
0.13 |
0.17 version Fixed the memory leak problem? |
yes, as far as we know. |
Expected behavior
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code) or complete log file
Moquette MQTT version
MQTT_3_1_1
JVM version (e.g.
java -version
)1.8
OS version (e.g.
uname -a
)centos 7
More than 10,000 clients are connected, usually once every week, the connection will not be connected, some data cannot be sent down, and some will also appear after internalPublish, empty pointer error, and no stack information.
After the restart, it will return to normal. How to troubleshoot this?
The text was updated successfully, but these errors were encountered: