These are chat archives for akkadotnet/akka.net

2nd
Feb 2017
Chris G. Stevens
@cgstevens
Feb 02 2017 00:34
It would appear that I have a really bad production memory leak :worried: I have just started to dig and using the memory profiler it appears that it is the EF and data objects are not getting disposed. The normal use that the service I am using was originally designed is for our websites. I guess I could kill that actor off and recreate it but not sure I understand if that actor would get a new kernel or context and does everything go dispose correctly. I'm using DI to inject the service and tried a couple different scopes with the same result. Just not sure what the issue is really yet but wanted ask if any has had any similar issues. Should the data context be disposed or can it live forever?
So far I'm not seeing anything that stands out. Perhaps I'm actually doing a mutable object somewhere. I don't know. Will continue tomorrow. Thanks for any advice!
Chris G. Stevens
@cgstevens
Feb 02 2017 00:57
@ckarcz I am using team city and I have it so I can deploy my services which is a member of the cluster to the same or different machine based on the configuration. Changing service name and port. Has worked out well for having 3 Dev environments on the same system and then push it to QA and prod. Then the same for our websites. Each member does have a specific role.
Chris Karcz
@ckarcz
Feb 02 2017 01:07
@cgstevens I was thinking it'd be nice to have a web GUI view of the cluster and be able to select a router and deploy child actors via this web interface (permissions) instead of going another to a other deployment "manager" (docker, octopus, xldeploy, team city, etc).
Chris G. Stevens
@cgstevens
Feb 02 2017 01:59
@ckarcz I gotcha and sounds cool.
Yip-Yip
@Yip-Yip
Feb 02 2017 02:21
Is there a Akka.net solution similar to Kamon.io for monitoring reactive systems ?
Bartosz Sypytkowski
@Horusiath
Feb 02 2017 07:58
@mwpro regarding your yesterday question about Hyperion serializer: could you tell me please, where your problem actually lies? From what I see, all of those are standard issues of people overusing schema changes. Maybe it should be written more explicitly but Hyperion version tolerance is limited to adding new fields to existing schema and changing field names if their position and type (or to be more explicit binary representation of the value) doesn't change
Maciej Wódke
@mwpro
Feb 02 2017 08:48

@Horusiath In my example, when I once serialize my object with two properties (string and int, Step 1), and then I add a new property to the class I cannot have my object deserialized (steps 3, 4, 5). Adding a new field only worked for a string property at the end of class (step 2).

But if the order and type of fields matters as you said, then it makes some sense why they are not deserialized properly.

scottBat
@scottBat
Feb 02 2017 10:59
in the type safe information at https://github.com/typesafehub/config#uses-of-substitutions it gives an example with subsitutiions and merging. “inheritance” as it call it. The example:
data-center-generic = { cluster-size = 6 }
data-center-east = ${data-center-generic}
data-center-east = { name = "east" }
data-center-west = ${data-center-generic}
data-center-west = { name = "west", cluster-size = 8 }
Should yield a merged config, but the hocon parser in Akka.net 1.1.3 does not seem to parse correctly. It doesn’t merge. Is this a known issue?
Arsene Tochemey GANDOTE
@Tochemey
Feb 02 2017 11:05
Hello Akka geeks, can someone explain to me how message immutability plays well with generic type?
Arsene Tochemey GANDOTE
@Tochemey
Feb 02 2017 11:10
Hello
Maxim Cherednik
@maxcherednik
Feb 02 2017 12:06
hi
can you extend a bit ?
Arsene Tochemey GANDOTE
@Tochemey
Feb 02 2017 12:09

Is it safe to do something like this looking at the thread safe beauty of Akka.Net

public class SomeMessage<T> {
    public SomeMessage(T data){
        Data = data;
    }
    public T Data{get;}
}

where T is also a immutable object?

so that in my receive I can proceed like
Receive<SomeMessage<T>>();
Maxim Cherednik
@maxcherednik
Feb 02 2017 12:22
Should be fine.
I have it in my project.
Arsene Tochemey GANDOTE
@Tochemey
Feb 02 2017 12:22
@maxcherednik Thank you
Natan Vivo
@nvivo
Feb 02 2017 14:10
looking in the archives but I cannot find it. how do I subscribe to an event that tells me the cluster is up?
Sometimes google does magic :)
Natan Vivo
@nvivo
Feb 02 2017 14:13
thanks
Kris Schepers
@schepersk
Feb 02 2017 15:59
Anyone else from here at #DDDEU ??
Damian Reeves
@DamianReeves
Feb 02 2017 16:21
@Horusiath in Akkling... if I ask and specify a specific response type, what will happen if the response is of a different type?
nm... I see you send back an Error with an InvalidCastException
Lutando Ngqakaza
@Lutando
Feb 02 2017 18:27
can i send Stream objects as instance of my message?
Lutando Ngqakaza
@Lutando
Feb 02 2017 19:28
ie anything that inherits IO.Stream
Arjen Smits
@Danthar
Feb 02 2017 20:01
@schepersk I was there today @ #DDDEU, and im there tomorrow as well
there was some good exposure for akka.net as well
Wim Van Houts
@_kiwi78_twitter
Feb 02 2017 20:29
In the docu it states that it is best not to instantiate the runtime in an ASP.NET application because IIS behaviour, which I agree upon, and, it states it would be best to create the runtime and actors in a separate application (or windows service). In this scenario, what would be the advised way to communicate between te ASP.NET applicaiton and the runtime? Is it a good idea to instantiate a runtime in the ASP.NET app which if it runs, gets a reference to the actors in the windows service runtime (using Akka.remote)? Any alternatives?
Arjen Smits
@Danthar
Feb 02 2017 20:44
no what is meant, is that its best to run a seperate application, which is part of your cluster. And have that application expose a service interface that your webapp calls. Via WCF or something
Arjen Smits
@Danthar
Feb 02 2017 20:52
ofc does not have to be part of a cluster or anything. can be a stand alone actor system as well
Sean Gilliam
@sean-gilliam
Feb 02 2017 20:58

Via WCF or something

WCF

: PTSD triggered : :P

Bartosz Sypytkowski
@Horusiath
Feb 02 2017 21:04
@Lutando not by default. If you try hard, you could achieve that, but that is rather the case of stinky design and potential leaks.
Arjen Smits
@Danthar
Feb 02 2017 21:35
@sean-gilliam lol :D