Thanks.
> --
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/akka-user/-/N95ljaLjp6gJ.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
--
Jonas Bonér
CTO
Typesafe <http://www.typesafe.com/> - Enterprise-Grade Scala from the
Experts
Phone: +46 733 777 123
Twitter: @jboner <http://twitter.com/jboner>
Google+: http://gplus.to/jboner
Thanks in advance.--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/N95ljaLjp6gJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
Yes, it worked. I am not stopping the remote actors anymore.
I think its a new issue since the same is observed for both remote and local actors (and local ones I do stop). The Actor class itself is being cleaned but the proxy object is being left there.
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/tz5MzYNKOAYJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
1. That was another issue :)2. Nothing else holds it, its pretty constant.
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/b2x_YvwkwzEJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
I mean nothing in my code holds it :)
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/fOJ3bDQxjLgJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/pWFO9_o_seYJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
In my application I use RemoteActors (typed actors) very intensively and lately during load tests I've discovered an interesting thing.Some time before I had a user group discussion with Victor about the need to "stop()" remote actor instance on the client side and the answer was that the actors die when connection drops and no need to stop them on the client.
But what if the connection never drops (client speaks with the server all the time) ? What I see now is that the memory is full of of actor proxy instances which are not being collected and cause out of memory errors.How should I approach this issue ?Thanks in advance.
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/N95ljaLjp6gJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
Currrenty I prepare lots of actors on the server side, with some "indexed" name and then access them from the client, round robin (all of that since there is no pool implementation in java).So server side actors are always alive and I never stop them. Anyways its not related to the current problem.
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/9Ssr2wXKYv8J.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
On Thu, Sep 8, 2011 at 3:18 PM, gutzeit <gut...@gmail.com> wrote:Currrenty I prepare lots of actors on the server side, with some "indexed" name and then access them from the client, round robin (all of that since there is no pool implementation in java).So server side actors are always alive and I never stop them. Anyways its not related to the current problem.
Ah, so the problem is that they leak on the client?
--To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/9Ssr2wXKYv8J.
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
--
Viktor Klang
Akka Tech Lead
If you aren't stopping local typed actors, then yes, it's going to leak.
The remote ones, if you're using client managed, you need to stop them on the client. For per-session and server managed they should not leak on the client.
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/9yzwz9a2_HkJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
I've discovered same (or similar) issue: Remote actor, per session,
leak at server side:
Here screenshot from MAT:
https://img.skitch.com/20110911-t8ycx9wimamt23h6ufi7r2gw4s.png
Do you call Actor.remote.shutdown() before terminating your clients?
Cheers,
V
Do you get the client disconnection event on the server properly?
I definitely getting postStop called (at least in most cases). Is it
enough? Or I should check for event?
I found one problem in my code - sometimes NullPointerException was
thrown in postStop. Can it cause leak?
Can please someone comment on this ? Please, please, please ? :)
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/Y0vd_YJZbxoJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
If not, why are you creating so many typed actor services, the idea is
to create a single one or a few ones and then fan out from this one.
I will add code to automatically unregister per-session actors, but
not the other ones, those you need to unregister yourself using:
Actor.remote.unregisterTypedActor("handle").
Please let me know ASAP.
/Jonas
> --
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/akka-user/-/crKmhaRH_owJ.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.
>
--
Jonas Bonér
CTO
Typesafe <http://www.typesafe.com/> - Enterprise-Grade Scala from the
Experts
Phone: +46 733 777 123
Twitter: @jboner <http://twitter.com/jboner>
Google+: http://gplus.to/jboner
On this:
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/crKmhaRH_owJ.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
Open a ticket to improve it
--
Jonas Bonér
CTO
Typesafe - Enterprise-Grade Scala from the Experts
Phone: +46 733 777 123
Twitter: @jboner
I checked all links under 'Project' on akka.io but havent found issue
tracker. :(
Is it top secret information?
> ...
>
> read more »
--
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
Thanks
--
Jonas Bonér
CTO
Typesafe - Enterprise-Grade Scala from the Experts
Phone: +46 733 777 123
Twitter: @jboner
Yes. You need to unregister the actor yourself. It is not possible for Akka to know when it can safely unregister your actor.
--
Jonas Bonér
CTO
Typesafe - Enterprise-Grade Scala from the Experts
Phone: +46 733 777 123
Twitter: @jboner