Hi,
I stumbled upon behaviour of AtLeastOnceDelivery which I do not understand.
When my actor is started and I call deliver in receiveRecover to make
sure that my message will eventually be delivered at least once. Because of
an error the actor throws an exception on a next event. This leads
Hi!
I'm using Akka with Java, and I'm trying to figure out the best way to
share logging between actors and regular classes that also do logging.
We're using slf4j both with our actors and other classes, so we already
have everything with the same pattern and in the same logfile. From what
Hello All,
Our application is nearly offline, it doesn't need to communicate with
remote servers etc. The only obligation they have is to communicate with
the hardware that are in the same gigabit network in realtime. So the load
is nearly at the same level all the time. We also already have
It is still not a trivial task to do this and keep your business logic
clean and separated from the persistence part. From my experiences the
following makes things more complex:
- It is not necessarily a 1:1 relationship between commands received and
state changes. One received command may
I have not had time to watch this yet, but perhaps it may be of some
interest - https://vimeo.com/105888905
On 17 October 2014 08:39, Koray Al hecatom...@gmail.com wrote:
Hello All,
Our application is nearly offline, it doesn't need to communicate with
remote servers etc. The only obligation
Hi Nan,
please try to avoid double-posting threads between akka-user and akka-dev.
This question has ben answered on
akka-dev: https://groups.google.com/forum/#!topic/akka-dev/bxSBxwHKw6M
-- Konrad
W dniu środa, 15 października 2014 04:10:56 UTC+2 użytkownik Nan Zhu
napisał:
Hi, all
When
Hi Nils,
I actually would keep logging separated as you have now, and simply use
slf4j as provider for both so it will be one config file (
http://doc.akka.io/docs/akka/snapshot/java/logging.html#slf4j ).
In your non actor classes you'd use the scala-logging
On Thu, Oct 16, 2014 at 10:49 AM, Alec Zorab aleczo...@gmail.com wrote:
I think this is a very common use case for applications streaming time
sensitive data (for example prices) where we would want to do an n-way zip
and then receive the most recent set of data for those n things.
I agree,
Hello guys,
Dan's suggestion is indeed a great one.
Java serialization might bight you when you least expect it, and that can
happen right away when you start using remoting.
We will aim to remove the java-serializer as configured by default
serializer in future versions of Akka so that people do
Sorry I don't have sample code I can share and I'm slammed right now, but
the per-request stuff is from the net-a-porter Activator template:
http://typesafe.com/activator/template/spray-actor-per-request
On Wed, Oct 15, 2014 at 4:35 AM, Chanan Braunstein
chanan.braunst...@pearson.com wrote:
Hi Jeroen,
Thanks for preparing the example, it made checking what the problem is very
simple :-)
Try searching for `confirmDelivery` in your code snippet. It's not there.
And with no confirmation, there is no information on in the sending-actor
that the target has really received the message.
Hi Vadim,
I'm not exactly sure what you mean by on other nodes with the same role.
How did you setup cluster sharding?
When do you expect the shard to be brought back?
I'll happily help but seem to be missing context here a bit.
On Wed, Oct 15, 2014 at 4:52 PM, Vadim Bondarev haghar...@gmail.com
Hi Anders,
You asked for a more advanced sample.
Here is one: http://typesafe.com/activator/template/akka-cluster-sharding-scala
Unfortunately it has not been ported to java yet, but you might be able to
understand the design.
The idea is that you always change the state by applying the stored
Hi all,
Is there any smart way to resend a MemberUp? I'm facing the next issue:
Let's say we have a cluster with 2 nodes and only one of them is a seed
node. I start the seed node and later the non-seed node and both can
communicate each other; so far, so good.
Seed node goes down and after a
By the way, I forgot to mention that I'm using the version 2.2
--
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
---
You received this message because
Hi Konrad
Sorry for missing context, now I'll try to give it to you
I have a cluster with two types of nodes(roles) A and B
On each B node, on start I run ClusterSharding(system) and
create N domain (PersistentActor) actors (just sending N message in
shardRegion actor with predefined key).
cool, scala-logging is back :) i had thought that had been abandoned.
-Michael
On 10/17/14 05:12, Konrad Malawski wrote:
Hi Nils,
I actually would keep logging separated as you have now, and simply
use slf4j as provider for both so it will be one config file (
I feel sure this must have been covered, but my searches are coming up
blank.
The benefits in terms of write-throughput are clear to me, but free
auditing is often touted as a benefit of event sourcing, and one that can
help sell the concept.
So, are there supported APIs to get access to the
Hello there Richard,
while it’s very low level API, it is publicly accessible if you want to
talk to it.
Access it like this:
val journalActor: ActorRef =
Persistence(system).journalFor(persistence-id-something)
In theory this is ready to support multiple journals in the same actor
system,
Thanks for the reply. I'm using plain Java, so is scala-logging for me?
What does it provide extra than using slf4j directly?
Nils-H
On Friday, October 17, 2014 2:13:22 PM UTC+2, Konrad Malawski wrote:
Hi Nils,
I actually would keep logging separated as you have now, and simply use
slf4j
Thanks for the link.
If I wanted to implement a show history api for a specific persistent
actor, I assume I could create a per-request view just for that one actor
and customize the replay settings?
Like everyone else, I am anxiously awaiting the new streams-based stuff :)
On Fri, Oct 17, 2014
If you're in plain Java just use slf4j directly – I didnt notice you're in
Java only.
Scala logging only provides some sugar to make obtaining the logger
instance more idiomatic.
On Sat, Oct 18, 2014 at 12:55 AM, nil...@gmail.com wrote:
Thanks for the reply. I'm using plain Java, so is
22 matches
Mail list logo
