Just an idea: you can actually form cycles
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0-M2/scala/stream-graphs.html#Graph_cycles__liveness_and_deadlocks
in
the Flow graph, which you can use to feedback acknowledgments.
On Sun, Jan 18, 2015 at 2:18 AM, Evan Chan vel...@gmail.com
Hi Sebastiaan,
there is nothing special in PoisonPill in the sense that you can always
implement one of your own.
Currently there is no way for an actor to choose not to swallow a
PoisonPill. This is why it was not reintroduced in the new akka-typed
module. This is probably what Heiko was
Hi Marco,
Please upgrade to 2.3.9 if you haven't already, there was a couple of
remoting-related issues fixed there.
On Wed, Jan 21, 2015 at 6:45 PM, Marco Luca Sbodio marco.sbo...@gmail.com
wrote:
I haven't.
I've managed to figure out that sometimes the following code
[[
I haven't.
I've managed to figure out that sometimes the following code
[[
int nextStepNumber = planSteps[0].getStepNumber();
Address nextAddress = planSteps[0].getPeer().getAddress();
PlanStep[] nextPlanSteps = new PlanStep[planSteps.length];
Hi Johannes,
See the milestone here:
https://github.com/akka/akka/issues?q=milestone%3A2.3.9+is%3Aclosed
The tickets cross reference the PRs, too, so you can look at the code
changes. The issue that probably hit you is
https://github.com/akka/akka/issues/16623 which manifested as system
message
Hi Sam,
you can use custom event listener to display the log messages that you are
interested in.
Here
https://github.com/2m/akka-remote-sandbox/blob/03b4eaaa1778fe3d44b7889b3d0c6a63c342b1a1/src/main/scala/LogMessages.scala
you
can find a simple example demonstrating that. And there is a
Upgrading to 2.3.9 does indeed seem to solve my problem. At least I haven't
experienced them yet.
Now I'm curious what the fixes were, is there somewhere a change summary
between versions or where is it listed what bugs have been fixed in which
versions?
On Wednesday, January 21, 2015 at
I have a slightly different approach (due to different requirements):
When the actor in question starts up, I do a check in onRecoveryCompleted.
If a certain field is empty, it means I have not yet received some
information from the external system. Then I start a new sequence of
retries
Hi Johannes,
see the news item: http://akka.io/news/2015/01/19/akka-2.3.9-released.html
On Wed, Jan 21, 2015 at 4:47 PM, Johannes Berg jberg...@gmail.com wrote:
Upgrading to 2.3.9 does indeed seem to solve my problem. At least I
haven't experienced them yet.
Now I'm curious what the fixes
Hi,
you can not run one ActorSystem on multiple nodes, however you can run a
cluster of ActorSystems on multiple nodes. Take a look at Cluster Sharding
http://doc.akka.io/docs/akka/2.3.9/contrib/cluster-sharding.html. It
seems it can help you in this particular case.
On Mon, Jan 5, 2015 at 11:36
You could also use slf4j logger and define the filter in the logback config (or
whatever impl you prefer).
An alternative; use grep/egrep to filter out the relevant information from the
log file after the fact.
/Patrik
21 jan 2015 kl. 17:29 skrev Martynas Mickevičius
I have setup cluster of 2 nodes using following config
akka {
log-dead-letters = 10
log-dead-letters-during-shutdown = on
actor {
provider = akka.cluster.ClusterActorRefProvider
}
remote {
log-remote-lifecycle-events = off
netty.tcp {
hostname = 127.0.0.1
Hey!
I have a stream that process incoming messages, assemble big message pack
and send it to other system via network. Incoming messages are relatively
small and I use big buffers to improve throughput for all stages related to
these small messages. At the very end of stream I have message
Hi all,
It's an exciting time for Akka with the imminent release of akka-http (as
announced
in 2013 in this thread
https://groups.google.com/forum/#!searchin/akka-user/Akka-HTTP/akka-user/sMB8tjYPOLA/ywU2G9baqwgJ
and more recently reaffirmed in this other thread
Thanks, I came up with the following, but I have some questions:
/**
* Holds elements of type A for a given finite duration after a predicate
p first yields true and as long as subsequent
* elements matching that first element (e.g. are equal) still satisfy
the predicate. If a matching
Update, in a simple test scenario like so
val ticks = Source(1 second, 1 second, () = Hello)
val flow = ticks.transform(() = new FilterFor[String](10 seconds)(x =
true)).to(Sink.foreach(println(_)))
flow.run()
I'm seeing the following error, so this doesn't work at all and I'm not
Hi Sebastiaan,
As Martinas pointed out (and I tried to tell in London) you should define some
ShutMeDownGracefully (replace this exemplary name with one matching the
context) message for each actor which needs graceful shutdown and implement the
specific behavior which might vary (not every
Hi,
Thanks for your explanations. I've also found link you provided (long
running projects one) and looks like promotion is what suits me the most in
this particular case. I can also combine it with journal implementation
(which I somehow missed during my learning process). Being able to inject
Hi,
What about other custom headers: X-Forwarded-For, SOAPAction, etc? How can
I add them to the request?
W dniu czwartek, 8 stycznia 2015 09:26:11 UTC+1 użytkownik André napisał:
Hi Marcin,
the user agent string is a config property and configured here
Hi Sam,
On Tue, Jan 20, 2015 at 9:56 PM, Sam Halliday sam.halli...@gmail.com
wrote:
One more comment on the streams API. It is really cool that you've thought
about using mapConcat instead of flatMap to enable optimised merge
operations. I just wanted to draw your attention to a clojure
Err, Endre, yes. And when merging Seq[T] in a mapConcat we would all
benefit greatly from faster merging, Seq[Seq[T]] = Seq[T]
On 21 Jan 2015 08:03, Endre Varga endre.va...@typesafe.com wrote:
Hi Sam,
On Tue, Jan 20, 2015 at 9:56 PM, Sam Halliday sam.halli...@gmail.com
wrote:
One more
On Wed, Jan 21, 2015 at 9:45 AM, Sam Halliday sam.halli...@gmail.com
wrote:
Err, Endre, yes. And when merging Seq[T] in a mapConcat we would all
benefit greatly from faster merging, Seq[Seq[T]] = Seq[T]
What do you mean? I don't understand. What mapConcat does is that it takes
a Source[T] and
Hi Johannes,
We just released 2.3.9 with important bugfixes. I recommend to update and
see if the problem is still persisting.
-Endre
On Wed, Jan 21, 2015 at 10:29 AM, Johannes Berg jberg...@gmail.com wrote:
Many connections seem to be formed in the case when the node has been
marked down
Many connections seem to be formed in the case when the node has been
marked down for unreachability even though it's still alive and it tries to
connect back into the cluster. The removed node prints:
Address is now gated for 5000 ms, all messages to this address will be
delivered to dead
Hi Sam,
Bjorn asked if I felt any examples were missing, and sadly my
original request (that I've been going on about for years,
sorry!) is indeed missing. It is the case of a fast producer and
a slow consumer that is ideal for parallelisation.
There are many examples of slow consumers,
It's the wording with merge being the preferred strategy. From your email
it is clear that merge is *not* the strategy used in Akka streams, so
perhaps best to drop this sentence as it confuses more than clarifies.
Instead, it would be instructive to note that a Source is returned and
perhaps talk
Yea my first intuition was to go with Hazelcast,
I'll check the alternatives first though
Thanks folks!
On Wednesday, January 21, 2015 at 9:29:06 AM UTC+2, Ngoc Dao wrote:
Not related to Akka, but you should try Hazelcast:
http://hazelcast.org/
Hazelcast is designed for this problem.
Hi,
I'm trying to implement persistence of entries (as in their presence not
their data) in a ClusterSharding based system. For the moment I have a
persistent ClusterSingleton that creates all entries, so that in the
event of a full cluster restart every running entries would be
re-created (by
Hi,
Just to clarify: are you proposing an actor/application with the sole
purpose of converting messages from old version to new version, or that the
existing application with its actors should support multiple versions of
the messages?
On Tuesday, January 20, 2015 at 1:08:38 PM UTC+1, rkuhn
The RequestBuilding trait is currently only used in tests.
you can use the methods on HttpMessage with RawHeaders instead:
HttpRequest(GET, /some/address.json)
.withHeaders(
RawHeader(X-Forwarded-For, ...),
RawHeader(SOAPAction, ...),
...)
On Wednesday, January 21, 2015 at
Thanks.
W dniu środa, 21 stycznia 2015 13:18:37 UTC+1 użytkownik André napisał:
The RequestBuilding trait is currently only used in tests.
you can use the methods on HttpMessage with RawHeaders instead:
HttpRequest(GET, /some/address.json)
.withHeaders(
RawHeader(X-Forwarded-For,
I have an application where we are creating and destroying a lot of
actors. The amount of actors that are created is tied to the volume of
requests on the application.
I am using FSM for the Actor in question here.
I do not fully understand what is involved with the setup / teardown of an
I would love to hear some more details about this! How do you avoid the two
clusters to write to the same persistence-id? Not all my actors are divided
in groups I can use to separate the traffic stream. Some are global, and
would (in my current application) immediately start to persist stuff
33 matches
Mail list logo
