There is no sense to run profiler in instrumentation mode on a high load.
Instead of using instrumentation you should use sampling mode.
This article describes the difference between instrumentation and sampling modes. JVisualVM is a good free tool for this task.
When configuring executors in multithreaded application, do not forget to assign names to your threads. It simplifies later profiling a lot, when you see a meaningful thread names in your profiler.
For example, you may use CustomizableThreadFactory from SpringFramework for that.
I have had spent some time recently making netty 3.6 sending some message when connection has been established.
What documentation suggests to do is to extend SimpleChannelUpstreamHandler and override method channelConnected(...).
It works fine unless SslHandler is used in the pipeline.
If handler is present, channelConnected() was never called on my handler.
Sometimes, reviewing code, I see misunderstanding of using Expected Exception concept in unit tests.
Since it may be references to existing javascript array from other objects, the best way to clear array contents is assign its length to zero
Here are few steps to configure protobuf-to-java compilation in your maven project:
Install google protobuf compiler on your computer.
brew install protobuf
Configure maven protobuf compiler plugin and protobuf-java dependency in pom.xml