[akka-user] Re: Akka Remoting Failures with Amazon EC2

Hi Ashvin, I want to deploy my app into Amazon. Where you able to successfully deploy your app into amazon? If yes, can you share me your experience and steps you followed. Also would like to understand how deployment in amazon differs from deploying app locally. Do we have to change any confi

Re: [akka-user] Akka 2.3.4- Cluster Aware Custom Router

On Tue, Aug 12, 2014 at 7:08 AM, tomerneeraj wrote: > Hi Patrik, > > Thanks for your response > > As of now we are working in design phase and after going through > documentation we thought to have multi-threaded router in case of cluster > aware router also. As per our point of view it can alway

[akka-user] reading and writing moderately sized xml (and other) files

My application occasionally needs to read and write files. Specifically I've got a file store of data project files - each one of which is maybe 10mb of xml with possibly an accompanying 2-3 mb of csv. The xml is currently being read with scala XML.loadFile(fileName) and the csv is being loaded i

Re: [akka-user] how to tune akka remoting performance

Thanks, Patrik, That may points to the right direction. After adding some metrics, the latency of akka remoting is extremely high, on average, it tooks *0.3s* to travel from one JVM to another JVM!!! message receive latency (ms): count = 2743521 min = 237

[akka-user] Handling Exception in Akka

I have a master worker public class EmailServiceActor extends UntypedActor{ ActorRef actorRef ; private static SupervisorStrategy strategy = new OneForOneStrategy(3, Duration.create("1 minute"), new Function() { @Override public Directive apply(

[akka-user] Stopping a child worker after its work is done

I have a parent Actor class called MainActor and a child actor called HelloLocalActor public class MainActor extends UntypedActor{ ActorRef actorRef ; @Override public void onReceive( Object me

Re: [akka-user] Akka 2.3.4- Cluster Aware Custom Router

Hi Patrik, Thanks for your response As of now we are working in design phase and after going through documentation we thought to have multi-threaded router in case of cluster aware router also. As per our point of view it can always improve the performance without any side effect Very soon we

Re: [akka-user] Shared callback object between actors is a good practice ?

OK.. Thank you Patrik, I think it will be safe to go with the first solution for my use case. On Monday, 11 August 2014 16:14:56 UTC+1, Patrik Nordwall wrote: > > If the callback instance is a "stateless thread-safe service" it would be > safe to share it between actor instances, otherwise you

Re: [akka-user] Re: akka.remote.ResendUnfulfillableException:

Alright, please update to 2.3.4 and report back. /Patrik > 11 aug 2014 kl. 20:40 skrev ryan walsh : > > using 2.3.0 > >> On Monday, August 11, 2014 10:28:06 AM UTC-5, ryan walsh wrote: >> I saw a previous thread post saying that this may be a defect, but nothing >> came of the thread. >> >> O

[akka-user] Re: akka.remote.ResendUnfulfillableException:

using 2.3.0 On Monday, August 11, 2014 10:28:06 AM UTC-5, ryan walsh wrote: > > I saw a previous thread post saying that this may be a defect, but nothing > came of the thread. > > Over the weekend, my server crashed due to OutOfMemoryException. Upon > restarting it, I am receiving this exceptio

Re: [akka-user] Event Sourcing Single Writers

I forgot that sagas are also discussed (briefly) in CAP Twelve Years Later . And it mentions (besides the Sagas paper) http://www.vldb.org/conf/1990/P095.PDF. On Sunday, August 10, 2014 9:39:02

Re: [akka-user] Akka 2.3.4- Cluster Aware Custom Router

Hi Neeraj, On Mon, Aug 11, 2014 at 11:27 AM, tomerneeraj wrote: > Hi, > > We are building app using Akka in cluster environment. We can see system > can be scaled in proportion of number of routees depends on the hardware > sizing. As documented in official documentation routers can be bottlen

Re: [akka-user] Re: akka.remote.ResendUnfulfillableException:

Which version of Akka are you using? On Mon, Aug 11, 2014 at 5:42 PM, ryan walsh wrote: > I am using a clusterclient to communicate between a remote cluster and > this app. The remote cluster pulls from JMS and send messages to this > cluster, and awaits to acknowledge the message off the JMS q

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Does it change anything if use another (default) dispatcher for the circuit breaker and the futures? /Patrik > 11 aug 2014 kl. 17:56 skrev Leonard Meyer : > > Anything blocking I put on a pinned dispatcher. So each FileProcessor and the > Controller (which sometimes does JDBC). Each FileProce

[akka-user] Re: Akka Cluster is shutting down after upgrading to Play 2.3.2

Thanks Michael - your suggestions worked well! And sorry for the delayed response - got stuck in BTN. Thanks, Mani On Thursday, August 7, 2014 7:53:55 PM UTC+8, Michael Pisula wrote: > > Just verified, the method Closable.closeQuietly was deprecated since at > least guava 14, and was removed

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Anything blocking I put on a pinned dispatcher. So each FileProcessor and the Controller (which sometimes does JDBC). Each FileProcessor also has a CircuitBreaker which uses the same pinned dispatcher as said FileProcessor. Is there something wrong with this ? 2014-08-11 17:34 GMT+02:00 Patrik

[akka-user] Re: akka.remote.ResendUnfulfillableException:

I am using a clusterclient to communicate between a remote cluster and this app. The remote cluster pulls from JMS and send messages to this cluster, and awaits to acknowledge the message off the JMS queue. On Monday, August 11, 2014 10:28:06 AM UTC-5, ryan walsh wrote: > > I saw a previous thre

Re: [akka-user] [akka-stream] Delayed retry

Hi Patrik, In own solution, which we use currently, we requeue the message in rabbitmq, so that it will be reappear again in a stream. Each message has deliveryTag (identifier) by which we can do "channel.nack(deliveryTag)" in case of failure Ideally, for my case it would be useful if: 1. I ca

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

What dispatcher do you use for what? You mentioned pinned dispatcher, but you also have context.dispatcher for the circuit breaker. Pinned dispatcher there is probably not a good idea since the actor is blocking (the thread is busy). You also have futures, e.g. mapTo. /Patrik On Mon, Aug 11, 201

[akka-user] akka.remote.ResendUnfulfillableException:

I saw a previous thread post saying that this may be a defect, but nothing came of the thread. Over the weekend, my server crashed due to OutOfMemoryException. Upon restarting it, I am receiving this exception repeatedly. Any idea how to handle / clear this? 08/11/2014 10:22:11,857 ERROR [Comm

Re: [akka-user] Shared callback object between actors is a good practice ?

If the callback instance is a "stateless thread-safe service" it would be safe to share it between actor instances, otherwise your second more idiomatic approach sounds good. /Patrik On Sun, Aug 10, 2014 at 1:58 PM, lranasingha wrote: > Hi All, > I have a java client which is implemented to st

Re: [akka-user] [akka-stream] Delayed retry

понедельник, 11 августа 2014 г., 17:58:04 UTC+4 пользователь √ написал: > > > > > On Mon, Aug 11, 2014 at 3:53 PM, Evgeniy Ostapenko > wrote: > >> Ok:) But will Producer have the StreamSettings or not: >> 1) Any Stream of elements, emitting by Producer, has a lot of properties. >> > > A Producer

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Yes, all I have is at the beginning where it's basically saying who's supervising who. And I have : [DEBUG] [08/11/2014 16:36:41.977] [akka.actor.default-dispatcher-2] [akka:///user] now supervising Actor[akka://x/user/connectionFactory#608280561] connectionFactory is the name of my datas

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Did you enable lifecycle logging? On Mon, Aug 11, 2014 at 4:22 PM, Jasper wrote: > Well, given what I said before, pretty sure yes. And yes the sender() > doesn't receive anything so it times out and the circuit breaker keep on > doing the Open/HalfOpen circle. Here are some sample logs >

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Well, given what I said before, pretty sure yes. And yes the sender() doesn't receive anything so it times out and the circuit breaker keep on doing the Open/HalfOpen circle. Here are some sample logs This is annoying, I don't know if I'm doing something wrong wit

Re: [akka-user] [akka-stream] Delayed retry

On Mon, Aug 11, 2014 at 3:53 PM, Evgeniy Ostapenko wrote: > Ok:) But will Producer have the StreamSettings or not: > 1) Any Stream of elements, emitting by Producer, has a lot of properties. > A Producer is already configured. > 2) You need to set them? I think of course yes. > Yes, depending

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Hi Jasper, It wasn't dumb at all. So are you sure that it doesn't blow up, because that would mean that the sender() of GetConnection never gets his/her connection. Right? On Mon, Aug 11, 2014 at 3:51 PM, Jasper wrote: > Quick and dirty modification but indeed, that was dumb. > > Le lundi 11 a

Re: [akka-user] [akka-stream] Delayed retry

Ok:) But will Producer have the StreamSettings or not: 1) Any Stream of elements, emitting by Producer, has a lot of properties. 2) You need to set them? I think of course yes. 3) This properties linked with Producer of that stream (one to one)? I think yes. 4) It is good to link properties of str

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Quick and dirty modification but indeed, that was dumb. Le lundi 11 août 2014 15:47:58 UTC+2, √ a écrit : > > Unrelated but why the complication of > > sender() ! datasource.map(ds => ds.getConnection).get > > iso > > sender() ! datasource.get.getConnection > > > On Mon, Aug 11, 2014 at 3:44 PM,

Re: [akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Unrelated but why the complication of sender() ! datasource.map(ds => ds.getConnection).get iso sender() ! datasource.get.getConnection On Mon, Aug 11, 2014 at 3:44 PM, Jasper wrote: > Spent some time today on this... Actually when I turn on autocommit and > crash the DB, processors do block

[akka-user] Re: Actors behaving unexpectedly with Circuit breaker

Spent some time today on this... Actually when I turn on autocommit and crash the DB, processors do block but they ALL go into Open state, which is good. But for some reason my actor holding the datasource isn't responding anymore and I end up with this when asking for a connection : akka.patte

Re: [akka-user] how to tune akka remoting performance

Hi, Unfortunately, the only test I'm aware of is: https://github.com/akka/akka/tree/v2.3.4/akka-samples/akka-sample-remote-scala/src/main/scala/sample/remote/benchmark We have only used it for add-hoc testing. You can find some results of running it here: https://groups.google.com/d/msg/akka-dev/

Re: [akka-user] [akka-stream] Delayed retry

On Mon, Aug 11, 2014 at 3:22 PM, Evgeniy Ostapenko wrote: > No, I mean each _Producer_ must have the StreamSettings, not _Flow_. > _Stream_ settings depends on Producer properties ( how and from, you take > next element) and not depends on what you doing with that stream/elements > after. > No,

Re: [akka-user] [akka-stream] Delayed retry

No, I mean each _Producer_ must have the StreamSettings, not _Flow_. _Stream_ settings depends on Producer properties ( how and from, you take next element) and not depends on what you doing with that stream/elements after. понедельник, 11 августа 2014 г., 16:44:58 UTC+4 пользователь √ написал:

Re: [akka-user] [akka-stream] Delayed retry

On Mon, Aug 11, 2014 at 1:22 PM, Evgeniy Ostapenko wrote: > Flow(() => getOneMoreElement(), StreamSettings(startAt = 1.second, cutoff > = 100.seconds, handleExceptionStrategy = LogOnly, ... any other > settings...)) > > In my mind each stream have settings defined by it nature. I was > discussing

Re: [akka-user] Periodic "Disassociated" with remote system

On Mon, Aug 11, 2014 at 6:21 PM, Patrik Nordwall wrote: > Hi Caoyuan, > > Do you see the same thing with Akka version 2.3.4 and changing > the transport-failure-detector settings to default? > Will try. But I don't see any relevance source changes between 2.3.3 and 2.3.4 > > Regards, > Patrik

Re: [akka-user] [akka-stream] Delayed retry

Flow(() => getOneMoreElement(), StreamSettings(startAt = 1.second, cutoff = 100.seconds, handleExceptionStrategy = LogOnly, ... any other settings...)) In my mind each stream have settings defined by it nature. I was discussing with *drewhk* about this https://groups.google.com/forum/?hl=ru#!to

Re: [akka-user] [akka-stream] Delayed retry

On Mon, Aug 11, 2014 at 12:33 PM, Evgeniy Ostapenko wrote: > A lot of options will require a lot of methods in such case. May be better > add StreamSettings parameter to the Producer and use it whenever you need > it? > I'm not sure I understand what you mean, could you elaborate/example? > >

Re: [akka-user] [akka-stream] Delayed retry

A lot of options will require a lot of methods in such case. May be better add StreamSettings parameter to the Producer and use it whenever you need it? понедельник, 11 августа 2014 г., 13:56:23 UTC+4 пользователь √ написал: > > One idea is to wrap a Publisher-creator with retry semantics: > >

Re: [akka-user] Periodic "Disassociated" with remote system

Hi Caoyuan, Do you see the same thing with Akka version 2.3.4 and changing the transport-failure-detector settings to default? Regards, Patrik On Sun, Aug 10, 2014 at 6:08 PM, Caoyuan wrote: > We have an akka cluster with 10 nodes. it works almost smoothly except > periodic firing "Disassoci

Re: [akka-user] [akka-stream] Delayed retry

One idea is to wrap a Publisher-creator with retry semantics: retry(() => openFileForRead(...), policy = exponentialBackoff(startAt = 1.second, cutoff = 100.seconds)) Other ideas? On Mon, Aug 11, 2014 at 11:51 AM, Patrik Nordwall wrote: > Hi Viktor, > > On Sat, Aug 9, 2014 at 6:53 PM, Vik

Re: [akka-user] [akka-stream] Delayed retry

Hi Viktor, On Sat, Aug 9, 2014 at 6:53 PM, Viktor Taranenko wrote: > Hi guys, > > I've just started investigating akka stream module. > > My use case is wrapping RabbitMQ worker queue with akka-stream (0.4). And > there might be many steps which required IO in a Flow. Potentially I could > put a

[akka-user] Akka 2.3.4- Cluster Aware Custom Router

Hi, We are building app using Akka in cluster environment. We can see system can be scaled in proportion of number of routees depends on the hardware sizing. As documented in official documentation routers can be bottleneck as some point of time so custom router is documented very well to overc

Re: [akka-user] Improving Akka Persistence wrt CQRS/ES/DDD

Hi Vaughn, When can we expect "Building a Reactive Process Manager, Twice" implementation working both in Scala with Akka into the github? On Monday, 11 August 2014 03:27:05 UTC+5:30, Vaughn Vernon wrote: > > None of this stuff is easy to do, and even harder to do right. Your post > gives away

Re: [akka-user] akka-persistence (2.3.4) and serialization

Hi Michael, yes, the TCK is not published yet – it will be as part of the 2.3.5 release. If you would like to use it before that you can publishLocal from the akka-persistence-tck-experimental project from the release-2.3 branch. Good luck with your plugin! On 11 August 2014 at 08:29:22, Michael