Thanks a lot Adam , even i tried creating a sample project to check
feasibility of log4j 2 with akka it works .
On Fri, May 22, 2015 at 12:10 AM, Adam adamho...@gmail.com wrote:
Hi,
Where I work, we're using Akka with log4j2 (through slf4j binding) in
production.
We're handling billions
Thanks patrick for the input .
On Thu, May 21, 2015 at 1:43 PM, Patrik Nordwall patrik.nordw...@gmail.com
wrote:
I have not tried it, but here is something that you might find useful:
https://github.com/hseeberger/akka-log4j
An alternative is to use log4j2 with the slf4j binding and the Akka
Hi David, RC4 will also contain a prepackaged Flow for this purpose (it
won't make it into RC3 I am afraid).
-Endre
On Fri, May 22, 2015 at 2:23 AM, Konrad Malawski kt...@typesafe.com wrote:
Hi David,
seems we worked out that one on gitter during the evening accidentally :-)
// Note for
On Thu, May 21, 2015 at 9:18 PM, Viktor Klang viktor.kl...@gmail.com
wrote:
Hi Eugene,
Those two correspond to usage of the Scheduler to defer things for a
specified amount of time.
IIRC there was recently a discussion whether there could be a memory leak
related to this.
Which one are
We are using log4j2.
在 2015年2月23日星期一 UTC+8下午7:40:04，Martin Ford写道：
Hi,
In the Akka documentation
http://doc.akka.io/docs/akka/current/java/logging.html#logging-java
Typesafe recommend using Logback as the runtime SLF4J backend logger. I'm
just wondering what the reasons are for that
Following up on this question, what are the best practices around creating
anonymous actors, as long as you are not closing over context of a parent
actor?
On Friday, May 22, 2015 at 12:08:45 PM UTC-7, Jeff wrote:
Is it bad practice to pass in the Receive pf to an actor as part of the
Hi Roland,
This is great! Kudo's for the good work.
I wanted to get it going and noticed that http://akka.io/docs/ still
mentions two seperate http artifacts for scala and java. It is not listing
all available artifacts as mentioned on
Thanks, corrected!
22 maj 2015 kl. 22:17 skrev Jeroen Gordijn jeroen.gord...@gmail.com:
Hi Roland,
This is great! Kudo's for the good work.
I wanted to get it going and noticed that http://akka.io/docs/
http://akka.io/docs/ still mentions two seperate http artifacts for scala
and
I am using Akka 2.3.10,
akka-slf4j_2.11 (2.3.10)
and logback_classic (1.0.5)
On Friday, May 22, 2015 at 5:18:18 PM UTC-7, TS wrote:
I have setup Akka logging and using logback with slf4j.
Everything works fine except that I do not see WARNING's (I see INFO,
DEBUG, ERROR)
This is a
Not really an akka question.. More of a logback question. Using logback
1.0.5
I have
%highlight(%-5level) in my pattern for logback.
I am seeing the messages stay bold (highlighted) after any error.
Is there a way to 'unbold' it after an error for the other levels
(TRACE,INFO, DEBUG,
Let's take this code..
public void testIt() throws IOException {
new JavaTestKit(system) {{
final Props props = Props.create(MyActor.class);
final ActorRef subject = system.actorOf(props);
ByteString someBytes =
I have setup Akka logging and using logback with slf4j.
Everything works fine except that I do not see WARNING's (I see INFO,
DEBUG, ERROR)
This is a logback config issue.. I also noticed when the error is
highlighted (bold font) the font stays bold for all other levels. Is there
a way to
Hi,
The way I understand materialisation in Akka Streams is that the
ActorFlowMaterializer will create a number of actors which are used to
process the flows within a stream. Is it possible to control the number and
location of actors that get materialised when running a Flow? I'd like to
be
Hello. Case is looks like I have a big file on some server. And I want to
handle it without saving. I need to send cookies and a filled form to get
file. Then file will be parsed line by line.
So, in my mind it looks like Flow[HttpRequest, Source[ByteString], _]
First of all, I couldn't find
Thanks Patrik, I actually thought of that too but was wondering if there
is any testkit support for it. Then ended up impl a test-only actor that
gathers all received messages and my test suite can get them as a stream
(blocking if the stream is empty in order to wait for the threading bit
to
Thanks Patrik!!.
On Friday, May 22, 2015 at 8:13:53 AM UTC-5, Patrik Nordwall wrote:
Use the ActorRef. ActorSelection is mainly intended for initiating
communication between two remote actors, i.e. when you don't have an
ActorRef
.
/Patrik
On Thu, May 21, 2015 at 5:05 AM, Hareesh
On Fri, May 22, 2015 at 3:28 PM, Viktor Klang viktor.kl...@gmail.com
wrote:
Thread subject: [akka-user] system.scheduler.scheduleOnce consumes Heap
over time
That had no confirmed leak, things got eventually GC-ed.
-Endre
--
Cheers,
√
On 22 May 2015 08:59, Endre Varga
On Friday, May 22, 2015 at 9:37:28 AM UTC-4, Patrik Nordwall wrote:
If you are using a bounded mailbox you should use zero
mailbox-push-timeout-time, which means that messages may be dropped.
Otherwise you will block threads, which is probably not desired.
If I simply allow messages to
Thread subject: [akka-user] system.scheduler.scheduleOnce consumes Heap
over time
--
Cheers,
√
On 22 May 2015 08:59, Endre Varga endre.va...@typesafe.com wrote:
On Thu, May 21, 2015 at 9:18 PM, Viktor Klang viktor.kl...@gmail.com
wrote:
Hi Eugene,
Those two correspond to usage of the
On Thu, May 21, 2015 at 10:33 AM, Jeroen Rosenberg
jeroen.rosenb...@gmail.com wrote:
I'm using Akka-Http 1.0-RC2 and I'm building a simple streaming server
(Chunked HTTP) and client using reactive streams / flow graphs.
My server looks like this (simplified version):
object Server extends
On Thu, May 21, 2015 at 1:46 PM, Przemek Piotrowski
piotrowski.prze...@gmail.com wrote:
Is there some workaround to use actors under BalancingPool in Akka 2.3.x ?
The issue says that bug activates when actors are children of Router.
Should I create them externally from the router and then add
I would start an actor on that path that forwards all messages to the test
probe.
/Patrik
On Thu, May 21, 2015 at 7:22 AM, Kostas kougios
kostas.koug...@googlemail.com wrote:
Hi, I am trying to test actor code that uses actorSelection:
val path = RootActorPath(member.address, name =
Use the ActorRef. ActorSelection is mainly intended for initiating
communication between two remote actors, i.e. when you don't have an
ActorRef
.
/Patrik
On Thu, May 21, 2015 at 5:05 AM, Hareesh Jagannathan harjag...@gmail.com
wrote:
I am new to Akka and I am bulding a Data ingestion system as
If you are using a bounded mailbox you should use zero
mailbox-push-timeout-time, which means that messages may be dropped.
Otherwise you will block threads, which is probably not desired.
It should be possible to solve this with pull pattern that is not awkward.
Let W request a bunch a items
The forwarding actor is actually included in
akka.testkit.TestActors.ForwardActor
https://github.com/akka/akka/blob/v2.4-M1/akka-testkit/src/main/scala/akka/testkit/TestActors.scala#L27-L31
in
Akka 2.4-M1.
/Patrik
On Fri, May 22, 2015 at 3:16 PM, Konstantinos Kougios
nice
On 22/05/15 14:49, Patrik Nordwall wrote:
The forwarding actor is actually included in
akka.testkit.TestActors.ForwardActor
https://github.com/akka/akka/blob/v2.4-M1/akka-testkit/src/main/scala/akka/testkit/TestActors.scala#L27-L31 in
Akka 2.4-M1.
/Patrik
On Fri, May 22, 2015 at 3:16
Could be a scheduling artifact?
--
Cheers,
√
On 22 May 2015 15:29, Endre Varga endre.va...@typesafe.com wrote:
On Fri, May 22, 2015 at 3:28 PM, Viktor Klang viktor.kl...@gmail.com
wrote:
Thread subject: [akka-user] system.scheduler.scheduleOnce consumes Heap
over time
That had no
Dear hakkers,
we—the Akka committers—are pleased to announce the third release candidate for
Akka Streams HTTP. The most notable changes since 1.0-RC2 are:
we integrated the Scala and Java DSLs within combined artifacts again, since
the separation was only superficial and did not justify the
From API docs:
* Read condition for the [[MergeLogic#State]] that will be
* fulfilled when there are elements for any of the given upstream
* inputs, however it differs from [[ReadAny]] in the case that both
* the `preferred` and at least one other `secondary` input have demand,
Hi giampaolo,
Sorry for the delay. This question must have fallen between the cracks.
I hope you have found the problem. This should absolutely work. Let me know
otherwise and I will investigate.
Regards,
Patrik
On Mon, May 11, 2015 at 3:21 PM, Giampaolo giampaolo.trapa...@gmail.com
wrote:
Hi all,
Some messages that arrive in dead letters are of no concern at all, such as
`Tcp.Close` (which happens a lot when using Akka IO).
Is there any way to filter out the logging of these particular dead letter
messages so that they don't clutter up the log?
Best regards,
Sam
--
Is it bad practice to pass in the Receive pf to an actor as part of the
constructor arguments, assuming all vals it closes over are consts?
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Awesome, especially the documentation, I was really looking forward to that.
Cheers!
On Friday, 22 May 2015 17:43:53 UTC+2, rkuhn wrote:
Dear hakkers,
we—the Akka committers—are pleased to announce the third release candidate
for Akka Streams HTTP. The most notable changes since 1.0-RC2
No, not referring to the effort required to keep up with the Akka team :)
I just came across this:
https://github.com/scalapenos/stamina
and wondered if anyone had any thoughts about it.
I'm itching to pitch Akka persistence, but would like the read side and
serialization to be well-baked.
--
Hi Chanan,
I am not aware of tools of the like of Swagger for plain actor messaging.
What we see people do and also encourage is to keep Actor messages in their
companion objects.
For example like so:
object RegistrationActor {
case class Register(…)
object Registration {
trait Failure
35 matches
Mail list logo
