Hi, Thank you for reporting it.

After quick test it turned out that this allocation starts and happens only after connecting JMX client (I checked HEAP memory usage using YourKit running in parallel and after startup Tigase maintained ~35M memory usage until VisualVM connected over JMX).

I'm aware this is inconvenient as JMX is the main monitoring solution of JVM processes but to avoid issue for now you should avoid using JMX. We will address issue in one of the upcoming versions)

(#server-1158)