Hi Roland,

Thanks for the response. Unfortunately can't migrate to 2.2.3 because of 
this issue

https://groups.google.com/forum/#!searchin/akka-user/fowler/akka-user/I-rqfGbq7UE/Yd_DO3NxjZ8J

https://www.assembla.com/spaces/akka/tickets/3860

Remote systems seem to lose connectivity in 2.2.3 and not recover.

Brian


On Tuesday, 11 February 2014 12:25:39 UTC, Akka Team wrote:
>
> Hi Brian,
>
> the old remoting in Akka 2.1.x used a lock to protect the map which holds 
> the connection information, which might be to blame here; the remoting 
> layer was completely rewritten using actors for 2.2. Can you upgrade to 
> 2.2.3 to see if that fixes the issue? (or if you can spare the time, it 
> would be awesome if you could try 2.3.0-RC2 which will hopefully turn final 
> next week)
>
> Regards,
>
> Roland
>
>
>
> On Tue, Feb 11, 2014 at 11:51 AM, Brian Fowler 
> <[email protected]<javascript:>
> > wrote:
>
>> Hi,
>>
>> In Akka 2.1.4 I'm seeing the following behaviour. We have a set of actor 
>> systems on different boxes in the following configuration.
>>
>> ActorSystemA (Actor 1)
>>                                          -
>>                                            |
>>                                            _
>>                                              > 
>>                                                   ActorSystemC (Actor 
>> 3)                <-->                   ActorSystemD (Actor 4)  
>>                                           _>
>>                                           |
>> ActorSystemB (Actor 2)  -
>>  
>>
>>
>> If ActorSystem B dies it is causing timeouts between actor system C and D 
>> for a short period which I don't understand. They are not proper timeouts 
>> i.e. the timeout has not elapsed it's being triggered early and actorSystem 
>> D is up and responding I.e.
>>
>>
>>  
>> ActorSystemA (Actor 1)
>>                                        -
>>                                          |
>>                                           _
>>                                              > 
>>                                                  ActorSystemC (Actor 3) 
>> <- TIMEOUT! -> ActorSystemD (Actor 4) 
>>                                                                              
>>       
>>
>>                                           
>> *ActorSystemB (Actor 2)* (DEAD) 
>>
>>
>> I've worked round it by creating a second actor system in the JVM that 
>> actorSystem C is on that is just used to obtain a remote actor ref to actor 
>> 4 on ActorSystem D which prevents this behaviour happening. Has anyone else 
>> seen this behaviour? Is there a better way to prevent this happening?
>>  
>> Appoloigies for the diagrams, I originally had images but my company is 
>> blocking attachments to google groups :S
>>
>> Thanks,
>>
>> Brian
>>  
>> -- 
>> >>>>>>>>>> Read the docs: http://akka.io/docs/
>> >>>>>>>>>> Check the FAQ: http://akka.io/faq/
>> >>>>>>>>>> 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] <javascript:>.
>> To post to this group, send email to [email protected]<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> Akka Team
> Typesafe - The software stack for applications that scale
> Blog: letitcrash.com
> Twitter: @akkateam
>  

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: http://akka.io/faq/
>>>>>>>>>>      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/groups/opt_out.

Reply via email to