I see. Thanks.
With the provided code I couldn't reproduce the issue at least in the quick
tests I did. Could you run
jmap -histo:live on the command line when some memory has accrued and
send the output here (or in private)?
Johannes
On Thu, Nov 22, 2018 at 1:16 PM Sean Gibbons
wrote:
>
And by native TLS I just mean a standard TLS AKKA Server, apologies for any
confusion.
--
__
Séanadh Ríomhphoist/_
Email Disclaimer__
**
Tá an ríomhphost seo agus
aon chomhad a sheoltar leis faoi rún agus is lena úsáid ag an seolaí agus
sin amháin é. Is féidir tuilleadh a léamh anseo.
Just to clarify by non-native TLS I meant to say "no TLS" i.e. simply an
insecure AKKA server.
--
__
Séanadh Ríomhphoist/_
Email Disclaimer__
**
Tá an ríomhphost seo agus
aon chomhad a sheoltar leis faoi rún agus is lena úsáid ag an seolaí agus
sin amháin é. Is féidir tuilleadh a léamh
Hi Johannes thanks for the reply,
I used the example code for both the native and non-native TLS Akka
servers. In the case of the non-native TLS server setup I simply changed
the Http.bind() method to not include the setupTls parameter e.g.
*Http().bindAndHandle(routes,
"0.0.0.0", 17715)*
--
Hi Sean,
thanks for the comprehensive report. What do you mean with a native vs
non-native TLS server? Is the example app for the "native TLS" server?
Johannes
On Wednesday, November 21, 2018 at 6:26:09 PM UTC+1, Sean Gibbons wrote:
>
> Hi all,
>
> I have been working with a native TLS Akka
