Hello,
I'll try not to spent too long on the background and to move quickly to the
point. The background is that I was setting up a multi-node cluster, with
each node running in its own Docker container. I had one seed node, and it
was called "meter-seed". By that I mean that I had set
akka.re
Hi Ben,
As my experience goes Netty 3 doesn't get much love, issues are barely
fixed,
like I mentioned before I'm running my own Netty 3.10.6 built internally,
also; 3.10.0 is not even a good version,
if you want force your version to 3.10.5.Final until they release
3.10.6.Final which has nice
I'm following up on this topic after upgrading to akka 2.3.15. I'm
reasonably confident that the issue is the resullt of using akka along with
another library that causes the netty dependency to be upgraded from
3.9.2.Final to 3.10.0.Final. For now I have removed the dependency on the
newer ver
Whoops, forgot to change a name, that CLFSM in the second snippet should be
"MyClass", and the first snippet is defined in "MyClass"'s companion object.
On Thursday, April 28, 2016 at 10:15:23 AM UTC-7, Spencer Judge wrote:
>
> Hi all,
>
> The section here:
> http://doc.akka.io/docs/akka/2.4.4/s
Hi all,
The section here:
http://doc.akka.io/docs/akka/2.4.4/scala/testing.html#Testing_parent-child_relationships
Has some good advice on doing child creation via dep injection so I could
pass in mock children during testing. That's great, but the example is a
bit of a toy because you can't p
It would be great if you can create a reproducer in the SchedulerSpec:
https://github.com/akka/akka/blob/master/akka-actor-tests/src/test/scala/akka/actor/SchedulerSpec.scala
I think it has a way to drive the clock:
https://github.com/akka/akka/blob/master/akka-actor-tests/src/test/scala/akka/acto
Hi all,
I'm using akka-http for uploading big zip files (~ 1Gb) containing a bunch
of files to parse. My goal is not to have to temporarily save to disk the
file but reading it on the fly. In order to do this, we've written a
`ZipInputStreamSource` that builds a `Source` from an `InputStream`.
What information can I provide to help out?
On Thursday, April 28, 2016 at 5:11:39 AM UTC-5, Konrad Malawski wrote:
>
> Yes, the reported issue is might be real and I'd like to get more info on
> it to investigate, I was arguing against the suggestion made to increase
> the range of the schedule
what does your persistent actor look like?
On Mon, Apr 25, 2016 at 7:23 PM, Yan Pei wrote:
> Got another issue.
>
> The logic is very simple: after sending certain number of messages, take a
> snapshot. But the sequence_nr is always 0 for the first time run. The
> second time, I saw some positiv
You can't send the file handle, unless you have a shared file system.
Actor messages should not be large. I would recommend Akka Streams, using
TCP or Http.
/Patrik
On Mon, Apr 25, 2016 at 5:09 AM, Raymond Guo wrote:
> Hi,everyone:
>
> sorry that I'm just new to akka.
> I need to transfer some
I'm not arguing about it, all I saying is:
now in millis + times expressed as Integer limits it to 50 days
now in millis + times expressed as Long limits it to 1000s of days.
Guido.
On Thursday, April 28, 2016 at 11:11:39 AM UTC+1, Konrad Malawski wrote:
>
> Yes, the reported issue is might be r
CPU wise in today's CPUs Long operations and comparison are faster than
with Integer (Integers are up cast to Long) but
memory wise Long has 2 more bytes, GC wise I think there is more work to do
with Integers than Long even if you end up consuming more longer term
memory.
That's getting down t
Yes, the reported issue is might be real and I'd like to get more info on it to
investigate, I was arguing against the suggestion made to increase the range of
the scheduler.
--
Konrad `ktoso` Malawski
Akka @ Lightbend
On 28 April 2016 at 12:10:03, Patrik Nordwall (patrik.nordw...@gmail.com) w
If I have not misunderstood the reported issue this is not about scheduling
something 50 days into the future, but after 50 days the scheduler stops
working. Scheduled tasks were typically around 8 ms.
On Thu, Apr 28, 2016 at 12:07 PM, Konrad Malawski <
konrad.malaw...@lightbend.com> wrote:
> Is
Is 50 days long enough? I think there is no right or wrong answer to that,
a quick solution maybe will be to change from Integer to Long which will be an
easy fix with a minimal effort, that should extend it to like 500 days or more?
No, because for long term scheduling you want to make sure the t
I think for an in-memory scheduler it is reasonable to have it contained
within an Integer (50 days),
in the micro-services world that is a long time to have the services
restarted,
some good reason for a restart is to update dependencies as part of any
standard maintenance cycle.
Is 50 days lo
That is interesting. The scheduler will reject tasks scheduled too far into
the future, but you are not doing that. Please create an issue:
https://github.com/akka/akka/issues
Regards,
Patrik
On Thu, Apr 28, 2016 at 9:49 AM, Guido Medina wrote:
> Hi Eric,
>
> That's a hell of a finding, I think
Hi Magnus,
As far as I remember this is not available, please open a ticket and let's
discuss there.
We likely won't be able to focus on it, but it would be a nice
contribution.. Also, the TLS stage needs to be rewritten to GraphStage, but
that's a rather big and painful task (needs to be done e
Hi Eric,
That's a hell of a finding, I think the immediate solution will be to
change Int.MaxValue to Long.MaxValue, I don't think a system will be
without restart for so many days, but who knows.
Cheers,
Guido.
On Thursday, April 28, 2016 at 7:43:57 AM UTC+1, Eric Cartner wrote:
>
> I've got
Well, I've suggested it: https://github.com/scala/scala/pull/5137
On Wednesday, April 27, 2016 at 4:41:07 PM UTC+2, Bruno Bieth wrote:
>
> I agree with Roland that having a Future[Unit] may lead to subtle bugs due
> to the value discarding mechanism. My favorite is mixing map and flatMap by
> mi
20 matches
Mail list logo
