Did you try to use the classloader of the ActorSystem?
Note that Akka microkernel is deprecated and better replacement is
documented.
/Patrik
ons 18 maj 2016 kl. 08:36 skrev Sidharth Khattri :
> I know this thread is quite old now, but encountered similar kind of
> problem.
hi ,i changed to async
implicit lazy val system = ActorSystem("example")
implicit val mat = ActorMaterializer()
val source = Source.repeat(1)
val temp = source.async.batch(5, it => new IntHolder(0))((all, other) => {
all.a += other; all
})
val end = temp.async.runForeach(it => {println(it);
Streames are fused by default right now so the entire pipeline is sleeping once
you did that.
You should try sprinkling an .async call around the fast (or slow) stages.
--
Konrad `ktoso` Malawski
Akka @ Lightbend
On 19 May 2016 at 03:18:45, Yang Yang (wjingyao2...@163.com) wrote:
hi , i got a
hi , i got a faster upstream, and a slow downstream,
so i want to "combine" the up-coming item into a arraybuffer, and then
consume the arraybuffer in a batch.
i find the Flow.batch seems can help me here,
but i write some test,which is not what i expect
*case class *IntHolder(*var
Apart from my prior point — that it is not practical for my test environment to
configure all the trust anchors (self signed cert signer), I decided to try it
anyhow for a single self-signed cert. I still am having issues: here is the
code:
val trustStoreConfig = TrustStoreConfig(None,
There are ways you can hide this eventual consistency as well (mostly UX
based).
As examples.
Don't take user to data they just changed.
Fake it in the UI (eg show the user stuff but only for their session)
Remember the transactionid + count etc and make these are monotonic, only
show data if
Hi Antti,
That was an unintentional consequence of a change to the build. We have now
published it to maven central and are making sure it is in the next release
by default.
Thanks for letting us know about it!
--
Johan Andrén
Akka Team, Lightbend Inc.
On Wednesday, May 18, 2016 at 2:38:49
Hi Group
I have asked a question on Stack overflow. Link:
http://stackoverflow.com/questions/37271858/how-are-remote-actors-created-on-joining-of-new-nodes-in-akka.
I am just posting here as well to increase my chance of getting help.
Thanks.
Question:
Explaining my Akka cluster setup:
- I
Great work.
Any reason why akka-osgi module is not included in the release?
-Antti
On Tuesday, May 17, 2016 at 1:01:47 PM UTC+3, Johan Andrén wrote:
>
> *Dear hakkers,*
>
> we—the Akka committers—are proud to announce a new minor release of Akka,
> 2.4.5 that contains some pretty major news
On Wed, May 18, 2016 at 12:09 AM, Markus Fresh <
markus.frischkne...@finconsgroup.com> wrote:
> Thank you for the reply; in one fell swoop, this explains what I
> encountered.
>
> On Friday, 13 May 2016 22:20:01 UTC+2, Patrik Nordwall wrote:
>>
>> Where in the documentation have you read that the
Hi,
I implemented a short prove of Concept and wanted to ask if this is the
right way to do it, because it doesn't feel so ;) Here the Code:
Failover is done when the hosting node crashes or is shutdown and then
there will be no outstanding writes lingering on the Akka side. A failover
also takes tens of seconds.
On Wed, May 18, 2016 at 7:26 AM, Denis Mikhaylov
wrote:
> Don't you think it's possible during
I know this thread is quite old now, but encountered similar kind of
problem. Did you find any solution?
On Wednesday, February 26, 2014 at 7:20:33 AM UTC+5:30, Constantine Kozak
wrote:
>
> Hello,
>
> I've created an Akka microkernel distribution (2.2.3) and having a problem
> on a launch. My
13 matches
Mail list logo