-
Type: Bug
-
Status: Closed (View Workflow)
-
Priority: Minor
-
Resolution: Done
-
Affects Version/s: 1.1.0
-
Fix Version/s: 1.2.0
-
Component/s: None
-
Labels:None
-
Epic Link:
-
Sprint:Cardinal Sprint 2 (4/6-4/17)
Encountered this while running messaging performance evaluation.
015-04-13 15:28:17,775 | ERROR | rf-test-receiver | Tools | 74 - org.onosproject.onlab-misc - 1.2.0.SNAPSHOT | Uncaught exception on onos-net-perf-test-receiver
java.lang.OutOfMemoryError: Direct buffer memory
at java.nio.Bits.reserveMemory(Bits.java:658)[:1.8.0_31]
at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123)[:1.8.0_31]
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)[:1.8.0_31]
at com.esotericsoftware.kryo.io.ByteBufferOutput.<init>(ByteBufferOutput.java:50)
at org.onlab.util.KryoNamespace.serialize(KryoNamespace.java:235)
at org.onlab.util.KryoNamespace.serialize(KryoNamespace.java:224)
at org.onosproject.store.serializers.KryoSerializer.encode(KryoSerializer.java:49)
at org.onosproject.store.app.NetPerfApp$$Lambda$176/2133167034.apply(Unknown Source)
at org.onosproject.store.cluster.messaging.impl.ClusterCommunicationManager$InternalMessageResponder.handle(ClusterCommunicationManager.java:305)
at org.onlab.netty.NettyMessagingService$2.lambda$handle$0(NettyMessagingService.java:211)
at org.onlab.netty.NettyMessagingService$2$$Lambda$21/592551204.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]