[akka-user] Re: Akka-Http [Version 10.0.5] OptionalHeaderValueByName & HeaderValueByName does not work for valid Content-Type values

You are right, it is confusing :) After a while I found this in the documenation http://doc.akka.io/docs/akka-http/10.0.4/scala/http/common/http-model.html#http-model, but for me it does not make sense that valid Content-Types are filtered-away and "customized" Content-Types show up. If this

[akka-user] Akka-Http [Version 10.0.5] OptionalHeaderValueByName & HeaderValueByName does not work for valid Content-Type values

Hi! For testing purpose I started an http-endpoint which looks like this ...I removed some code to make it simple object WebServer extends HttpApp { def route: Route = path("publishvalid") { optionalHeaderValueByName("Content-Type") { header => println("Content-Type is

Re: [akka-user] ANNOUNCE: Akka 2.4.0 Released

Hi again! Its not a big deal but I recognized that in contrast to akka 2.3.14 ( http://doc.akka.io/docs/akka/2.3.14/contrib/cluster-sharding.html#Configuration ,http://doc.akka.io/docs/akka/2.4-M1/scala/cluster-sharding.html)

Re: [akka-user] ANNOUNCE: Akka 2.4.0 Released

Currently I try to migrate my project from 2.3.X to 2.4.0. While doing this I recognized that the akka.persistence.PersitenceFailure has been removed and instead an function (onPersitentFailure) is offered where proper action could be taken. In the past (< 2.4.0) we did this by catching the

Re: [akka-user] ANNOUNCE: Akka 2.4.0 Released

Hi Patrik! The new handling make sense to me. We handled the problem a slightly different so far, we used a scheduleOnce and retried to store the message in case a PersistendFailure occurred. The reason we didn't stop the actor is that our PersistendActor is as well a ClusterSingleton and

Re: [akka-user] ANNOUNCE: Akka 2.4.0 Released

://typesafe.com> > > On 1 October 2015 at 13:42:34, Konrad Malawski (konrad@typesafe.com > ) wrote: > > Great catch, thanks Wolfgang! > I'll fix that. > > -- > Cheers, > Konrad `ktoso` Malawski > Akka <http://akka.io> @ Typesafe <http://typesafe.c

Re: [akka-user] ANNOUNCE: Akka 2.4.0 Released

Looking forward to use 2.4.0 :) I just found that in the documentation for the persistence module (http://doc.akka.io/docs/akka/2.4.0/scala/persistence.html#Plugin_TCK ) the include path for the TCK is not correct, it must "com.typesafe.akka" %% "akka-persistence-tck" % "2.4.0" % "test". In

[akka-user] Re: Could you explain idResolver

Well we do have a similar scenario and we do it that way. Simply assigning the name to the persitenceId. val persistenceId: String = self.path.name // userId I guess you mean the idExtractor (idResolver), it could look like this val idExtractor: ShardRegion.IdExtractor = { case

Re: [akka-user] ActorSystem terminates when restarted remote ActorSystem has associated after being quarantined

Even-so on our crashes ( https://groups.google.com/forum/#!searchin/akka-user/disapear/akka-user/QZhDFmrXZaY/_NgOM9O0wmkJ) no quarantine was involved. -- Read the docs: http://akka.io/docs/ Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html Search the

Re: [akka-user] [akka-ClusterSharding 2.3.7/2.3.9] After ClusterShardFailover ShardAllocation gets lost

Here the issue I've created for those how are interested https://github.com/akka/akka/issues/17200 -- Read the docs: http://akka.io/docs/ Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html Search the archives: https://groups.google.com/group/akka-user

Re: [akka-user] [akka-ClusterSharding 2.3.7/2.3.9] After ClusterShardFailover ShardAllocation gets lost

is this the case for ShardRegions? I didn't find anything suspicious in the code of the ShardRegion? So maybe you can enlighten me I'm really curious ;) Regards Wolfgang Am Mittwoch, 15. April 2015 08:01:21 UTC+2 schrieb Wolfgang Friedl: Hi Patrik! I've created an issue for this. Thanks

Re: [akka-user] [akka-ClusterSharding 2.3.7/2.3.9] After ClusterShardFailover ShardAllocation gets lost

Got it! I saw I made a mistake in my sample. When I'm watching an actor on a Node which is leaving the cluster I now got an Terminated message! Thanks for the clarification. -- Read the docs: http://akka.io/docs/ Check the FAQ:

[akka-user] [akka-ClusterSharding 2.3.7/2.3.9] After ClusterShardFailover ShardAllocation gets lost

Hi everyone! We do have the following setup. 4 Nodes of the Cluster 2 Seed-Nodes. I startup all four nodes and wait until the cluster has formed. Afterwards I put some load on our cluster to ensure that the ClusterShard creates shards on all four Nodes. Now I remove the node which hosts the

Re: [akka-user] Re: Confusing problem whilst testing a PushPullStage implementation of a sliding window

Freitag, 20. Februar 2015 09:29:49 UTC+1 schrieb drewhk: Hi Wolfgang, On Thu, Feb 19, 2015 at 7:35 PM, Wolfgang Friedl wolfgan...@hotmail.com javascript: wrote: Hi Endre My publisher is quite simple! It is an actor (extending the ActorPublisher) waiting for incoming messages. He puts

Re: [akka-user] ActorSystem disappear [akka 2.3.8 , 2.3.9]

is causing this? Maybe because internally do many actors are created by akka-stream? Just a wild guess? Regards Wolfgang Am Freitag, 13. Februar 2015 12:35:49 UTC+1 schrieb Wolfgang Friedl: Hi Roland! That's true that might be related to our problem. Now the only open question is what have

Re: [akka-user] Re: Confusing problem whilst testing a PushPullStage implementation of a sliding window

Hi togehter! I observed the same exception ( Input buffer overrun) on my side today. Even so I read this task I'm not sure if I got it right. I do have a Flow were I put some processing steps together with map and mapConcat. I've written the producer for the Flow on my own. The Producer

Re: [akka-user] Re: Confusing problem whilst testing a PushPullStage implementation of a sliding window

. My sink is also an Actor (extending the ActorSubscriber) using the WatermarkRequestStrategy. I do not know what I can do wrong here. Regards Wolfgang Am Donnerstag, 19. Februar 2015 16:53:44 UTC+1 schrieb drewhk: Hi Wolfgang, On Thu, Feb 19, 2015 at 4:47 PM, Wolfgang Friedl wolfgan

Re: [akka-user] Re: Confusing problem whilst testing a PushPullStage implementation of a sliding window

at the Inputbuffer size). As mentioned the producer is a simple Actor pushing message into the flow if requested. Regards Wolfgang Am Donnerstag, 19. Februar 2015 15:28:52 UTC+1 schrieb drewhk: Hi Wolfgang, On Thu, Feb 19, 2015 at 3:24 PM, Wolfgang Friedl wolfgan...@hotmail.com

[akka-user] Akka-Remote frequent Disassociated events

Hi together! We run our application by using the akka-cluster as well akka-remote is used to by external system to connect to our application. At the very begining of our project we had serveral problems regarding gated and quarantined as well inbetween the nodes of the cluster as with the

Re: [akka-user] ActorSystem disappear [akka 2.3.8 , 2.3.9]

ActorSystem while an old JVM silently disappears in its entirety, e.g. by using ømq and encountering a failure). Regards, Roland 29 jan 2015 kl. 14:58 skrev Wolfgang Friedl wolfgan...@hotmail.com javascript:: Update After switching back to Akka 2.3.7 the problem did not occur anymore

Re: [akka-user] ActorSystem disappear [akka 2.3.8 , 2.3.9]

the magical shutdown. /Patrik On Mon, Feb 9, 2015 at 11:51 AM, Wolfgang Friedl wolfgan...@hotmail.com javascript: wrote: Hi Roland! I was out on vacation, so sorry for may delayed response. Its exactly happed like I described. The JVM was still running but the actorsystem was gone of course

[akka-user] Akka.Stream[ 1.0-M1] Flow ignores RequesStrategy

Following Sample: The Producer receives a different demand of elements dependent if the flow does have processing steps or not. (*Consumer uses the WatermarkStrategy(30)*) var flow = Flow.empty[Int]

Re: [akka-user] Akka.Stream[ 1.0-M1] Flow ignores RequesStrategy

of the map directly, while the map will observe the schedule of your consumer. The backpressure protocol is always local between a producer-consumer pair. -Endre On Mon, Dec 22, 2014 at 11:59 AM, Wolfgang Friedl wolfgan...@hotmail.com javascript: wrote: Following Sample: The Producer

Re: [akka-user] Akka.Stream[ 1.0-M1] Flow ignores RequesStrategy

are telling my) which is some overhead especially as I do connect to Flows via Bridge. Regards Wolfgang Am Montag, 22. Dezember 2014 13:32:56 UTC+1 schrieb Akka Team: Hi Wolfgang, On Mon, Dec 22, 2014 at 1:10 PM, Wolfgang Friedl wolfgan...@hotmail.com javascript: wrote: Hi Endre

Re: [akka-user] Akka.Stream[ 1.0-M1] Flow ignores RequesStrategy

this relation is 1:2 (at least this is what my tests are telling my) which is some overhead especially as I do connect to Flows via Bridge. Regards Wolfgang Am Montag, 22. Dezember 2014 13:32:56 UTC+1 schrieb Akka Team: Hi Wolfgang, On Mon, Dec 22, 2014 at 1:10 PM, Wolfgang Friedl

[akka-user] Switch off rebalancing for Cluster Sharding

Hi together! I know its sounds a little bit strange but is it possible to switch of the re balancing-mechanism of the Cluster-Shard by eg. setting the rebalance-interval to some infinite value, or could even than a re-balance happen when a new node is added to the Cluster. In our setup it

[akka-user] Cluster-Shard Rebalancing of persistent actors

Hi together! The actors created by our cluster-shard are persistent-actors. Currently we have implemented an graceful shutdown mechanism (by using the gracefulshutdown function form Akka) which sends a customized message to our actors giving them time to shutdown gracefully, which in our case