#2697
- Created on2012-11-11 01:52
- Reported by
- StatusFixed
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
After remote connect, system waits on execution-pool-keepalive before full shutdown
NettyRemoteTransport.PipelineFactory.executionHandler hangs at shutdown until the execution-pool-keepalive timeout passes.
This issue can be prevented by explicitly releasing the executionHandler in NettyRemoteTransport.shutdown() after releasing clientChannelFactory.
clientChannelFactory.releaseExternalResources()
PipelineFactory.executionHandler foreach { _.releaseExternalResources() }
The initial discusson on this is here: https://groups.google.com/forum/?fromgroups=#!topic/akka-user/Jv8rwsEIXKc
I separated this from my modifications for NAT (described in the mailing list) and now I think it may be an issue in the vanilla version of akka-2.1-RC1. This occurs if one sends a message to a remote actor system or if a lone system tries to send a message to a non-existant ip/port.
This issue can be prevented by explicitly releasing the executionHandler in NettyRemoteTransport.shutdown() after releasing clientChannelFactory.
clientChannelFactory.releaseExternalResources()
PipelineFactory.executionHandler foreach { _.releaseExternalResources() }
The initial discusson on this is here: https://groups.google.com/forum/?fromgroups=#!topic/akka-user/Jv8rwsEIXKc
I separated this from my modifications for NAT (described in the mailing list) and now I think it may be an issue in the vanilla version of akka-2.1-RC1. This occurs if one sends a message to a remote actor system or if a lone system tries to send a message to a non-existant ip/port.
Leave a comment
on 2012-11-11 04:24 *
By cessationoftime
I meant to put the pull request above in my other ticket. It is for the NAT modifications I was working on when I found this timeout problem.
on 2012-12-21 15:00 *
By rkuhn
Assigned to changed from cessationoftime to -none-
Status changed from Test to New
This issue fell through the cracks since the patch was not in fact in the pull request cited above, and that pull request was closed due to not being of general interest (see the comments there). Sorry about this, the one-line fix will have to be vetted after 2.1.0 and then go into 2.1.1 (if found okay).
on 2013-02-19 15:31 *
By bjorn.antonsson@typesafe.com
Assigned to set to bjorn.antonsson@typesafe.com
This doesn't exist in the new remoting so no need to forward port.