[akka-user] akka-camel: is remoting required for using akka producer

I am working on spray and akka based application in which there are some services which require to call other REST services hosted on different server. Currently our application is built on top of local actor system. We have plan to gradually port our application in a clustered environment in c

Re: [akka-user] Configuring an Actor listening to two different protocols

Sorry for late reply. I was trying to make the spray service actor, a part of the akka cluster directly. I could not find a proper example for the same. So, just wanted to know is that possible. On Thursday, January 30, 2014 12:56:42 PM UTC+5:30, √ wrote: > > Hi Valbhav, > > What did you try a

[akka-user] Serialization and ScalaBuff

Hi people, In the default configuration, the serializer for ProtocolBuffer is enabled with akka { actor { serialization-bindings { "com.google.protobuf.GeneratedMessage" = proto ... However, the ScalaBuff generates classes with GeneratedMessageLite (code for the generator

[akka-user] BitTorrent Client written in Akka

Hello all, After playing with Akka for some time and then learning about it properly on the Coursera principles of reactive programming course, I decided to try and write a BitTorrent client. The new reactive IO features seemed like a perfect abstraction for managing the multiple concurrent con

Re: [akka-user] Re: akka cluster seed nodes on ec2

Scott, What did you ever end up doing about this? As yet, I have not seen any decent story for auto-scalling akka-cluster on AWS; it strikes me that over a long enough period all the seed nodes could be reaped by the ASG, but that there would be enough folks wanting to do this that there would

Re: [akka-user] persistence.channel question

Hello Martin, After finishing reading the persistence and rereading the actoRef/actorPath documentations plus your answers it becomes quite clear, and I Always forget about ActorPath.fromString... Thanks a lot, michael -- >> Read the docs: http://akka.io/docs/ >> Ch

Re: [akka-user] Using remote actors with SSL results in dead letters

Hi, Great that you found a solution. Tanks for sharing. B/ On 6 February 2014 at 16:58:14, Ekroth (andree.ekr...@gmail.com) wrote: Hello, I got it to work, I found out that I could enable ssl-debugging in Java by using JAVA_OPTS. Which got me this log: https://gist.github.com/ekroth/ca8afe582

Re: [akka-user] Using remote actors with SSL results in dead letters

Hello, I got it to work, I found out that I could enable ssl-debugging in Java by using JAVA_OPTS. Which got me this log: https://gist.github.com/ekroth/ca8afe58253c2b7e22c1 [info] %% Initialized: [Session-1, SSL_NULL_WITH_NULL_NULL] [info] New I/O worker #4, fatal error: 40: no cipher suites i

Re: [akka-user] persistence.channel question

Hi michael, On 06.02.14 14:50, delasoul wrote: Hello Martin, I have some other questions related to Channel usage in akka-persistence: In eventsourced a channel and its destination where "married" when creating the channel: val channel = extension.channelOf(DefaultChannelProps(channelId, de

Re: [akka-user] Akka global logging to slf4j

That actually did help, thanks a lot! Tag: Fix akka log duplication On Thursday, February 6, 2014 5:18:21 PM UTC+4, Oleg Zhurakousky wrote: > > Although I can't reproduce your issue (so may be sharing a reproducible > sample would help) > But this is somewhat common issue and could be managed wi

Re: [akka-user] persistence.channel question

Hello Martin, I have some other questions related to Channel usage in akka-persistence: In eventsourced a channel and its destination where "married" when creating the channel: val channel = extension.channelOf(DefaultChannelProps(channelId, destination)) Why has this changed for akka-persiste

Re: [akka-user] Akka global logging to slf4j

Although I can't reproduce your issue (so may be sharing a reproducible sample would help) But this is somewhat common issue and could be managed with turning off the aditivity in log4j Try to add this line: log4j.additivity.akka.actor.RepointableActorRef=false Cheers Oleg On Thu, Feb 6, 2014 at

Re: [akka-user] Using remote actors with SSL results in dead letters

Hi, On 6 February 2014 at 13:24:45, Ekroth (andree.ekr...@gmail.com) wrote: Hello again, Right, I'm running Linux, the /dev/random blocking fixed the delay, but still results in dead letters. I tried changing the key pairs to an example I found in the Akka bug tracker, but still the same probl

Re: [akka-user] Threading Issues of Using DiagnosticLoggingAdapter in UntypedActor

Well, you are not creating MDC, rather getting it from 'intmSoapResponse', so not sure what's going on there and if there are possibilities of another thread making entries to it. Also, is it possible that even within the same Actor you may be modifying MDC from separate threads (e..g, from Future

[akka-user] Akka global logging to slf4j

Problem i currently trying to solve is that i need to log all actors with log level INFO while all other loggers are on ERROR. Somehow i found out that if you configure log4j like: log4j.rootLogger=ERROR, MY_APPENDER ###Akka log4j.logger.akka.actor.RepointableActorRef=INFO, MY_APPENDER and even

[akka-user] Threading Issues of Using DiagnosticLoggingAdapter in UntypedActor

Hi, I'm using Akka 2.3.0-RC2. In my UntypedActor class, I use DiagnosticLoggingAdapter to write logs. Randomly my code throws the following exception: java.util.ConcurrentModificationException: null at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) ~[na:1.6.0_37] at java.util.HashM

Re: [akka-user] Using remote actors with SSL results in dead letters

Hello again, Right, I'm running Linux, the /dev/random blocking fixed the delay, but still results in dead letters. I tried changing the key pairs to an example I found in the Akka bug tracker, but still the same problem. I posted an older log of the client by mistake, I always start the server

Re: [akka-user] Running an Actor System inside a JEE 7 application server

An impassioned 'cri du coeur' ! On Wednesday, February 5, 2014 3:46:04 PM UTC, Justin du coeur wrote: > > On Fri, Jan 31, 2014 at 5:49 PM, Tin Tvrtković > > > wrote: > >> To everyone suggesting ditching the AS: you're preaching to the choir >> here, which is why I was trying to use Akka in the

Re: [akka-user] ClusterClient continues to send to dead node

I tried making the scenario a bit simpler: - start 4 nodes - start client, observe no timeouts - kill 1 node - observe node is downed - observe timeouts on client continue indefinitely - kill client - start new client - observe timeouts on newly started client continue indefinitely The fact that

Re: [akka-user] Re: Occasionally active actors

On Thu, Feb 6, 2014 at 11:12 AM, Roger Alsing wrote: > Would it be possible to simulate this behavior using an > VirtualActorPathContainer (dont remember the exact name, the type that the > remote daemon inherits from) so that if one try to select an actor in such > container, it gets incarnated

[akka-user] Re: Occasionally active actors

Would it be possible to simulate this behavior using an VirtualActorPathContainer (dont remember the exact name, the type that the remote daemon inherits from) so that if one try to select an actor in such container, it gets incarnated on demand. and then kills itself after x amount of time.

Re: [akka-user] ClusterClient continues to send to dead node

On Thu, Feb 6, 2014 at 10:31 AM, Tycho Lamerigts wrote: > In the meantime, I have looked at the logs a bit more. If I do my test > with 3 nodes, then kill 1 node, the ClusterClient seems to always recover > correctly, i.e. it continues using the 2 surviving nodes and there are no > timeouts. If I

Re: [akka-user] ClusterClient continues to send to dead node

In the meantime, I have looked at the logs a bit more. If I do my test with 3 nodes, then kill 1 node, the ClusterClient seems to always recover correctly, i.e. it continues using the 2 surviving nodes and there are no timeouts. If I start with 4 nodes, then kill 1 node, it nearly always causes

Re: [akka-user] ClusterClient continues to send to dead node

Using 2.2.3. The log of the surviving nodes shows the failing mode as unreachable and then quarantined, I think that means it is correctly downed. I have DEBUG logging enabled. But not sure how to track the Send() going from client to receptionist to detination actor and back. How can I tell fr

Re: [akka-user] ClusterClient continues to send to dead node

I use version 2.2.3. I can see the failing node being flagged as unreachable and then as quarantined by the surviving nodes, I think that means it is correctly downed? I have akka.loglevel and akka,stdout-loglevel at DEBUG, but it is not very clear what to look for. For example, it is not clear