Hi
I think that's a fairly normal way to use typesafe config - I'm doing
similar and it seems to work for me.
I'd suggest turning on akka.log-config-on-start in your restapi.conf or
also specifying -Dconfig.trace=loads to see what it's doing at startup.
Perhaps it has found another
This would be for a system that services requests from users directly and
also with other systems. Users would have a session cookie and non-user
systems a token.
The idea / paradigm here is the old java interceptor authentication
approach where authentication was attempted a number of ways
is this not a common environment setup? (aka. an application.conf inside an
uber jar containing application configurations and an external smaller conf
file that contains a small set of environment-specific overrides)
if it isn't I'd be happy to here how others manage application
We've both gotten ssl to work in a manual (aka non-sslConfig) way. My
question still stands though. Has the sslConfig actually been wired to work
with akka-http or is this still something being worked on? If the former is
there any example to a config-based ssl integration?
And please don't
Hi,
Using ReactiveKafka with hundreds of consumers per app/JVM, I frequently a
lot of "already requested" warning.
As far as I understand under normal situation it could happen in case of
rebalancing, but with so many occurence seems weird to me.
21:46:22.820 WARN a.k.KafkaConsumerActor -
A few a know about: rsyslog, Splunk, Lightbend ConductR
/Patrik
fre 19 maj 2017 kl. 12:47 skrev Evgeny Shepelyuk :
> Hello,
>
> We're using ELK for our Docker based services and currently it's quite
> useful for collecting and analyzing logs.
> There's another option
look at this profiler output showing the incoming references to a
ClusterRouterGroup for a terminated Actor why are these still here?
These ClusterRouterGroup (and settings) just keep piling up after the actor
is terminated and recreated later
anyone thoughts?
On Wednesday, May 17, 2017 at 8:11:01 PM UTC-6, bitsof...@gmail.com wrote:
>
> Whats the best way to properly terminate a ClusterRouterGroup actor
>
> i'm doing
>
> ActorRef actorRef = getContext().actorOf(new ClusterRouterGroup(new
> RandomGroup(myPaths),
>
No, no -- I mean "node" in the sense that a configuration file is
essentially a tree, and each section is a node in that tree. As far as I
know, the description of "my-dispatcher" doesn't belong under
ActorSys.akka.actor. Please re-read the documentation...
On Fri, May 19, 2017 at 2:14 AM,
Hello,
We're using ELK for our Docker based services and currently it's quite
useful for collecting and analyzing logs.
There's another option https://www.graylog.org - it works very similar to
how ELK does, but as for me - easier to setup.
Also, you can try some of hosted solutions,
-
Hi Justin,
Am running this code on local machine. What am missing here...?
On Thursday, May 18, 2017 at 12:42:09 PM UTC+5:30, Abhishek G wrote:
>
> Am a newbie to Akka
>
> import akka.actor.Props
> import akka.actor.ActorSystem
> import akka.actor.Actor
>
Hi Justin,
Am running this code on local machine. Make necessary changes in the code.
Thanks..!!
On Thursday, May 18, 2017 at 12:42:09 PM UTC+5:30, Abhishek G wrote:
>
> Am a newbie to Akka
>
> import akka.actor.Props
> import akka.actor.ActorSystem
>
Dear Hakkers,
I would be interested in using Google Cloud Platform for deploying Akka
clusters with persistent actors. I was wondering if there is a
possibility and if somebody did use the Google Data Store for Akka
persistency.
I understand that for that one would need to be able to implement
Hi Justin,
Am ruuning this code on local machine no concept of node
On Thursday, May 18, 2017 at 12:42:09 PM UTC+5:30, Abhishek G wrote:
>
> Am a newbie to Akka
>
> import akka.actor.Props
> import akka.actor.ActorSystem
> import akka.actor.Actor
>
14 matches
Mail list logo