Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 01:47
    Arkatufus opened #4240
  • 00:10
    Aaronontheweb synchronize #4212
  • Feb 20 23:50
    Aaronontheweb synchronize #4238
  • Feb 20 23:48
    Aaronontheweb commented #4234
  • Feb 20 23:47
    Aaronontheweb synchronize #4212
  • Feb 20 23:46

    Aaronontheweb on dev

    close #4234 - added CachingConf… (compare)

  • Feb 20 23:46
    Aaronontheweb closed #4239
  • Feb 20 23:46
    Aaronontheweb closed #4234
  • Feb 20 23:25
    Aaronontheweb synchronize #4239
  • Feb 20 23:24
    Aaronontheweb opened #4239
  • Feb 20 23:14
    Aaronontheweb commented #4234
  • Feb 20 22:52
    Aaronontheweb commented #4234
  • Feb 20 22:27
    Aaronontheweb synchronize #4212
  • Feb 20 22:27
    Aaronontheweb commented #4238
  • Feb 20 22:24
    Aaronontheweb synchronize #4212
  • Feb 20 21:48
    cptjazz synchronize #4238
  • Feb 20 21:07
    Aaronontheweb labeled #4238
  • Feb 20 20:58
    cptjazz opened #4238
  • Feb 20 20:45
    Aaronontheweb ready_for_review #4212
  • Feb 20 20:45
    Aaronontheweb edited #4212
slc
@slc
^ I keep getting disassociated exception when communicating betweem my MVC site and a background web service
I am resolving the RemoteActor address in the website correctly, and I can Tell the windows service messages correctly, but when I try to send from the windows service back to the website (with Sender.Tell()) I am getting this disassociation error
All latest versions of Akka + Remote and with JSON.NET 9.0.1 as serialiser
*sorry, I mean background Windows Service
Arjen Smits
@Danthar
@slc it looks like you are using localhost in one node and 127.0.0.1 in the other
We had a DNS resolve issue a short while back, which i think is not in the 1.1.1 release
if you change you config on both sides to use 127.0.0.1 that imight help
Stuart Cam
@codebrain
@Danthar - I'll check my HOCON, but I'm pretty sure I had localhost in both
I'll move both to use 127.0.0.1 loopback address
Arjen Smits
@Danthar
Besides that. How have you set up your website ?
the actorsystem needs to be a global singleton
slc
@slc
yup, its on the WebApplication as a static
Arjen Smits
@Danthar
a static reference in the global asax will do, check out the docs for an example.
k
and.. are you 2 persons ?
:P
slc
@slc
:)
different machine and account :)
Arjen Smits
@Danthar
ah
When does the dc happen? Because iis has a habit to recycle the appool which obviously nukes your association.
ah wait, your using sender.tell upon response. so that seems unlikely
slc
@slc
It seems to DA as soon as the delegate for sending the response back completes
So... i init the web site and the service. Website resolves an actor from service and passes it a message with its own actorref
That actorref is held by the service and when an event needs to be passed to the web site it uses the actor ref it was given
Then instantly it shows the Diassociation
The actorref held by the service "looks" correct but trying to tell a message to it causes the problem
Trying to tell a message causes the disassociation
Im a bit stumped
Arjen Smits
@Danthar
thats. odd
slc
@slc
I tried 127.0.0.1 and no luck
Kris Schepers
@schepersk
Hi, what is the best version of Wire to use with akka 1.1.1? Currently references 0.0.6, but 0.7.1 is latest..
Arjen Smits
@Danthar
@schepersk the latest adapter of wire for akka isn't been published yet
Kris Schepers
@schepersk
Owkay, lets keep it on 0.0.6 then..
Arjen Smits
@Danthar
We have a dedicated room for wire questions btw: https://gitter.im/akkadotnet/Wire
not chasing you away though ;)
its something we did a while back.
Kris Schepers
@schepersk
Is there an update planned for Sql-Server persistence to akka 1.1.1 ? We're using that..
:-)
Arjen Smits
@Danthar
it helps with keeping the chat logs focused and helps people find answers to specific questions. As opposed to having everything in one chatroom and disapear in the blackhole that is called gitter chat history.
its being worked on
Kris Schepers
@schepersk
is the current one compatible with the latest sql-common?
or should I just go for the trail and error approach :-)
Arjen Smits
@Danthar
honestly, i have no idea. I use the sqlite integration everywhere for my own solutions.
I think @Silv3rcircl3 or @alexvaluyskiy might have a better idea
Kris Schepers
@schepersk
ic.. that's not really an option for us.. dealing with LOTS of events and projections..
would like to update the cluster out of beta asap :-)
Arjen Smits
@Danthar
i can imagine
1.1.1 is alot better then 1.08
Kris Schepers
@schepersk
so they say :P
Arjen Smits
@Danthar
@Aaronontheweb did an insane amount of work