On Wed, Apr 15, 2015 at 8:16 AM, Wolfgang Friedl <
wolfgang.fri...@hotmail.com> wrote:
> Hi again!
>
> Out of interest, how is it possible to receive a terminated messages from
> Nodes which are still running?
>
It watched an actor that was running on a node (ActorSystem) that was part
of the clu
Hi Kevin,
see
https://github.com/akka/akka/blob/release-2.3-dev/akka-http-core/src/main/scala/akka/http/model/HttpMessage.scala#L133
Cheers,
André
On Wednesday, April 15, 2015 at 4:51:33 AM UTC+2, Kevin Meredith wrote:
>
> There's a Github issue, titled, 500 ISE for Client Side Error -
> http
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:
>> http://doc.akk
On Wed, Apr 15, 2015 at 10:36 AM, Wolfgang Friedl <
wolfgang.fri...@hotmail.com> wrote:
> 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.
>
You're welcome. Thank
For type safety, I use a value class for IDs, like:
case class ClaimId(id: String) extends AnyVal {
override def toString: String = id
}
I'd like to read this id from a query parameter.
For the moment, I use this:
parameter('claim_id.as[String] ?) { claimId ⇒
... claimId.map(ClaimId.apply) ...
How does using akka actor helps in achieving concurrency without use of any
external locks?
Is it because at a moment only one message can be processed for one actor ?
Hence no 2 threads can be acting upon same actor ?
If that is the case, then maximum number of threads we require is equal to
nu
Thanks for the help guys! I figured I stumbled onto a big topic here. :)
@Richard - I haven't used Scala Pickling, though I do have some experience
with scodec for binary serialization. One problem I have with binary
serialization with akka-persistence is it makes it makes it harder to debug
On Wed, Mar 25, 2015 at 11:55 AM, Patrik Nordwall wrote:
> Hi Amir,
>
> On Sun, Mar 22, 2015 at 8:57 PM, Amir Karimi wrote:
>
>> Hi,
>>
>> I have an actor with multiple states. What is the best practice to save
>> snapshots of them:
>>
>>- Aggregating all states into one case class and just
Hi,
I have two ActorSystems Node-A and Node-B in separate JVM processes with
netty-tcp remoting enabled running on the same machine (127.0.0.1) on port
2552 and 2553.
Each ActorSystem starts itself a actor.
The actor sends a "ping" message and replies to a sender with a "pong"
message using ac
Cross posted to stackoverflow
http://stackoverflow.com/questions/29655888/hocon-not-substituting-environment-variables
Anyone have any experience with this issue. Is what I'm attempting even
feasible?
Thanks in advance,
-barrett
--
>> Read the docs: http://akka.io/docs/
Are you using ReactiveMongo? If so what version? Have you investigated
bulkInsert, perhaps buffer locally and only flushing when a certain limit
is reached?
What do your write queues in MMS look like?
Can you clarify what actors you believe are not terminating properly?
On Friday, April 10,
On 04/15/15 04:47, Rohit Jain wrote:
How does using akka actor helps in achieving concurrency without use
of any external locks?
Is it because at a moment only one message can be processed for one
actor ? Hence no 2 threads can be acting upon same actor ?
that is correct. processing within th
On 04/15/15 09:53, bearrito wrote:
Cross posted to stackoverflow
http://stackoverflow.com/questions/29655888/hocon-not-substituting-environment-variables
Anyone have any experience with this issue. Is what I'm attempting
even feasible?
this is a shot in the dark, but are you using an older v
What is actually an Actor in context of code. Is it the java class which
extends UnTypedActor ? i.e. 1 Actor=1 Class.
If yes, do we have multiple instance of it, simple referred using actorref.
How does multiple instance of actorref for same actor differs from each
other ?
What do we mean by a
Correct me If I am wrong, because of message communication design it
inherently provides distributed locking as well.
On Wednesday, April 15, 2015 at 10:37:36 PM UTC+5:30, Michael Frank wrote:
>
> On 04/15/15 04:47, Rohit Jain wrote:
>
> How does using akka actor helps in achieving concurren
My project was using an ancient version. I upgraded to 1.2.1 and it seems
to be working.
Go get those stackoverflow points if that is your thing!
Thanks,
barrett
On Wednesday, April 15, 2015 at 1:19:19 PM UTC-4, Michael Frank wrote:
>
> On 04/15/15 09:53, bearrito wrote:
>
> Cross posted t
Hmm...
Spray currently allows this and products like ElasticSearch promote GET
bodies. This will be a breaking change for me as well once I migrate to
akka-http.
How opinionated are the developers here? Can this be more of a guideline
than a rule? :)
--
>> Read the docs: http:
I was originally thinking that this would be inconvenient for ES clients.
I could work around that. However for anyone attempting to build a
transparent proxy in front of ES (where they can't control client calls),
this would be an impossible to fix solution if a GET with body was
forbidden.
reposted to SO. glad i was able to help :)
-Michael
On 04/15/15 12:07, bearrito wrote:
this is a shot in the dark, but are you using an older version of
typesafe-config? maybe its a newer-ish feature? the feature seems to
be advertised as you describe, but if you are pulling in
typesafe-co
Thanks for you reply. I will look into the aggregator pattern.
On Wednesday, April 15, 2015 at 1:45:33 AM UTC-4, Adam wrote:
>
> Hi,
>
> First of all, actors are very lightweight and you can have many of them,
> while an ActorSystem is heavyweight and you should not have many of that
> (typical
Hi Anil,
I provide the Aggregator pattern and approximately 60 others in my upcoming
book "Reactive Enterprise with Actor Model". It's written for Scala and
Akka, and you can see the preview here:
https://www.safaribooksonline.com/library/view/reactive-enterprise-with/9780133846904/
Best,
Vaug
On Wednesday, April 15, 2015 at 10:37:36 PM UTC+5:30, Michael Frank wrote:
>
> On 04/15/15 04:47, Rohit Jain wrote:
>
> How does using akka actor helps in achieving concurrency without use of
> any external locks?
> Is it because at a moment only one message can be processed for one
> acto
Hello!
I have 2 actors. deployed to different nodes on cluster:
On consumer:
val mediator = DistributedPubSubExtension(context.system).mediator
override def preStart(): Unit = {
log.debug("Subscribing to urls ⇒ {}", self)
mediator ! Subscribe("urls", self)
}
and on producer:
23 matches
Mail list logo
