Hi Julian,
can you post more information about your code and what happens exactly when
you run it? What kind of key material do you have and how do you load it?
Are you using akka-http on the client side or on the server side?
Johannes
On Thursday, November 10, 2016 at 9:50:08 AM UTC+1, Julian
Hi Gang,
disassociation usually means some kind of connection error. Unfortunately,
akka currently doesn't say anything about why a connection was closed. This
will be improved in the next version.
See https://github.com/akka/akka/pull/22278
Johannes
On Wednesday, February 8, 2017 at 12:04:19
Hi Elmar,
could you first update to the latest version of akka-http, 10.0.3? We fixed
a few issues with the connection pool since akka 2.4.7.
Johannes
On Wednesday, February 15, 2017 at 5:12:18 PM UTC+1, Elmar Weber wrote:
>
> Hello,
>
> we are observing an issue with akka-http client side sinc
Hi,
these internal tests basically use it:
https://github.com/akka/akka-http/blob/master/akka-http-core/src/test/scala/akka/http/impl/engine/server/HttpServerSpec.scala
See
https://github.com/akka/akka-http/blob/master/akka-http-core/src/test/scala/akka/http/impl/engine/server/HttpServerTestSet
Hi,
you are applying the `alsoTo` clause to the wrong side of the connection.
You need to put it on the Sink-side. The way you have written it, the
`alsoTo` clause waits for your `Source.actorRef` to close the connection.
Try using
singleWebSocketRequest(...,
Flow[Message].alsoTo(Sink.onCompl
Hi Elliot,
the reason is not the type parameter directly, but the `: ClassTag` context
bound which introduces an implicit parameter list to your method. So, after
unfolding this syntactic sugar your withActor method basically looks like
this:
def withActor[A <: Actor](message: Any)(implicit ev
Hi,
injecting frames manually is not supported. Not supported means that we
don't offer an API that would allow users to do that.
That said, there's an internal API that allows to specify a frame handler
directly:
* You can case the `UpgradeToWebsocket` header to
`UpgradeToWebsocketLowLevel`
This SO questions lists a few alternatives about how to achieve that with a
reasonably new JVM:
http://stackoverflow.com/questions/12096403/java-shutting-down-on-out-of-memory-error
On Wednesday, February 22, 2017 at 11:27:21 AM UTC+1, Hippolyte Léger wrote:
>
> Hello,
> so I have a fairly large
Hi Richard,
the behavior you describe is as expected. The ask ActorRef has no relation
to the connection and so watching it doesn't have the desired effect.
The routing DSL doesn't even know about the concept of connections. It only
handles single requests and doesn't get notified in any way wh
Hi Manuel,
how did you determine that the problem is related to Akka? What did the
profiling say and where's the bottleneck now?
Answering your questions:
On Friday, April 28, 2017 at 12:10:50 AM UTC+2, Manuel wrote:
I guess that non-blocking code using Futures and work stealing by the
> fork
Dear fast application restarters,
we just released sbt-revolver 0.9.0 which is the first version of
sbt-revolver cross-built for sbt 0.13.x and 1.0.x. Thanks go to Olli
Helenius / @liff who contributed the sbt 1.0 compatibility changes
(#62).
We also merged a long-standing PR that allows to custo
Hi,
in akka-stream, processing is usually run in a fused fashion, i.e. without
further configuration one stream will run in a single actor so all
operations are run sequentially. In such a synchronous scenario, there's
little room for elements to ever get dropped because the actorRef stage
bas
closed issues can be found on the 10.1.0-RC2 milestone
<https://github.com/akka/akka-http/milestone/34?closed=1> milestones on
GitHub.
For this release we had the help of 23 contributors – thank you all very
much!
commits added removed
35 507 215 Johannes Rudolph
13
list of closed issues can be found on the 10.1.0-RC1
<https://github.com/akka/akka-http/milestone/26?closed=1>, 10.1.0-RC2
<https://github.com/akka/akka-http/milestone/34?closed=1>, and 10.1.0
<https://github.com/akka/akka-http/milestone/35?closed=1>milestones on
GitHub.
For
to
>> (stream.gnip.com) to be a virtual host (as they also provide other endpoints
>> such as api.gnip.com). I just tried with 1.0 and it gives me the same
>> result.
>>
>> Jeroen
>>
>> On Wednesday, July 15, 2015 at 4:47:10 PM UTC+2, Johannes Rudolph wrote:
>
Hi Jeroen,
On Thu, Jul 16, 2015 at 4:05 PM, Jeroen Rosenberg
wrote:
> Anyways, it's working as expected. I do have one small unrelated issue. The
> stream I am consuming is in Gzip format, so I'm unzipping the ByteStrings as
> they come in as part of my FlowGraph. However, when I try to unzip the
as this.
The `Gzip.decoderFlow`, in contrast, keeps this state between chunks.
--
Johannes
-------
Johannes Rudolph
http://virtual-void.net
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>&
Hi Adam,
On Mon, Jul 20, 2015 at 3:25 PM, Adam Shannon wrote:
> "All Internet-based HTTP/1.1 servers MUST respond with a 400 (Bad Request)
> status code to any HTTP/1.1 request message which lacks a Host header
> field."
>
> Is from RFC 2616
>
> I can confirm (the gist above) that akka-http is do
On Mon, Jul 20, 2015 at 3:37 PM, André wrote:
> I think the problem here is that we currently "absolutize" all requests
> (code).
>
> This will always fail with HTTP/1.0 request as they are always relative and
> don't carry a host header.
>
> I think the requestPreparation Flow in HttpServerBluePr
On Mon, Jul 20, 2015 at 3:59 PM, Nicolau Werneck wrote:
> It is unfortunate that I missed my error logs, but I'm glad you guys are
> taking a look at this!
>
> I confirmed that removing the Host header with curl just gives a 400, so it
> can't but just this. I was using 1.0-RC4, so maybe it was re
d from M2 to 1.0 this weekend and I never saw the server dying from
> these requests.
>
> On Mon, Jul 20, 2015 at 9:26 AM, 'Johannes Rudolph' via Akka User List
> wrote:
>>
>> On Mon, Jul 20, 2015 at 3:59 PM, Nicolau Werneck
>> wrote:
>> > It is un
t see any connections failing. In which way do you observe
connections to fail?
--
Johannes
---
Johannes Rudolph
http://virtual-void.net
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>&g
Hi Luc,
On Mon, Jul 27, 2015 at 4:49 PM, Luc Klaassen wrote:
> The connection does not give an error on the client side, but each time a
> message is sent it should print the message server side and then return a
> response with the reversed string. None of this is happening most of the
> time. I
c
>
> Op maandag 27 juli 2015 17:03:50 UTC+2 schreef Johannes Rudolph:
>>
>> Hi Luc,
>>
>> On Mon, Jul 27, 2015 at 4:49 PM, Luc Klaassen wrote:
>> > The connection does not give an error on the client side, but each time
>> > a
>> > messag
well so it's
really hard to see what's really going on.
--
Johannes
-------
Johannes Rudolph
http://virtual-void.net
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>&g
ver
> gets sent)
>
> Op dinsdag 28 juli 2015 08:16:09 UTC+2 schreef Johannes Rudolph:
>>
>> Hi Luc,
>>
>> On Mon, Jul 27, 2015 at 8:23 PM, Luc Klaassen wrote:
>> > If you check the git repository, i made some dumps with rawcap (to be
>> > able
&
hink its because I am getting the error No such instance method:
> 'akka.http.scaladsl.util.FastFuture'
>
> Did I compile wrongly?
>
>
>
>
> Am Dienstag, 11. August 2015 09:49:29 UTC+2 schrieb Johannes Rudolph:
>>
>> Hi john,
>>
>> it seems that
ckend flow.
>
>
> Am Donnerstag, 13. August 2015 10:18:39 UTC+2 schrieb Johannes Rudolph:
>>
>> Yes, good point.
>>
>> https://github.com/akka/akka/pull/18201
>>
>> On the other hand, I wonder why you need to implement TestResponse, john?
>> You
Thanks Adam.
On Tue, Aug 18, 2015 at 4:01 PM, Adam Shannon wrote:
> FYI If you want to add a class to your application here's an example:
> https://gist.github.com/adamdecaf/f83c7000d1b69bc29c4d
>
> On Tue, Aug 18, 2015 at 2:29 AM, Johannes Rudolph
> wrote:
>>
&
I apply transformation as Source data =
> source.via(encoder) but how do I get Source data.
>
>
> Flow.of(Integer.class) creates Flow that materializes to BoxUnit
>
>
> what Object stands for?
>
>
> On Tuesday, 11 August 2015 09:44:15 UTC+2, Johannes Rudolph wrote:
>>
>
On Wed, Aug 26, 2015 at 2:02 AM, Simon Schäfer wrote:
> The only thing I didn't understand was this part:
>
> Source.actorRef(1, OverflowStrategy.fail)
>
> When I replace the 1 with a 0 (which is allowed according to the
> documentation) I get this error message: Dropping element because there i
cs, send an email to
> akka-user+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
--
Johannes
-
Hi Henry,
couldn't you just use ActorSelection or `actorFor`? You could then start
with the most specific path and strip segments from the end until you find
an already existing actor to handle the rest of the URI.
Johannes
On Monday, February 29, 2016 at 10:39:42 PM UTC+1, Henry Story wrote:
Hi,
On Tuesday, September 13, 2016 at 4:26:55 PM UTC+2, rrodseth wrote:
> Is this the right way to debug the missing conversion?
> val prm = implicitly[Future[PimpedResult[(StatusCode,
Result[StatusDTO])]] => ToResponseMarshallable]
Try
implicitly[ToResponseMarshaller[Future[PimpedResult[(St
Hi Kunai,
On Thursday, September 15, 2016 at 7:49:18 AM UTC+2, Kunal Deshpande wrote:
>
> Few questions on back pressure
> 1. While using Flows in akka-streams using .via will a downstream flow
> apply back pressure to a flow upstream or is back pressure only signaled to
> a Source?
>
Backpress
Hi Paul,
a combinator to achieve something like this has been proposed several times
but I think there hasn't been consensus how to implement it exactly. The
latest approach is discussed here:
https://github.com/akka/akka-stream-contrib/issues/50
Johannes
On Thursday, September 15, 2016 at 8:
Hi Yaroslav,
no worries, this is a good question. It depends a bit on what kind of logic
you want to trigger. If you just want to do something, you can use
`mapMaterializedValue` to do something with the `OutgoingConnection` object
before materialization is complete.
If you want to prepend som
Hi Simon,
you could also try to split up the asynchronous computation and the actual
filtering like this:
def filterFunc(e: E): Future[Result]
xyz.mapAsync(n)(e => filterFunc(e).map(res => e -> res))
.via(statefulFilterGraphStage)
And then implement the `statefulFilterGraphStage` with whate
Hi Victor,
isn't that the same as the identity flow
`Flow.apply[T]` (or just `Flow[T]`)
?
But maybe I am missing something?
Johannes
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>
Klymko wrote:
>
> Basically I'd like to prepend something, but at the moment first
> ByteString received, I mean that prepended value should not be in the
> stream in case of connection failure.
>
> On Tuesday, September 20, 2016 at 1:44:56 PM UTC+3, Johannes Rudolph w
Hi Ronny,
I agree that error message is little helpful. Maybe you are sending plain
Strings to the actor created by Source.actorRef? (Still we might want to
improve the error message in that case.)
Johannes
On Monday, September 19, 2016 at 12:08:52 AM UTC+2, Ronny Bräunlich wrote:
>
> Hi every
d issues can be found on the 10.0.1 milestones on github.
For this release we had the help of 21 committers – thank you all very much!
Credits:
commits added removed
14 429 310 Johannes Rudolph
7207 16 Konrad `ktoso` Malawski
6238 109 Josep Prat
Hi Gaurav,
two small remarks:
* Try using `Http().singleRequest` instead of
`Souce.single().via(poolClientFlow).run`. Materialization (= `run` /
`runWith`) has a certain cost that can be avoided using
`Http().singleRequest`.
* Using `(1 to 1000).par.foreach` to run the benchmark may lead to
Hi Alan,
here are a few steps to get there:
* provide all your different authentication directives as values of type
`Directive1[T]` with T being the type of the principal found after
successful authentication.
* To build those, use either one of the existing authentication directives
starti
On Monday, January 2, 2017 at 1:42:27 PM UTC+1, Alan Burlison wrote:
>
> One question:
>
> headerValueByName("X-Auth-Key")).flatMap { (user, pass) =>
> // <- user flatMap for custom directives
>
> doesn't compile as the resulting value of type Directive[(String,
> String)] doesn't have a fl
an be found on the 10.0.3 milestone
<https://github.com/akka/akka-http/milestone/19> on github.
commits added removed
26 1607 175 Konrad `ktoso` Malawski
24 1445 1029 Johannes Rudolph
18673 209 Jonas Fonseca
13 2812 821 Josep Prat
5
Hi Eric,
we'd like to look into that. It looks as if a streams materializer is
holding on to some memory but we need more info to see what it keeps
exactly to.
Is this a reproducible scenario? Could you share the memory dump (in
private) with us? Otherwise, could you send the list of top consu
Yes, this seems to be a bug in sbt-assembly which gets triggered if you use
shading. See https://github.com/sbt/sbt-assembly/issues/205
>
>
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>
Hi David,
the 503 is generated by the timeout logic, see the
`akka.http.server.request-timeout` setting. See the timeout directives for
ways to change it based on the
request:
http://doc.akka.io/docs/akka-http/10.0.3/scala/http/routing-dsl/directives/timeout-directives/index.html
Regarding th
Hi,
XMPP is an application-level protocol while TCP is a transport-level
protocol. In fact, XMPP usually runs *on top of* TCP. So, yes, you can use
Akka TCP to implement XMPP.
Comparing XMPP to what you probably have right now is that in your current
application you used your own custom protoc
Hi Johnson,
if you use a `cachedHostConnectionPool`, the pool itself is a shared
resource that is managed by the infrastructure. If you don't do anything
else, the pool will shutdown itself after
the akka.http.host-connection-pool.idle-timeout has passed. If you want
manual control, the `HostC
Hello,
the error is thrown
here:
https://github.com/akka/akka/blob/master/akka-stream/src/main/scala/akka/stream/impl/io/TcpStages.scala#L303.
I agree it's hard to see why that error would happen. One thing that could
have happened is that a connection attempt was very slow and so the
idle-t
Hi Dimitry,
that message is a different one. It means that your code is issuing
requests with an explicit header `RawHeader("User-Agent", ...)` somewhere.
Johannes
On Thursday, February 23, 2017 at 8:10:03 PM UTC+1,
dmitriy...@alisagaming.com wrote:
>
> Hi everyone.
>
> I've been using akka wi
Hi Brice,
we changed the default behavior in akka-http. Now, all directives (i.e.
also `Directive0`) behave as `dynamic` did in spray before.
Johannes
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/addition
Hi Brice,
we previously recommended the stream variant
(`Source.single(request).mapAsync(1))`) but it turned out that this is not
a good idea as materialization has some cost and the API is more complex
than using `Http.singleRequest()` directly. So, using
`Http.singleRequest()` is the right w
Hi Alan,
yes, that's a valid use case. The route tree is usually traversed
completely until a Route matches. But if you know that the search can be
cut short, then `seal` is definitely a good solution. Another solution
would be to use only `handleRejections` which would have the advantage that
Hi Alan,
On Friday, March 17, 2017 at 12:25:09 PM UTC+1, Alan Burlison wrote:
>
> pathPrefix("root") {
>concat(
> pathPrefix("service1") { service1.route },
> pathPrefix("service2") { service2.route }
>)
> }
>
> That works fine with a path of say "/root/service1", but
Hi,
that sounds as if you haven't configured Akka HTTP to open an HTTPS server.
It's hard to say though, as you didn't post any code ;) What code did you
use to configure Akka HTTP to use HTTPS?
Johannes
On Tuesday, April 18, 2017 at 2:40:08 PM UTC+2, Abdeali Chandanwala wrote:
>
> Hi Arnout
I think there are a few things that should be treated separately:
* How to organize bigger route structures?
* How to implement some parts of the route structure as actors?
As Roland wrote before, a Route is just an alias for a function
`RequestContext => Future[RouteResult]`. This gives you u
I think that's a valid analogy. A while ago we were investigating similar
things and also arrived at that analogy. In practice, it turns out that
fused streams, i.e. multiple stream components that run in one actor will
skew measurements.
Not sure how much sense these analogies make when going
Hi Gavin,
the current version of Play is not compatible with Akka 2.5.0. This has
already been fixed for the upcoming Play 2.6 series. I created a ticket to
investigate if the compatibility fix should be backported to Play 2.5.x as
well: https://github.com/playframework/playframework/issues/725
Hi Thibault,
if you have the body of the response already as a Source,
you can create a response with a chunked entity from it like this:
HttpResponse.create()
.withEntity(HttpEntities.create(contentType, source))
Johannes
On Thursday, April 20, 2017 at 9:56:47 AM UTC+2, Thibault Meyer wrote
Thanks Julian for sharing the example. Indeed, using the BroadcastHub is
the recommended way to implement something like this.
On Saturday, April 22, 2017 at 1:09:19 AM UTC+2, Julian Howarth wrote:
>
> I may have misunderstood what you want to achieve, but you don't have to
> use actors if you'd
101 - 163 of 163 matches
Mail list logo
