We run into a problem with 1 of our AWS EC2 c4.xlarge instances. It looks like when the total incoming traffic reaches about 1GB/5min, the instance is unable to process all EventBus messages, as well as is unable to support external communication via WebClient. According to various internet resources the VM itself should be able to process up to 1Gbit/s which is about 37.5GB/5min.
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: Unhandled exception
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: java.lang.NullPointerException
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: at io.vertx.core.net.impl.NetClientImpl$1.handleMsgReceived(NetClientImpl.java:197)
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: at io.vertx.core.net.impl.VertxNetHandler.lambda$channelRead$0(VertxNetHandler.java:64)
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:335)
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Apr 14 03:31:19 ip-XX-XX-XX-XX.us-east-1.compute.internal run_vertx[9193]: at java.lang.Thread.run(Thread.java:745)
We would appreciate all the help any of you guys can provide in either understanding the specifics of the VM / Vert.x configuration or guidance on EventBus utilization that can help us to resolve this.