you share actor refs between
> two actor systems in the same jvm in a wrong way.
>
> I think it would be easiest if you don't use a separate HttpSystem, and
> instead run those things in the ActorSystem named ClusterSystem.
>
> /Patrik
>> fre 30 okt. 2015 kl. 19:57 skrev
I have a web service that up until my addition of server-side web socket
support, worked fine.
I use akka-http to handle HTTP requests, and a cluster sharding region to
route messages (sourced from the HTTP request) to actors that handle a
particular "job" (the job id is the id used for
On Thursday, October 15, 2015 at 12:24:48 AM UTC-7, Johannes Rudolph wrote:
>
> Have you seen/tried
> http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html? It
> seems to suggest that chunked transfer-encoding is supported, though in a
> bit complicated format where on top of
> Content-Type: text/plain; charset=UTF-8
> Content-Disposition: form-data; name=foo
>
> FOO
> --1QipXPrd9L25eJwcQYgiNbfA
> Content-Type: text/plain; charset=UTF-8
> Content-Disposition: form-data; name=bar
>
> BAR
> --1QipXPrd9L25eJwcQYgiNbfA
AWS/S3 HTTP Post with a policy requires an HTTP post with multipart-mime --
one part for the file and one part, each, for various form parameters. When
I use akka.http and attempt to marshal FormData to an Entity and use that
to create a multi-part mime message, all the form data go into one
; marshallers, one for url encoding and one for multipart called, I think,
> Multipart.FormData. sorry if you already know this.
>
> Hi Eric! :P
> On Oct 11, 2015 9:18 PM, "Eric Swenson" <er...@swenson.org >
> wrote:
>
>> AWS/S3 HTTP Post with a policy requires
Since upgrading to akka 2.4.2-RC2, I’m seeing the following warning on startup:
background log: info: [WARN] [02/04/2016 15:21:46.414]
[ClusterSystem-akka.actor.default-dispatcher-25]
[akka.serialization.Serialization(akka://ClusterSystem)] Using the default Java
serializer for class
AM, Roland Kuhn <goo...@rkuhn.info
> > wrote:
>
>> Yes, this sounds like a good strategy to me.
>>
>> Regards,
>>
>> Roland
>>
>> 1 feb 2016 kl. 23:56 skrev Eric Swenson <er...@swenson.org
>> >:
>>
>> Probably a bett
of
nodes out-of-sync with reality is minimal. — Eric
> On Feb 1, 2016, at 2:43 PM, Eric Swenson <e...@swenson.org> wrote:
>
> Are there any good solutions for deploying akka clustered applications in
> docker containers running under AWS/ECS? While there are proposed soluti
>.
>
> Greetings
> Odd
>
> On 2 feb. 2016, at 19:01, Eric Swenson <e...@swenson.org
> <mailto:e...@swenson.org>> wrote:
>
>> Hi Odd,
>>
>> Thanks. I've looked at constructr and see that it would work fine and is a
>> general sol
be something else at play here.
Help!
— Eric
> On Mar 18, 2016, at 7:17 PM, Eric Swenson <e...@swenson.org> wrote:
>
> One more thing to add to this, in case it is relevant. I see multiple of
> these messages in the log:
>
> [akka://ClusterSystem/system/sharding/Exper
#-396422686])
— Eric
> On Mar 18, 2016, at 6:54 PM, Eric Swenson <e...@swenson.org> wrote:
>
> I’ve been unsuccessful in trying to get an akka-cluster application that
> works fine with one instance to work when there are multiple members of the
> clusters. A bit of b
I’ve been unsuccessful in trying to get an akka-cluster application that works
fine with one instance to work when there are multiple members of the clusters.
A bit of background is in order:
1) the application is an akka-cluster-sharing application
2) it runs in a docker container
3) the
.akka.io/docs/akka/2.4.2/scala/remoting.html#Akka_behind_NAT_or_in_a_Docker_container
>
> -Endre
>
> On Sat, Mar 19, 2016 at 3:27 AM, Eric Swenson <er...@swenson.org
> > wrote:
>
>> Well, I may be able to answer my own question. It absolutely does matter
>> that the new remote
se config specifies:
withDisableHostnameVerification(true)
I’m finding it hard to believe it is this hard to do HTTPS with self-signed
certs. Any suggestions?
— Eric
> On May 17, 2016, at 5:11 PM, Eric Swenson <e...@swenson.org> wrote:
>
> I don't want or need to configure a specific trust
I have a need (no, not in production) to have an akka-based service contact
another service using TLS where the remote service is using a self-signed
cert.
I've used AkkaSSLConfig to configure the "loose" settings:
val looseConfig = SSLLooseConfig().withAcceptAnyCertificate(true).
is
> example shows:
> https://github.com/akka/akka/blob/master/akka-http-tests/src/main/java/akka/http/javadsl/server/examples/simple/SimpleServerApp.java
> (it's server side, but the same process can be done for client – pretty much)
>
> --
> Konrad `ktoso` Malawski
>
Just checked again. No override of that config parameter. Yet, these were,
indeed, logged as errors not warnings. -- Eric
On Monday, August 8, 2016 at 11:28:33 PM UTC-7, Patrik Nordwall wrote:
>
>
>
> On Mon, Aug 8, 2016 at 10:06 PM, Eric Swenson <er...@swenson.org
> >
We have an akka-cluster/sharding application deployed an AWS/ECS, where
each instance of the application is a Docker container. An ECS service
launches N instances of the application based on configuration data. It is
not possible to know, for certain, the IP addresses of the cluster members.
sage.html#How_To_Cleanup_when_Member_is_Removed
>
> /Patrik
>
> fre 5 aug. 2016 kl. 22:31 skrev Eric Swenson <er...@swenson.org
> >:
>
>> One more clue as to the cluster daemon's shutting itself down. Earlier
>> in the logs (although prior to several successful requests being handle
Thanks, Giovanni. That was precisely the problem and while I didn't see the
article you quoted, I "fixed" the problem on my end by having my client use
a Source.fromFuture of a promise which I didn't complete. I'll switch to
using the approach in the article you referenced. Still, I think
I have a web service, implemented in akka-http, to which I’ve added web socket
support. I have an akka-http client that is able to connect to the service and
receive a single message, thereupon the web socket is, for some reason,
disconnected. I do not understand why it becomes disconnected.
I wrote a simple python client:
$ cat ws-test.py
import os
from websocket import create_connection
eiid=os.getenv("EIID")
token=os.getenv("BEARER_TOKEN")
header="Authorization: Bearer %s" % token
ws = create_connection("ws://localhost:9000/ws-connect/%s" % eiid,
header=[header])
while True:
rdened module for dealing with this problem. That's not strictly
> necessary, but you *do* need to have a reliable solution...
>
> On Wed, Aug 3, 2016 at 8:42 PM, Eric Swenson <er...@swenson.org
> > wrote:
>
>> We have an akka-cluster/sharding application deployed
downed, I imagine the rest of the cluster is going to *quickly* lock up,
>> because the result is that nobody is authorized to make these sorts of
>> allocation decisions.
>>
>> All that said -- keep in mind, I'm just a user of this stuff, and am
>> talking at
> All that said -- keep in mind, I'm just a user of this stuff, and am
> talking at the edges of my knowledge. Konrad's the actual expert...
>
> On Thu, Aug 4, 2016 at 4:59 PM, Eric Swenson <er...@swenson.org
> > wrote:
>
>> While I'm in the process of implementing your pro
Our akka-cluster-sharding service went down last night. In the middle of
processing akka-http requests (and sending these requests to a sharding
region for processing) on a 10-node cluster, one of the requests got an
"ask timeout" exception:
[ERROR] [08/05/2016 05:04:51.077]
from
Actor[akka://ClusterSystem/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FClusterSystem%4010.0.3.176%3A2552-6#1200432312]:
Ungate
On Friday, August 5, 2016 at 12:58:55 PM UTC-7, Eric Swenson wrote:
>
> Our akka-cluster-sharding service went down last night. In the
One more clue as to the cluster daemon's shutting itself down. Earlier in
the logs (although prior to several successful requests being handled), I
find this:
[INFO] [08/05/2016 05:04:45.042]
[ClusterSystem-akka.actor.default-dispatcher-5]
[akka.cluster.Cluster(akka://ClusterSystem)] Cluster
elieve the official party line is "Buy a Lightbend Subscription",
> through which you can get their Split Brain Resolver, which is a fairly
> battle-hardened module for dealing with this problem. That's not strictly
> necessary, but you *do* need to have a reliable solution...
&g
es downing.
>
> I believe the official party line is "Buy a Lightbend Subscription",
> through which you can get their Split Brain Resolver, which is a fairly
> battle-hardened module for dealing with this problem. That's not strictly
> necessary, but you *do* need to ha
n/resources/reference.conf#L131
>
> <https://github.com/akka/akka/blob/master/akka-persistence/src/main/resources/reference.conf#L131>
>
> Regards,
> Patrik
>
> On Tue, Aug 2, 2016 at 9:44 PM, Eric Swenson <e...@swenson.org
> <mailto:e...@swenson.org>> wro
oc.akka.io/docs/akka/2.4/scala/cluster-sharding.html#Removal_of_Internal_Cluster_Sharding_Data
>
> Have you changed the default mode=repair-by-discard-old in the config of
> the replay filter?
>
> https://github.com/akka/akka/blob/master/akka-persistence/src/main/resources/reference.conf#L131
>
&g
I'm getting this error consistently now, and don't know why this is
happening nor what to do about it. I form the persistentId this way:
override def persistenceId: String = self.path.parent.parent.name + "-"
+ self.path.name
So I don't see how I could have two persisters with the same
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"
a reproducible scenario? Could you share the memory dump (in
> private) with us? Otherwise, could you send the list of top consumers (by
> numbers and / or bytes) as seen in MAT?
>
> Thanks,
> Johannes
>
> On Friday, February 3, 2017 at 2:56:04 PM UTC-7, Eric Swenson
to “push”
during onStreamFinish, since with AES/CBC encryption, there are more stream
elements after the last input that must be emitted.
Anyone see what is wrong? — Eric
> On Oct 7, 2016, at 12:02, Eric Swenson <e...@swenson.org> wrote:
>
> I wrote a simple test for my CipherS
sure why this caused the behavior I was seeing, fixing this caused the
onUpstreamFinish to be called. It must been because since all output Sinks
were Sink.head, that the sinks terminated the graph execution before the Source
did. — Eric
> On Oct 7, 2016, at 12:46, Eric Swenson <e...@swens
ote that all other modules
> other than "the DSL" have been stable for a long time already.
>
> --
> Konrad `ktoso` Malawski
> Akka <http://akka.io/> @ Lightbend <http://lightbend.com/>
> On 18 October 2016 at 19:41:18, Eric Swenson (e...@swenson.org
&
Congratulations! Is the plan to remove the "experimental" from
akka-http-experimental when this moves from RC to final? -- Eric
On Monday, October 17, 2016 at 3:22:17 PM UTC-7, Konrad 'ktoso' Malawski
wrote:
>
> Dear hakkers,
>
> We are proud to announce the first Release Candidate of the
ng all the security
> (just to identify where is the issue) is still not working.
>
> On Wednesday, 18 May 2016 22:13:03 UTC+1, Eric Swenson wrote:
> Apart from my prior point — that it is not practical for my test environment
> to configure all the trust anchors (self signed cert si
Konrad,
Will new topics continue to be pushed to the mailing list as they are
published on the discuss.akka.io web site? I have avidly followed the
mailing list and use it to learn of new developments and read up on topics
of interest to me. I relied on the "push" nature of the mailing list
kka-user][deprecated] Re: [akka-user] Announcing discuss.akka.io!
Hi Eric,
You can setup email notifications as described in
https://discuss.lightbend.com/t/how-to-use-the-discuss-forum-as-a-mailing-list/61
/Patrik
fre 16 mars 2018 kl. 22:01 skrev Eric Swenson <e...@swenson.org>:
Kon
-http.
On Wednesday, January 2, 2019 at 7:11:11 AM UTC-8, and...@tipser.com wrote:
>
> Hi Eric,
> we are having the same issue. Did you finally debugged/resolved it?
>
> Many thanks,
> Andrzej
>
>
> On Monday, February 6, 2017 at 9:15:11 PM UTC+1, Eric Swens
44 matches
Mail list logo
