[akka-user] Order of log lines is mixed when 3rd party logs write directly to SLF4J

Hi, While using in akka's infrastructure (akka.event.Logging), log lines are written asynchronously. If 3rd party code that writes directly to SLF4J runs within the context of an actor, this can lead to condition where akka code performed before the 3rd party code only gets logged after the 3rd

Re: [akka-user] Order of log lines is mixed when 3rd party logs write directly to SLF4J

Thanks for the quick response! On Monday, June 19, 2017 at 4:33:50 PM UTC+3, Konrad Malawski wrote: > > You can always just us slf4j directly - use an async appender in the impl > (logback2 AFAIR provides one and others as well) and you're good. > > There's no requirement to use ActorLogging,

[akka-user] ANNOUNCE: Akka 2.5.3

Dear hakkers, We are pleased to announce a new patch release of Akka 2.5. Some notable improvements and bug fixes in 2.5.3 are: - Fix Akka Remoting issue (ResendUnfulfillableException) after transport failure detection, #23010 -

Re: [akka-user] Order of log lines is mixed when 3rd party logs write directly to SLF4J

You can always just us slf4j directly - use an async appender in the impl (logback2 AFAIR provides one and others as well) and you're good. There's no requirement to use ActorLogging, we only have it to not depend on a specific logging API in akka-actor itself. -- Konrad `ktoso` Malawski Akka

[akka-user] Akka http client not responsing

Hi, I'm migrating a big project from dispatch to Akka http for client calls. I'm having an issues in our tests, we're sending a lot of calls and at some point I'm not getting any response, i.e. with the request-level API the Future never completes. >From what I have read, that can happen when

[akka-user] Strange java.lang.VerifyError with ActorSystem initialization

I'm encountering this issue which I've never seen before, and was wondering if someone could point me in the right direction. I have some Akka streams 2.4.10 code (with Scala 2.11.8) that is embedded into a GlassFish 4.0 server running Oracle Java 1.8.0_131-b11. All this is wrapped into a

[akka-user] Re: Akka http client not responsing

Hi, make sure you catch all exceptions, for example if the unmarshaller dies you still have to consume the entity. For example by putting a recoverWith case on the unmarshaller's future something like this: Unmarshal(response.entity) .to[T] .recoverWith { case reason: Throwable =>

[akka-user] Is ExecutionContext.reportFailure working?

While I was trying to stub out an execution context to test concurrent code, I noticed some surprising behavior demonstrated below. I would have expected the exception thrown by the Future to cause reportFailure to be invoked. To my surprise, reportFailure never got called at all, and the

[akka-user] Re: [akka-http] Tagless Final and ToResponseMarshallable

In order to avoid the mix-in, you should rely on ad-hoc polymorphism, i.e. use implicits to get an evidence of a Marshaller for your type. `Marshaller` is basically a typeclass so stick to that pattern in your solution. El jueves, 15 de junio de 2017, 23:21:17 (UTC+2), Jeff escribió: > > That

Re: [akka-user] State Replication in ORMultiMap

ORMap and ORMultiMap have support for deltas. Nested deltas can be difficult so the current implementation is sending the full state of the changed entry of the ORMap, i.e. the 1000 items of the "a" ORSet in your example. There is variant of ORMultiMap that supports nested deltas but it has some

[akka-user] Favorite execution mode for Akka "batch"

Hi there, I made an akka based tool that collect tasks from various sources and publish them to one system. Mainly, I havd many 'collectors' that send a `TaskFoundEvent` to an event bus. And one 'publisher' that create the task on the target system. This tool should be executed on a