I'm using a Flow.backpressureTimeout on the incoming flow, and I
don't want to have to wait for the broadcast hubs buffer to be filled
before the timeout is triggered.
If there's agreement that the buffer should be kept empty while there's no
consumers, then I'll be happy to submit a PR.
Cheers,
James
--
*James Roper*
On Friday, July 14, 2017 at 11:55:22 AM UTC+10, James Roper wrote:
>
> We need some form a framing over the TCP connection. A lightweight binary
> protocol could do it, but an easier and probably good enough solution to
> start with is WebSockets with akka-http (to my knowledge akka-
I may have some use cases for this, so I've been thinking about what it
could look like. Here are my rough thoughts:
The problem with using Akka remoting is that it's not a guaranteed
transport nor does it provide back pressure - you would have to serialize
the requset packets, and then
i suspect the issue is related to how you call 'context.system.shutdown()'.
Make sure it is called only after all your messages have been processed to
completion. As written, it appears to be called after the first message is
handled. I'm no expert with actors, but I would guess the reason it
I think what you are looking for is a Source that defines your queries, and
a `mapAsync (3){/* perform query */}` as that executes the queries in
parallel, and returns the results in order.
If the result of the mapAsync is collections, you can flatMap to unpack
them. If the result is Streams, you
on this.
- James
On Dec 2, 2016 8:27 AM, "Martynas Mickevičius" <
martynas.mickevic...@lightbend.com> wrote:
> James, have you seen this ticket: https://github.com/
> akka/akka-http/issues/424
>
> There is an example there, which might help you.
>
> On Tue, Nov
. Am I missing something obvious?
Much thanks,
James
On Nov 26, 2016 4:14 PM, "James Matlik" <james.mat...@gmail.com> wrote:
> I am trying to create an Akka-HTTP streaming service that supports both
> JSON and protobuf.
>
> I am able to support both for
best to handle this?
Thank you,
James
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>&g
Try doing
sbt clean update compile
On Thursday, October 20, 2016 at 11:52:48 PM UTC+8, Gerard Vico wrote:
>
> Hi,
>
> I am working in a project with Scala and Akka. Two days ago, I can't
> launch the test because this error is thrown:
>
> [WARN] [10/20/2016 15:47:32.743] [pool-1-thread-1]
processing it first. You may need to enrich the types at the start of
the stream to drive the special handling logic, such as wrapping in
'either' or donation specific case classes.
Hope this helps,
James
On Sep 27, 2016 5:27 AM, <gor...@8kdata.com> wrote:
> I am an Akka Stream newbie and
are
submitted?
- James
On Jul 22, 2016 5:46 AM, "Akka Team" <akka.offic...@gmail.com> wrote:
> Hi James
>
> On Thu, Jul 14, 2016 at 1:22 PM, James Matlik <james.mat...@gmail.com>
> wrote:
>
>> Using Akka streams for ETL is our primary use case. The back pr
Thank you Rob,
Another way is to pass the actorRef to a static object, which can be
referenced by other instances later. I am wondering which way is better:
pass the actoreRef to a class instance or assign the actoreRef to a static
attribute in an object.
Best,
James
On Tuesday, July 19
e the best approach to handle this issue to have the class
instance got the new restarted actorRef automatically?
Thank you very much!
James
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ
-
We are not quite sure how to do this with new AKKA http since there is no
HttpService available any more.
Thank you very much!
James
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check th
that
decides what external entities should be processed, and how many should be
run concurrently, isolating failures between them and reporting accordingly.
This has worked well for us. Hopefully these ideas may help you as well.
- James
On Jul 15, 2016 3:10 AM, "AWel" <andy.zelin...@
Using Akka streams for ETL is our primary use case. The back pressure
support has been extremely useful in helping us maximize throughout while
at the same time avoid overwhelming the multiple external rest services we
query against. By maintaining dedicated, fixed sized dispatcher pools, we
can
. It is a
pleasure to work with.
Thanks,
James
On Mon, Jul 11, 2016 at 9:19 AM, Akka Team <akka.offic...@gmail.com> wrote:
> FYI: we will work on performance (of the materialization among other
> things) the coming weeks.
>
> Until that is done you probably won't see much difference with any
incrementally. I would like to
minimize the materialization overhead, but don't really know the basic
patterns needed to do so.
I believe this issue is very similar to that of the short lived connections
performance issues the akka-http server is experiencing.
Thank you,
James
e with 2.4.3, etc. They move together now.
>
> Happy talking!
> On Apr 8, 2016 18:43, "James P" <jsp...@gmail.com > wrote:
>
>> Hi Folks,
>>
>> I'm trying out the tutorial on Akka Streams (Java) and the following line
>> of code from the tutorial:
>
-and-basics.html
Any help would be much appreciated. Thanks.
Best regards,
James
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ:
>>>>>>>>>> http://doc.akka.io/docs/akka/
conversion, but
I've come to realize Streams usually provide a safer/cleaner/better way.
Finding out what that way is tends to be the big challenge.
Thoughts or suggestions? Have I missed something standard and am now
reinventing the wheel?
Thanks, James
--
>>>>>>>>>>
Got it. Many thanks :D
On Tuesday, February 16, 2016 at 12:30:19 PM UTC-8, √ wrote:
>
> Hi James,
>
> 1) Message sends are not guaranteed to be delivered (i.e. at-most-once)
> 2) B could die/exit before it gets the message from C
> 3) C could die/exit before it get
issue in the
> first case.
>
> --
> Cheers,
> Konrad 'ktoso’ Malawski
> Akka <http://akka.io> @ Typesafe <http://typesafe.com>
>
> On 30 January 2016 at 04:47:27, James P (jsp...@gmail.com )
> wrote:
>
> Hi folks,
>
> Good da
talk I'm about to deliver:
> //
> https://www.evernote.com/l/AAkD5JPO-rVM3J5S7bnd1g_awyWstD8kCOIB/image.png
> ;-)
>
> --
> Cheers,
> Konrad 'ktoso’ Malawski
> Akka <http://akka.io> @ Typesafe <http://typesafe.com>
>
> On 30 January 2016 at 09:51:41, James P
Hi folks,
Good day. I'm just starting with Akka (Java with Lambda) and I have a
question regarding AbstractFSM.
When using "*akka.actor.FSM.State.using(Data)*" does "*Data*" need to be
immutable?
Example:
*when(State.Idle,*
* matchEvent(Event.class, StateData.class,*
* (event, stateData) ->*
wouldn't depend on always being able to gracefully leave the cluster in
production! node failures and network partitions are a fact of life.
-Michael
On 07/06/15 06:08, James Carman wrote:
We are considering using the DistributedPubSub support in a production
system. We would like
?
James
--
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 because you are subscribed to the Google Groups Akka
User List
It looks to be as simple as adding:
OSGi.contrib
to the sbt file for contrib. Is that all there is to it?
On Saturday, June 6, 2015 at 8:37:34 AM UTC-4, James Carman wrote:
I am using Akka version 2.3.11 in an OSGi-based project and we tried to
add akka-contrib (com.typesafe.akka/akka
/resources/features.xml
On Saturday, June 6, 2015 at 9:36:35 AM UTC-4, Konrad Malawski wrote:
That's quite possibly the only thing missing. Would you like to submit a
PullRequest and we'll look into it there?
On Sat, Jun 6, 2015 at 2:40 PM, James Carman jca...@savoirtech.com
javascript: wrote
/dec95e5b1a1d1761a1d8fe65d8eec4dfacffa857#diff-a7b71e1d7cdab9f7bcd7c6ba9f2ae84dR503
- Why does request(1) trigger the 100-Continue response?
- Is there any documentation or examples that might be more helpful than
what I've already found?
Thanks in advance,
--James
--
Read the docs: http://akka.io/docs/
Check
I think you need an in-scope implicit FlowMaterializer (or perhaps an
ActorFlowMaterializer, if you're on M3. I think that may have been resolved in
M4 though)
James
Sent from my iPhone
On Mar 15, 2015, at 15:17, Arthur Kushka arhel...@gmail.com wrote:
Hi. I was faced with a typical
direction here, please?
—James
[1]
http://doc.akka.io/api/akka-stream-and-http-experimental/1.0-M4/?_ga=1.53285288.1092433602.1423525300#akka.http.server.RequestContext
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
direction here, please?
—James
[1]
http://doc.akka.io/api/akka-stream-and-http-experimental/1.0-M4/?_ga=1.53285288.1092433602.1423525300#akka.http.server.RequestContext
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
?
Thanks
James
--
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 because you are subscribed to the Google Groups Akka
User
but I don't want to use it.
Seems as if there was already a similar ticket in the past
(https://www.assembla.com/spaces/akka/tickets/3665-make-actorselection-working-when-using-untrusted-mode#/activity/).
Looks as if the problem still exists or exists again.
Regards
James Brems
--
Read
Hi,
I just recently updated to Scala 2.11 and I need some features from
2.4-SNAPSHOT
but there is no _2.11-2.4-SNAPSHOT in the repository.
Specifically this feature:
https://github.com/akka/akka/pull/15610/files
Where could I get it?
Thanks in advance.
-- Andrew
--
Read the docs:
Yes the docker probem. Do yo have any solution? without having this fix?
On Monday, January 12, 2015 at 8:40:09 PM UTC+8, 何品 wrote:
the docker one?
在 2015年1月12日星期一 UTC+8下午4:01:35，Andrew James Ramirez写道：
Hi,
I just recently updated to Scala 2.11 and I need some features from
2.4-SNAPSHOT
in Scala :-)
If you'd need moer advanced things you can look at the cake pattern
(that's pure scala, but sometimes gets a bit complicated).
Hope this helps!
On Tue, Nov 25, 2014 at 3:23 PM, Andrew James Ramirez
andrewjam...@gmail.com javascript: wrote:
Hi,
What is the best way to do
Hi,
What is the best way to do this? Currently what I'm doing is
class MainActor(Dependency1:ActorRef, Dependency2:ActorRef) = {
def receive ={
case TestMessage =
Dependency1 ! Test
}
}
object MainActor{
def props(Dependency1:ActorRef, Dependency2:ActorRef) = Props(classOf[
Any update on if/when this likely to be tackled?
The github issue seems to have been quiet for a while.
Cheers,
James
--
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
Hi Björn,
today I found out that the root cause seems to be the length of the fully
qualified class name of the snapshot class. If the length (pacakge+class
name) exceeds 60 characters an EOFException is thrown instead of calling
fromBinary.
Here's my reference.conf:
akka {
actor {
Can anyone point in the right direction with this one, probably something
obvious I'm missing!
I'm trying to debug a strange Cluster issue…
I have 3 actor systems in a cluster (all in the same JVM) communicating via
the distributed bus. (It's just a test app at the moment, and in production
Hi,
I have a similar problem. I am using a custom serializer for serializing a
snapshot. (extended from akka.serialization.Serializer):
akka {
actor {
serializers {
customSerializer = com.handler.util.CustomSerializer
}
serialization-bindings {
That's ok. I think I'll try the batching pattern (with max size and max
latency constraints) described in
https://groups.google.com/forum/#!topic/akka-user/todrna9GRS8/discussion
It seems to improve throughput substantially - in a quick test over a
simulated high latency link.
--
Read
Thanks, that looks useful.
I'm using spray.client at the moment to make the network call (to a
web-service). I'm not sure how the akka.io stuff would fit in to this
though?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Hi All,
Has anyone used Akka to implement something akin to the 'Smart Batching'
pattern that Martin Thompson describes in this blog post?
http://mechanical-sympathy.blogspot.co.uk/2011/10/smart-batching.html
I've seen this
topic:
Thank you so much!
On Thursday, March 20, 2014 7:41:34 AM UTC+8, James wrote:
I missed the live, is this going to be available on Yotube?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives
I missed the live, is this going to be available on Yotube?
--
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 because you
Hi gang, a question regarding shard failover
Here's my 3-node setup (using akka-2.3.0 rc3):
- backend 1
- backend 2
- frontend
All nodes initialize ClusterSharding at startup -- frontend supplies an
empty entryProps so that it does not host any regions.
Frontend starts pinging a range
Hi Tim,
We have a similar-ish setup over here. We ended up registering all nodes in
zookeeper and doing discovery through that. This works well for initial
cluster startup as well as nodes joining an existing cluster. It also works
well for hybrid environments that are not all on aws.
On Tue,
if this is an issue
in cluster sharding, cluster singleton manager in general, or a caveat
emptor with using ephemeral ports
On Tue, Feb 11, 2014 at 2:36 AM, Akka Team akka.offic...@gmail.com wrote:
Hi James,
the sequence you describe makes perfect sense to me, and the
ClusterSingletonManager
Hi gang.
What is the process for a node to gracefully exit a cluster?
Nodes in our system are going through this sequence:
- jvm gets the shutdown signal
- node calls cluster.leave(cluster.selfAddress)
- node waits until it sees MemberRemoved with its own address
- node gives
52 matches
Mail list logo
