Hi everyone,
I'm using akka-http 1.0-M5 and I want to make the following transformation:
From *RequestContext* to *HttpEntity* then *ByteStrings* andthen
*JsonString* andthen *Deserialize* andthen *[Domain object that came to
server in payload]*
The transformation path looks like:
I have a test that does something like this:
test in {
val actorName: String = UUID.randomUUID.toString
val eventActor = system.actorOf(Props(new EventActor(...)), name =
actorName)
watch(eventActor) // receive message if actor terminates
// do something
Hi everyone,
I'm using the version 2.3.4 and I would like to know if there is a way of
subscribing or catching the event of a OversizedPayloadException. The thing
is that a node of the cluster performs an operation in a database and the
result is larger than the configured maximum size. A
https://www.typesafe.com/blog/akka-wins-2015-jax-award-for-most-innovative-open-technology
--
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
In my system, I use 16 sender actors sending messages to 1 receiver actor.
16 sender actors distribute evenly on 4 ActorSystem,s and receiver actor is
in an individual ActorSystem.
Each sender sends 75msg/s to receiver, each message is about 1kb.
The problem I met is that when the senders begin
I'm trying to compile and run a Multi-JVM test I've written but trying to
compile the test results in import errors for various akka.* packages that
are on my classpath in the runtime and test configurations but don't
seem to be included in my multi-jvm configuration.
I've resorted
*SOLUTION:*
Adding the multi-jvm configuration qualifier to my test dependencies
seems to have fixed the issue. So I changed:
org.scalatest %% scalatest % 2.2.1 % test
to:
org.scalatest %% scalatest % 2.2.1 % test,multi-jvm
On Thursday, April 23, 2015 at 11:54:38 AM UTC-7, GG wrote:
Hi,
I would like to better understand how a Receptionist actor is going to work.
val receptionist: ActorRef[Command] = ctx.spawn(Props(Receptionist.
behavior), receptionist)
receptionist ! Register(MySystem, someActor)([1])
receptionist ! Find(MySystem)([2])
[1] why it
Hi David,
The reason why we don't expose a raw actor based ActorProcessor class
because it is much harder to write a correct Processor than you think. Much
much much harder. Knowing how to write a Publisher and Pubscriber does not
translate to knowing how to write a Processor. We already know
Hi Jacy,
The latest version of Akka is 2.3.9. Is there a reason why you use 2.1.4?
It is very old now. Since 2.2 the whole IO layer has been changed and now
it is not iteratee but actor based. In addition there is the upcoming
experimental Akka Streams package that has support for TCP as well.
Hi drewhk,
It is because we have used 2.1.4 since 2 years ago, it was always working
fine until it encountered that Error twice in this month.
It is better not to upgrade the already-working-good product unless we have
carry out all kinds of tests over the latest version.
On Thursday, April
After reading the source code of IOManagerActor, it seems it might have
concurrent problem if it tries to write message into a closed channel.
On Wednesday, April 22, 2015 at 4:09:28 PM UTC+8, jacy hong wrote:
1.
Server Environment
OS: Centos 6
JDK: 1.6.0_30
Akka:
On Thu, Apr 23, 2015 at 8:22 AM, jacy hong johnsoncr.h...@gmail.com wrote:
Hi drewhk,
It is because we have used 2.1.4 since 2 years ago, it was always working
fine until it encountered that Error twice in this month.
It is better not to upgrade the already-working-good product unless we
drewhk,
Alright, it is noted, previously i was just wandering is there anybody
else have encountered the same problem so we could borrow some idea, now
since we already got to know where it was related to, we will figure out
how to fix it by our own.
Thank you for your response/advice
Hi Harit,
the Java API is feature-complete (as all our Java APIs) - you can do anything
you might possibly need in plain Java.
The note speaks about the conciseness of the code - we find that tests written
in Scala are much more readable because of
how we can utilise the language to provide a
Hi
I have designed an Actor system which takes a request which consists of
8000 IDs, splits it into 4 chunks (2000 IDs each), processes each chunk in
parallel, and merges the results.
To do this, I have a main thread which is calling ask on a request
handling actor at a rate of 200 requests
By the way, I am measuring the latency as the time from when the request
handler actor receives the ProcessRequest message to the time when the
request handler actor receives all 4 PartialResults for that request.
Also, I am using Akka 2.3.9
--
Read the docs: http://akka.io/docs/
Dear hAkkers,
We—the Akka committers—are pleased to be able to announce the availability
of Akka 2.3.10. This is the tenth maintenance release of the 2.3 branch.
This release contains several important improvements:
-
change default configuration to disable TCP IO connection abort
On Tue, Apr 21, 2015 at 10:44 PM, Joseph Elliott joe.elli...@joulebug.com
wrote:
Hello,
I've got an application that uses an Akka cluster v2.3.9 (we are running
several servers at Amazon EC2) and recently the cluster has been behaving
badly. The nodes aren't reconnecting to each other when
Is this related to AdaptiveReceiveBufferSizePredictor of Netty?
I found akka use the default configuration:
AdaptiveReceiveBufferSizePredictor(64, 1024, 65536)
在 2015年4月24日星期五 UTC+8上午2:54:37，刘澜涛写道：
In my system, I use 16 sender actors sending messages to 1 receiver actor.
16 sender actors
20 matches
Mail list logo
