Did you get a chance to try out the fix?
The whole dev team here has just come back from the JavaZone conference in Oslo, so we've not looked into this yet.
We'll get our hands on it as soon as possible - it's attached to the SR, right?
BR. Jan-Helge Bergesen
Good news everyone!
I can confirm that the build attached to 3-11320855021 does the trick.
Both with and without setConnectionCachingEnabled(true), we end up with a heap at about 12-17 Mb after our simple test is done - which seems like a OK number at that stage.
Above: with ConnectionCachingEnabled=true - GC forced by refreshing heap historgram at points with notable drops in heap graph.
Below: with ConnectionCachingEnabled=false (actually not set) - GC-ing as above.
We are happy to proceed with this fix for this issue.