Sean Gibbons
2018-11-21 17:06:50 UTC
Hi all,
I have been working with a native TLS Akka HTTP service deployed to
Production. We have noticed memory increasing consistently throughout the
week until our Akka service died due to memory constraints.
Running a JProfiler locally I've managed to reproduce what I believe to be
a leak in SSL related classes just using Akka code.
I am using Akka HTTP version 10.1.5 and Akka version 2.5.18.
I ran a comparison of a non native TLS Akka server vs a native TLS Akka
server. The load test consisted of sending around 20 req/s to a dummy
endpoint that simply just returns a hardcoded "hello" string.
A *complete* *runnable* *example* of the Akka code used to produce this
leak can be found as *dummy-app.zip *along with JProfiler snapshots in this *Google
Drive link*
- https://drive.google.com/drive/folders/1Q1zgN4m5J4oI_S0TupMs1LO1UVlJfh87?usp=sharing
*With Native TLS:*
[image: Screen Shot 2018-11-21 at 12.09.17 PM.png] <about:invalid#zClosurez>
JProfiler snapshots associated with this image are *included *in the*
Google Drive link *above and named:
- TLSLocal1.jps
- TLSLocal2.jps
- TLSLocal3.jps
Each blue line above is when a snapshot was taken.
*Without Native TLS:*
<about:invalid#zClosurez>[image: Screen Shot 2018-11-21 at 12.12.58 PM.png]
<about:invalid#zClosurez>
JProfiler snapshots associated with this image are *included *in the* Google
Drive link *above and named:
- NoTLSLocal1.jps
- NoTLSLocal2.jps
- NoTLSLocal3.jps
Each blue line above is when a snapshot was taken.
Any help is much appreciated on this topic thanks.
--
__
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.
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>Â
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>*
_
This e-mail and any
files transmitted with it are confidential and are intended solely for use
by the addressee. Read more here.
<https://www4.dcu.ie/iss/email-disclaimer.shtml>Â _
*_
--
*****************************************************************************************************
** New discussion forum: https://discuss.akka.io/ replacing akka-user google-group soon.
** This group will soon be put into read-only mode, and replaced by discuss.akka.io
** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced
*****************************************************************************************************
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+***@googlegroups.com.
To post to this group, send email to akka-***@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
I have been working with a native TLS Akka HTTP service deployed to
Production. We have noticed memory increasing consistently throughout the
week until our Akka service died due to memory constraints.
Running a JProfiler locally I've managed to reproduce what I believe to be
a leak in SSL related classes just using Akka code.
I am using Akka HTTP version 10.1.5 and Akka version 2.5.18.
I ran a comparison of a non native TLS Akka server vs a native TLS Akka
server. The load test consisted of sending around 20 req/s to a dummy
endpoint that simply just returns a hardcoded "hello" string.
A *complete* *runnable* *example* of the Akka code used to produce this
leak can be found as *dummy-app.zip *along with JProfiler snapshots in this *Google
Drive link*
- https://drive.google.com/drive/folders/1Q1zgN4m5J4oI_S0TupMs1LO1UVlJfh87?usp=sharing
*With Native TLS:*
[image: Screen Shot 2018-11-21 at 12.09.17 PM.png] <about:invalid#zClosurez>
JProfiler snapshots associated with this image are *included *in the*
Google Drive link *above and named:
- TLSLocal1.jps
- TLSLocal2.jps
- TLSLocal3.jps
Each blue line above is when a snapshot was taken.
*Without Native TLS:*
<about:invalid#zClosurez>[image: Screen Shot 2018-11-21 at 12.12.58 PM.png]
<about:invalid#zClosurez>
JProfiler snapshots associated with this image are *included *in the* Google
Drive link *above and named:
- NoTLSLocal1.jps
- NoTLSLocal2.jps
- NoTLSLocal3.jps
Each blue line above is when a snapshot was taken.
Any help is much appreciated on this topic thanks.
--
__
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.
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>Â
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>*
_
This e-mail and any
files transmitted with it are confidential and are intended solely for use
by the addressee. Read more here.
<https://www4.dcu.ie/iss/email-disclaimer.shtml>Â _
*_
--
*****************************************************************************************************
** New discussion forum: https://discuss.akka.io/ replacing akka-user google-group soon.
** This group will soon be put into read-only mode, and replaced by discuss.akka.io
** More details: https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced
*****************************************************************************************************
Read the docs: http://akka.io/docs/
Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
---Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https://groups.google.com/group/akka-user
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+***@googlegroups.com.
To post to this group, send email to akka-***@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.