4mc 1.3.0

Introduced direct memory buffer pools to cope with "java.lang.OufOfMemoryError: Direct Buffer Memory".
This is not happening on cluster jobs but if client apps open huge number of 4mc files, it happens with lazy GC that direct nio buffers are alive and their dedicated memory go over.
With dedicated cache pool of these buffers client applications are much safer, but in worst case it's still not enough, the recommended setting is to increase direct buffer memory of your app by e.g.:
-XX:MaxDirectMemorySize=512m