by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 08:50
    storware-mchojnacki opened #4514
  • Jul 13 20:11
    Arkatufus commented #4511
  • Jul 13 20:10
    Arkatufus synchronize #4511
  • Jul 13 18:45
    Aaronontheweb milestoned #4505
  • Jul 13 18:45
    Aaronontheweb labeled #4505
  • Jul 13 18:45
    Aaronontheweb labeled #4505
  • Jul 13 18:45
    Aaronontheweb commented #4505
  • Jul 13 18:26
    Aaronontheweb synchronize #4510
  • Jul 13 18:24
    Aaronontheweb synchronize #4513
  • Jul 13 18:24

    Aaronontheweb on dev

    Use Props.Create<TActor>() inst… (compare)

  • Jul 13 18:24
    Aaronontheweb closed #4509
  • Jul 13 18:24
    Aaronontheweb milestoned #4509
  • Jul 13 18:24
    Aaronontheweb labeled #4509
  • Jul 13 18:24
    Aaronontheweb labeled #4509
  • Jul 13 18:23

    Aaronontheweb on dev

    Use SetItem instead of Add for … (compare)

  • Jul 13 18:23
    Aaronontheweb closed #4512
  • Jul 13 18:23
    Aaronontheweb commented #4512
  • Jul 13 18:22
    Aaronontheweb milestoned #4512
  • Jul 13 18:22
    Aaronontheweb labeled #4512
  • Jul 13 18:22
    Aaronontheweb labeled #4512
Aaron Stannard
@Aaronontheweb
yeah Hyperion isn't used as a default anywhere at the moment
if you're serious about using Akka.Remote or Akka.Cluster in production though
you're better off going with hand-rolled serialization using something that has an explicit scheme like Google.Protobuf
better performance, first and foremost
but more importantly, this type of issue doesn't happen
since you can explicitly control serialization
also makes it easier to version messages on the wire too
Lutando Ngqakaza
@Lutando
we will probably end up there, right now were doing a "large" proof of concept
Aaron Stannard
@Aaronontheweb
we ship with JSON.NET / Hyperion in the future as a default because it's easy to get up and running
but those polymorphic serializers aren't perfect
might have to give them some hints on how to do their job
Lutando Ngqakaza
@Lutando
i see
Jesse Connor
@jesseconnr
I'm having an issue with message delivery in a setup remoting between a windows service and an asp.net site. I'm using an aggreggator to send a large amount of messages to keep the size small, but out of 3500 messages only 1700 or so are making it. In smaller quantities, when there's only a few hundred there's no problems.
My agreggator and the hocon config for the two is here: https://gist.github.com/jesseconnr/256da997b49e38026c32f4bc2987adf5
Aaron Stannard
@Aaronontheweb
are you hitting your receive timeout?
and shutting down?
Jesse Connor
@jesseconnr
Both are on the same machine. I get errors like this Error while decoding incoming Akka PDU of length 28885 but I'm not sure what to make of it.
Aaron Stannard
@Aaronontheweb
ah shit
that's a serialization problem
Jesse Connor
@jesseconnr
Oh the 30 seconds? No I don't think so.
Aaron Stannard
@Aaronontheweb
this is with Hyperion
do you get that issue without it?
and is this on Linux?
Jesse Connor
@jesseconnr
It's on windows.
Aaron Stannard
@Aaronontheweb
so we've had reports of DotNetty fucking up its length-frame encoding
on v0.4.6
originally the reports were Windows-only
err
Linux only
Jesse Connor
@jesseconnr
I send the messages in the same order and tried to figure out if it was a particular one that was having a serialization issue, but the point at which the error occurs seems random.
Aaron Stannard
@Aaronontheweb
had one last week on Windows
no no, this isn't something you're doing wrong
it's DotNetty
Jesse Connor
@jesseconnr
I believe I read that issue, but I think I'm on 0.4.7
Yep, as far as I can tell, DotNetty is all 0.4.7
Aaron Stannard
@Aaronontheweb
v0.4.7 has major issues
like, their API is outright broken there
I've literally never had this issue happen to me on v0.4.6 but other users have reported it
I would strongly, strongly encourage rolling back to v0.4.6
Jesse Connor
@jesseconnr
I was having the issue on 0.4.6 and an older version of akka and upgraded to see if it would fix it and no dice.
Aaron Stannard
@Aaronontheweb
well shucks
can you guys do me a favor and open an issue on the DotNetty github
I don't have a window where I can even look into the issue for another 5 days
you're going to get a faster resolution on it if we can get their org to start looking at the problem
this is not an Akka.NET issue
it's a problem with length-frame encoding not being written or read correctly
Jesse Connor
@jesseconnr
Ah yeah I see the bug report and the mention. I get that same error. DotNetty.Codecs.TooLongFrameException: Adjusted frame length exceeds 128000: 419561476 - discarded
Aaron Stannard
@Aaronontheweb
Azure/DotNetty#360
Jesse Connor
@jesseconnr
hmm, v5 was next week in february, but I guess it never got there
Aaron Stannard
@Aaronontheweb
I have the DotNetty guys on the horn in their gitter now