Seems akka Remoting still keep some memory object even sender called 
actorSystem.shutdown. test as below


akka version 2.3.4

Receiver(only 1) <==========> Sender (multiple)


We keep create sender and (around *300k* Senders) each sender behavior same 
way - Connect to Receiver,Send serveral messages, shutdown actor system

When all *300k* Senders run completed. The Receiver consumed lot of memory 
after full gc (456 MB).
2.634: [GC 15424K->3809K(58816K), 0.0184900 secs]
3.411: [GC 19233K->6358K(58816K), 0.0095820 secs]
....
7040.107: [GC 335042K->250050K(333056K), 0.0419540 secs]
7040.149: [Full GC 250050K->219156K(346368K), 2.2192770 secs]
...
42445.401: [GC 476143K->461016K(628928K), 0.0100950 secs]
42445.411: [Full GC 461016K->456824K(651840K), 1.4056710 secs]

run "jmap -dump:live,format=b,file=akkatestheap.bin 28819" and "jhat 
akkatestheap.bin" to analyze the heap content, find there are plenty of "
*akka.remote.transport.netty.TcpAssociationHandle*" which contains 
"remoteAddress". 

In fact all Senders' actor system were shutdown. Why the Receiver actor 
system still save so many Senders' address? Is this a *memory leak*?

-- 
>>>>>>>>>>      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
--- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to