[akka-user] Re: remote akka problem - not able to communicate

Thanks to all, Problem got solved. mistake was transport = "akka.remote.netty.NettyRemoteTransport" it should be akka.remote.netty.NettyTransport" Thanks a lot!! On Tuesday, November 25, 2014 12:22:36 PM UTC+5:30, Suman Adak wrote: > > Dear All, > > I have some problem with remote akka. > >

Re: [akka-user] Akka Streams - Chunked Encoding

I am not completely sure, but the dead letters are probably nothing to worry about. I had a similar experience when I played around with it a few weeks ago. See this thread: https://groups.google.com/d/topic/akka-user/4ybCq7mEp4g/discussion On Wed, Nov 26, 2014 at 11:52 PM, Paul Cleary wrote: > U

Re: [akka-user] Akka Streams - Chunked Encoding

Using a CURL, I do seem to get some data going down, it does the concatenation. < HTTP/1.1 200 OK > > * Server akka-http/2.3.7 is not blacklisted > > < Server: akka-http/2.3.7 > > < Date: Wed, 26 Nov 2014 22:50:32 GMT > > < Transfer-Encoding: chunked > > < Content-Type: application/x-gzip > > <

Re: [akka-user] Akka Streams - Chunked Encoding

It seems to me that you are gzip-compressing each file individually. So the result of your request will be the concatenation of multiple gzipped files, which does not make any sense. You should get some data though. Have you tried testing with wget or curl? On Wed, Nov 26, 2014 at 11:27 PM, Paul

[akka-user] Akka Streams - Chunked Encoding

I am trying to created a chunked response from a series of files on the file system. I am using the Test Server code as the basis. Here is my sample code: val requestHandler: HttpRequest ⇒ HttpResponse = { case HttpRequest(GET, Uri.Path("/"), _, _, _) ⇒ val dir = "/test-data/"

[akka-user] Using a BalancingPool with PriorityGenerator

Hi I am trying to get a balancing pool working in conjunction with a priority mailbox (eg using the PriorityGenerator) I expected the following to work : context.actorOf(BalancingPool(5).withDispatcher("prio-dispatcher").props(Props(new Actor))) but it seems that the PriorityGenerator never

[akka-user] Re: remote akka problem - not able to communicate

there is no NettyRemoteTransport but NettyTransport 在 2014年11月25日星期二UTC+8下午2时52分36秒，Suman Adak写道： > > Dear All, > > I have some problem with remote akka. > > I'm trying to create one akka remote actor node and connect it from a > different machine. I opened > the port 2551,2552,2553 ports of bo

Re: [akka-user] Akka stream throttle the transmission bandwidth

Looks like you got some advice over at akka-dev: https://groups.google.com/d/msg/akka-dev/piuPD8xSnpM/E6E8nBUCrecJ /Patrik On Tue, Nov 25, 2014 at 1:40 PM, Nicolas Jozwiak wrote: > Hello, > > I’m currently using akka stream 0.11 to process some big files and > I want to throttle the trans

Re: [akka-user] remote akka problem - not able to communicate

Hard to say what can be wrong. Firewall? What do you see in the logs? You can also try to run with akka.loglevel=DEBUG Regards, Patrik On Tue, Nov 25, 2014 at 7:52 AM, Suman Adak wrote: > Dear All, > > I have some problem with remote akka. > > I'm trying to create one akka remote actor node an

Re: [akka-user] Design question on with akka persistence

On Wed, Nov 26, 2014 at 1:20 PM, wrote: > Thanks a lot. My question was more on the pattern of creating and poison > pilling a new PersistentView for each request. Since the query optimized > view of mine changes a lot on request params. Is it the right way to do it? > Depends on how many events

Re: [akka-user] Re: Trying to figure out why all threads for a dispatcher will block at the same time consistently

Glad to hear that you found the problem. You might want to use the Akka async logging API and/or try the Logback AsyncAppender . Regards, Patrik On Wed, Nov 26, 2014 at 11:17 AM, Martynas Mickevičius < martynas.mickevic...@typesafe.com> w

Re: [akka-user] Re: how to control number of threads started by a RoundRobin worker.

Glad to hear that. /Patrik On Tue, Nov 25, 2014 at 8:52 PM, Hector123 wrote: > I got this resolved , it was an error with the configuration json object. > here is the correct setting > > akka { > actor{ > default-dispatcher { > type = Dispatcher > executor = "thread-pool-executor" >

Re: [akka-user] Akka streams - stability

We’ll announce when it’s “stable stable” ;-) No huge changes planned, but there still may be a few here and there. Issue tracker is github, as for the rest of Akka as well:  https://github.com/akka/akka/issues?q=is%3Aopen+is%3Aissue+label%3At%3Astream Happy hakking! --  Konrad 'ktoso' Malawski h

[akka-user] Akka streams - stability

What is the status of Akka streams? Are there major changes on the roadmap or the API is stable? Where can I find a bugtracker of Akka streams? Best, Maciej -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/add

Re: [akka-user] testing akka cluster on Blue Waters @ NCSA

On Tue, Nov 25, 2014 at 9:35 PM, Nidhi wrote: > Thank you Patrik, we are restricting the sender to send lesser queries > now. > Sounds good. > Could you tell us what exactly is to be used from the fix ? We have akka > 2.3.6. > There is nothing you need to enable to use the improvements, apart

Re: [akka-user] Design question on with akka persistence

Thanks a lot. My question was more on the pattern of creating and poison pilling a new PersistentView for each request. Since the query optimized view of mine changes a lot on request params. Is it the right way to do it? On Monday, November 24, 2014 4:10:27 AM UTC+5:30, Andrew Easter wrote: > >

Re: [akka-user] akka http+streams applying TCP backpressure

Hi Joe, There is a configuration section for the underlying IO stuff: # The maximum number of bytes delivered by a `Received` message. Before # more data is read from the network the connection actor will try to # do other work. akka.io.tcp.max-received-message-size = unlimited (see http

Re: [akka-user] akka http+streams applying TCP backpressure

Thanks, sounds like I must be doing something wrong. This isn't a huge priority right now, so I'll probably worry about it later. The situation is that I have an app streaming a (potentially large) request in from a client and forwards it on to another downstream application. I made a test (ru

Re: [akka-user] Re: Trying to figure out why all threads for a dispatcher will block at the same time consistently

Great investigative work! Thanks for letting us know what was the problem. On Wed, Nov 26, 2014 at 5:22 AM, Soumya Simanta wrote: > I stand corrected. The blocking is not happening at Unsafe.park but the > following > > ch.qos.logback.core.AppenderBase.doAppend(Object) AppenderBase.java:64 > ch.

Re: [akka-user] Akka actors not processing messages after a while

Hi Yogesh, what do you see in your server logs? Try to set log level to eleven, I mean DEBUG, and check if you see something out of the ordinary. How fast messages are processed in the backend? Do you do blocking there? Do you use Await? No