Great work, everyone! With special thanks to Jan :-)
Sent from my iPhone
> On 18 May 2016, at 02:14, Giovanni wrote:
>
> Great!
>
> giovanni
>
>> On Tue, May 17, 2016 at 6:01 PM, Johan Andrén
>> wrote:
>> Dear hakkers,
>>
>> we—the Akka
I'm learning about akka tcp using actors in scala and I would like to write
a bytestring to a connection to a remote host, and wait until I receive a
msg reply. I need to do this in order to not overflow the server with my
client. Can someone help me write an actor that can write and wait for
I don't want or need to configure a specific trust anchor. I want to be able to
do the equivalent of "curl -k" on a set of local servers, with different
signing certs. I would have thought the loose "acceptAnyCertificate" would have
been precisely for this. What does that setting do?
If the
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).
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 leader is the oldest
> member? I would like to correct that, because it's not true.
>
In fact, there
(I'm not clear if you have N singletons, that they all reside on the same node
though?)
Yes, unless you give tell some of them to be on a specific role.
As seen in
http://doc.akka.io/docs/akka/current/scala/cluster-singleton.html#An_Example
-- Konrad
--
>> Read the docs:
Okay, I was starting to pursue just asking which node in the cluster was
the oldest. Seems like the singletons ought to migrate to that node?
(I'm not clear if you have N singletons, that they all reside on the same
node though?)
On Tue, May 17, 2016 at 4:47 PM, Justin du coeur
I suspect the most straightforward way to do this is to send a message to
the singleton and ask it which node it's living on. Granted, that makes
the test a bit less black-box...
On Tue, May 17, 2016 at 4:29 PM, Steve Rehrauer
wrote:
> I have a few cluster singletons.
Wait, might be as simple as node.address.host == actorRef.path.address.host?
On Tuesday, May 17, 2016 at 4:29:53 PM UTC-4, Steve Rehrauer wrote:
>
> I have a few cluster singletons.
>
> One in particular can hold a fair bit of state.
>
> While doing load-tests, I want a way to discover which
I have a few cluster singletons.
One in particular can hold a fair bit of state.
While doing load-tests, I want a way to discover which node's heap use is
contributed to by that singleton.
Is there a programmatic way to, from a sequence of the cluster nodes and
the singleton's proxy actor
yes, it should be piped to self, and thrown there so that the parent can
handle the exception. Sorry if I was unclear.
On Mon, May 16, 2016 at 5:58 PM, Yan Pei wrote:
> Patrik,
> I think I made it work by piped Status to itself(the child actor) and
> 'throw' the matched
Thanks, look for PoisonPill
On Tue, May 17, 2016 at 8:50 PM, Denis Mikhaylov
wrote:
> Patrik, thanks for your response!
>
> I will create an issue and will take a look at rebalance code with your
> suggestion in mind.
>
> Denis.
>
> --
> >> Read the docs:
Patrik, thanks for your response!
I will create an issue and will take a look at rebalance code with your
suggestion in mind.
Denis.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
Please don't use Durable mailboxes, they're deprecated for a reason –
they're really bad as they *block* the sender.
It's replacement is Akka Persistence, read up on it – it allows you to
build apps using event sourcing.
Though what you describe does not sound like you need that... what's your
Hy Endre,
thanks for the reply and sorry for the late answer (Was on vacation).
Good thoughts - a router seems like a good idea. It will also solve the
problem of a DDOS attack against the login page (which is very expensive
due to the bcrypt).
What do you prefer to cover the first overhead
Found the problem, an actor creator constructor need to be preferably
public, even if the code compiles in Java,
under some complex circumstances the class loader cannot see the
constructor,
in the reproducer posted on the
issue https://github.com/akka/akka/issues/20537 I made it private to
That is an interesting scenario. I think it can happen as you describe it
and for rebalance there are no big timeouts as for the failover scenarios.
We are using PoisonPill to stop the entity actors during the rebalance.
PoisonPill is not very good for persistent actors, since it bypasses the
*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 for those of you who are using
Akka HTTP with Java.
*Rise of the “New” Java Routing DSL*
This release contains the long-awaited “new” Routing DSL for Java
Yeah, agreed, I deleted that comment once realized the complexity of the
problem.
On Tuesday, May 17, 2016 at 10:15:30 AM UTC+1, Patrik Nordwall wrote:
>
>
>
> On Tue, May 17, 2016 at 10:32 AM, Guido Medina > wrote:
>
>> Is it safe to say it will be fixed in the next
I have already had this discussion in the akka gitter channel. The actor
will recover its status after the next restart if no snapshots are involved.
On 16 May 2016 at 17:45, Денис Михайлов wrote:
> Is it possible that insert sent from PersistentActor to C* has stuck
>
On Tue, May 17, 2016 at 10:32 AM, Guido Medina wrote:
> Is it safe to say it will be fixed in the next release? i.e.: 2.4.6?
>
We must first understand the issue, before promising anything. We can
continue the discussion in issue https://github.com/akka/akka/issues/20537
and
Thanks Patrik and Konrad for the quick responses.
Yes, you are right, there are many ways, from the Java perspective an
static class and creation at a method or constructor might be very common.
Thanks again for the quick responses.
On Tuesday, May 17, 2016 at 9:31:31 AM UTC+1, Patrik Nordwall
Is it safe to say it will be fixed in the next release? i.e.: 2.4.6?
On Tuesday, May 17, 2016 at 9:28:58 AM UTC+1, Konrad Malawski wrote:
>
> The change is this: https://github.com/akka/akka/pull/20488
>
> On Tue, May 17, 2016 at 9:50 AM, Guido Medina > wrote:
>
>> I didn't
Thanks of noticing this, Guido. The change was introduced in
https://github.com/akka/akka/pull/20488 due to a fix of a bug that we have
not dared to touch for 1 year just because there is a risk of such
regression. There are incredibly many ways you can write such a Creator and
we obviously didn't
The change is this: https://github.com/akka/akka/pull/20488
On Tue, May 17, 2016 at 9:50 AM, Guido Medina wrote:
> I didn't pasted the code because I wasn't sure it was a known issue:
>
> // Inside an actor supervisor:
>
> static final class PriceProcessorCreator implements
I didn't pasted the code because I wasn't sure it was a known issue:
// Inside an actor supervisor:
static final class PriceProcessorCreator implements
Creator {
final StrategySupervisor supervisor;
protected PriceProcessorCreator(StrategySupervisor supervisor) {
When talking about "that code does not work", please paste the code under
discussion.
On Tue, May 17, 2016 at 9:39 AM, Guido Medina wrote:
> My creators are not working with Akka 2.4.5, they have been working up to
> now,
> My actor creators are either static classes or
My creators are not working with Akka 2.4.5, they have been working up to
now,
My actor creators are either static classes or standard classes but the
methods that use the creator are not static:
java.lang.IllegalArgumentException: cannot use non-static local Creator to
create actors; make it
Hi
We are using akka for which we are exploring rabbitmq to persist
mailbox messages. Is there any rabbitmq plugin for akka durable mailbox
compatible with akka 2.4.4?
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>>
29 matches
Mail list logo