I´m doing some practical examples with Akka. Everything fine so far. But now
that I start looking Akka persistence, in all blogs that I read they said that
I need to configure the persistence in the application.conf
akka {
persistence {
journal.plugin = "inmemory-journal"
Thank you Rafal.
On Thursday, 2 February 2017 23:01:04 UTC+8, Rafał Krzewski wrote:
>
> What I mean is completely standard SLF4J usage like:
>
> import org.slf4j.LoggerFactory
> val logger = LoggerFactory.getLogger(classOf[MyClass])
> logger.info("hello")
>
> It should just work. akka-slf4j
Hi Eric,
we'd like to look into that. It looks as if a streams materializer is
holding on to some memory but we need more info to see what it keeps
exactly to.
Is this a reproducible scenario? Could you share the memory dump (in
private) with us? Otherwise, could you send the list of top
I have an akka-http/akka-streams application that I’ve recently upgraded to
10.0.3. After handling many requests, it runs out of memory. Using the
Eclipse MAT, I see this message:
One instance of "akka.actor.RepointableActorRef" loaded by
"sun.misc.Launcher$AppClassLoader @ 0x8b58"
I'd like to process persistent query events by tag, but parallelize the
processing by persistenceId. Something like...
def readEvents(): Future[Done] = {
val startOffset = state getOrElse NoOffset
/* group by persistenceId
* run the groups in parallel,
* but in order within each
I am trying to stream large files to an endpoint. To briefly describe what
this code does : - It generates a valid path, then stream the data to the
disk, then store metadata.
It works well expect for one thing : The file seems to be stored in memory
(as well as on the disk). My memory-free
By the way, using akka 2.3.13.
--
>> 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
Some time ago I started to use akka.pattern.Patterns.after. Yesterday I
noticed that it was not working as intended, that is, the function wrapped
in a Future passed as parameter was being executed imediately, in the act
of calling it.
Then I realized that besides akka.pattern.Patterns.after
