You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by "Philipp Zehnder (Jira)" <ji...@apache.org> on 2020/12/01 08:56:00 UTC

[jira] [Created] (STREAMPIPES-262) OutOfMemoryError in MQTT adapter

Philipp Zehnder created STREAMPIPES-262:
-------------------------------------------

             Summary: OutOfMemoryError in MQTT adapter
                 Key: STREAMPIPES-262
                 URL: https://issues.apache.org/jira/browse/STREAMPIPES-262
             Project: StreamPipes
          Issue Type: Bug
          Components: Connect
            Reporter: Philipp Zehnder


When the MQTT adapter is running for some time we get an of memory exception.

I tested it twice for the same setting. The first time the error came after about 5 hours and 3000 events and the second time after 13 hours and 5500 events.

connect-worker-main_1 | Exception in thread "hawtdispatch-DEFAULT-7" java.lang.OutOfMemoryError: Direct buffer memory
connect-worker-main_1 | at java.nio.Bits.reserveMemory(Bits.java:703)
connect-worker-main_1 | at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:128)
connect-worker-main_1 | at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
connect-worker-main_1 | at org.fusesource.hawtdispatch.transport.SslTransport.initializeChannel(SslTransport.java:250)
connect-worker-main_1 | at org.fusesource.hawtdispatch.transport.TcpTransport.connecting(TcpTransport.java:425)
connect-worker-main_1 | at org.fusesource.hawtdispatch.transport.SslTransport.connecting(SslTransport.java:195)
connect-worker-main_1 | at org.fusesource.mqtt.client.CallbackConnection.createTransport(CallbackConnection.java:285)
connect-worker-main_1 | at org.fusesource.mqtt.client.CallbackConnection$4.run(CallbackConnection.java:236)
connect-worker-main_1 | at org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:100)
connect-worker-main_1 | at org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:77)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)