Re: [akka-user] Re: one more issue in migration ..

2016-07-19 Thread Debasish Ghosh
Hi Johan - Yes, Source.empty was the problem. Replacing it with Source.maybe fixed it. Will check the halfClosed property that u suggested as well. Thanks. On Tue, Jul 19, 2016 at 12:38 PM, Johan Andrén wrote: > Hi Debashish, > > I'd guess it is because of the Source.empty which will complete

[akka-user] Re: one more issue in migration ..

2016-07-19 Thread Johan Andrén
Hi Debashish, I'd guess it is because of the Source.empty which will complete the outgoing stream, there is a halfClosed property you can set when binding to allow the socket to stay alive even after the writing side close. -- Johan On Saturday, July 16, 2016 at 11:20:50 AM UTC+2, debasish wro

[akka-user] Re: one more issue in migration ..

2016-07-16 Thread debasish
Just to give some more context on the error that I get .. I get the following when the client side connects to this service .. [INFO] [07/16/2016 14:46:40.274] [front_office-akka.actor.default-dispatcher-2] [akka://front_office/system/IO-TCP/selectors/$a/0] Message [akka.io.Tcp$Write] from Ac