Re: [akka-user] Re: Akka, Camel and RabbitMQ - Asynchronously acknowledging specific message
Hi Konrad, Not quite sure what you are referring to with basically the feature did not pull it's weight so it was discontinued. Are you saying that the akka-camel module is orphaned? If so, could someone update the docs? Thanks On Monday, 17 November 2014 23:25:14 UTC+11, Konrad Malawski wrote: Hi guys, to put some team perspective on it - basically the feature did not pull it's weight so it was discontinued. Also, for things like these external integrations, we feel it's better left up to the community as they really use these external libraries and care a lot about them on a daily basis, if we on the other hand take up such kind of integration, we much match release cycles and keep the module up to date in normal akka releases etc. So it is a lot of weight which needs to give equally as much value, in this case we thought it's better to leave out. As Todd already mentioned, there is this one library, and recently the guys from scalac have developed an akka-streams integration to rabbit: https://github.com/ScalaConsultants/reactive-rabbit So while akka-streams are still pre-experimental you could have a look into it as it looks pretty interesting, though it's your call if you want to go prod with these (streams are not yet supported by us, but will be soon). Happy hakking! On Sun, Nov 16, 2014 at 9:25 AM, Tal Pressman kir...@gmail.com javascript: wrote: Thanks, I'll have a look at it. I would have preferred something maintained by Typesafe or some other dependable organization, but I guess beggars can't be choosers. On Monday, November 10, 2014 4:19:33 PM UTC+2, Todd Nist wrote: @Tal, You may be able to use https://github.com/sstone/amqp-client in place of akka-amqp. -Todd -- 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 group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com javascript:. To post to this group, send email to akka...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- Cheers, Konrad 'ktoso' Malawski hAkker @ Typesafe -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Re: Basic HTTP client with Akka HTTP
Something like a akka-http based curl equivalent would be a great asset for testing, and also a good example. However, I am not sure how much the syntax will change from now to 1.0. If you want to play with it, one capability I would like to see is client-side bandwidth limiting (like the --limit-rate parameter of curl). That allows you to request a large amount of data at very low rate and see if the server blows up with an OOME due to wrong back pressure handling. On Fri, Nov 21, 2014 at 12:35 AM, Allan Brighton allane...@gmail.com wrote: I'm also interested in this. Here is a modified example http client and server that work on 0.11 (based on Rüdiger's example): https://gist.github.com/abrighton/acd43a6cd9c0b997c456 Any suggestions are welcome. I also plan to add the capability to upload files using this (with POST), which should work in a similar way. -- Allan On Thursday, November 20, 2014 8:16:26 PM UTC+1, Brian Topping wrote: Hi all, It looks like the syntax of handling client HTTP streams are under rapid revision, but I wanted to build a client with 0.11 anyway. I've found some examples, but none of them are quite up-to-date. If anyone cares to contribute, a little discussion is going on at https://gist.github.com/rklaehn/3f26c3f80e5870831f52 for 0.11. (A dead link for future seekers means the examples are better documented elsewhere!). Kind of wondering if a test client could be kept updated, maybe something paired with https://github.com/akka/akka/blob/release-2.3-dev/akka-http-tests/src/test/scala/akka/http/server/TestServer.scala. I think it would be completely reasonable to skip the HttpAuthentication directive that Johannes added on 3-Nov to the server, just something that can log in and dump the results of the /ping path would be awesome! Thoughts? Cheers, Brian -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Re: Akka, Camel and RabbitMQ - Asynchronously acknowledging specific message
Not quite sure what you are referring to with basically the feature did not pull it's weight so it was discontinued”? Are you saying that the akka-camel module is orphaned? Not camel, amqp. It was a module long time ago in the 1.x series: http://doc.akka.io/docs/akka-modules/1.3.1/modules/amqp.html Camel continues to be very useful on oh-so-many cases. -- Konrad 'ktoso' Malawski hAkker @ typesafe http://akka.io -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Design question on with akka persistence
I am trying to build a system to manage configuration values with akka-persistence. I would like to view all changes that has happened to a particular value in the configuration. I have the entire configuration as state in a PersistentActor and when someone queries for changes. I create a new PersistentView with what configuration key i need in the props and replay history on it to filter out the changes not needed and then query the filter changes and kill it with PoisonPill. All these happens in the query part of PersistentActor. Is this rightway to do it? Is there any simpler way to create a view out of the history in akka-persistence -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] how to implement the state migration with consistent hashing routing
Hi, all I have a question about consistent hashing routing in akka in my system, all actors are stateful, specifically: all the actor maintains one or more lists as their state, the message is indexed by a key. The router then forward the message according to the key to one of the actors which in turn save the message to the corresponding list (i.e. the list is bind with a key)... when a new node is added to the cluster, the router will update the hash function, and the future messages with the keys falling in the certain range will be forwarded to this new node *The problem, I also need to query the saved message...according to my understanding on the Akka implementation, the messages saved in the old routee will not be automatically migrated to the new joined one, so my query will only get partial result* is that true? if yes, how to implement this function? it seems that cluster-sharding can do this naturally, but just curious about if we can do with consistent hashing schema Thanks Nan -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: how to implement the state migration with consistent hashing routing
the only way is to replicate what cluster -sharding does? use a singleton instance to maintain everything? (but that is contrast with the discipline of DHT which is essentially a de-centralized design?) Best, Nan On Friday, November 21, 2014 7:10:42 AM UTC-5, Nan Zhu wrote: Hi, all I have a question about consistent hashing routing in akka in my system, all actors are stateful, specifically: all the actor maintains one or more lists as their state, the message is indexed by a key. The router then forward the message according to the key to one of the actors which in turn save the message to the corresponding list (i.e. the list is bind with a key)... when a new node is added to the cluster, the router will update the hash function, and the future messages with the keys falling in the certain range will be forwarded to this new node *The problem, I also need to query the saved message...according to my understanding on the Akka implementation, the messages saved in the old routee will not be automatically migrated to the new joined one, so my query will only get partial result* is that true? if yes, how to implement this function? it seems that cluster-sharding can do this naturally, but just curious about if we can do with consistent hashing schema Thanks Nan -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Use TypedActor or something else
Hello Vladimir, The typed actors in 2.x are not the best solution and introduce some overhead on invoking them. In general you should accept the fact that the network is message based anyway and it's more powerful to express things as messages (you reason about messages then), instead of hiding them under what looks like a method. If you're wondering if we're going to remove the current typed actors from 2.x, the answer is no - they're still useful (mostly as integration point with legacy code though). We're aiming to reimplement typed actors to be proper and included in Akka 3, but that's a long time ahead of us yet (1+ year). -- Konrad -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Re: Akka IO going into endless loop
Hi Peter,
Sorry I wasn't able to jump in to help in time.
Seems like you have it solved though, thanks for sharing your findings /
snippet.
As for streams we do want to and will provide something that has the
feature you're asking for with akka-streams,
we just haven't gotten the time yet to do it. Stay tuned and look forward
to it's 1.0! :-)
-- konrad
On Wed, Nov 19, 2014 at 3:59 PM, Peter peter.van.rensb...@gmail.com wrote:
Nobody wants to touch this one with a 10' pole ? :)
I was able to confirm my theory by sending my service a malformed packet
(ByteString(0, 0, 0, 0) header). I made this crude modification for now to
fix it:
@tailrec
def extractFrames(bs: ByteString, acc: List[ByteString]) //
: (Option[ByteString], Seq[ByteString]) = {
if (bs.isEmpty) {
(None, acc)
} else if (bs.length headerSize) {
(Some(bs.compact), acc)
} else {
val length = bs.iterator.getLongPart(headerSize).toInt
if (length 0 || length maxSize)
throw new IllegalArgumentException(
sreceived too large frame of size $length (max = $maxSize))
+ if (0 == length)
+ throw new IllegalArgumentException(
+ sreceived data but the frame header indicates 0 length?
discarding)
val total = if (lengthIncludesHeader) length else length +
headerSize
if (bs.length = total) {
println(slicing from {} to {} currently length {},
headerSize, total, bs.length)
extractFrames(bs drop total, bs.slice(headerSize, total) ::
acc)
} else {
(Some(bs.compact), acc)
}
}
}
Maybe it can help someone else..
--
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 group.
To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
--
Akka Team
Typesafe - The software stack for applications that scale
Blog: letitcrash.com
Twitter: @akkateam
--
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 group.
To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] actorOf raises StackOverflowError with long valid name
Hello again,
pinging this issue to inform you that I've reimplemented the path checking:
https://github.com/akka/akka/pull/16352
It's now faster and won't ever blow up.
Having that said, please remember that such huge paths put a huge burden on
remoting - avoid such long paths like fire.
On Wed, Nov 19, 2014 at 8:09 PM, Konrad Malawski kt...@typesafe.com wrote:
Hi Matias,
That is a rather crazy actor name!
Regex issue aside -are you sure you cannot condense the name into
something shorter?
Even if this would pass the check, if this ends up going through remoting
it will carry the entire actor path with it over the wire (!), which is a
lot of data!
We'll see what we can do about the check in the mean time...
On Wed, Nov 19, 2014 at 7:55 PM, Matias Tealdi matiastea...@gmail.com
wrote:
I am running akka 2.3.5 and I got some issues creating actor (actorOf
raises a StackOverflowError) with long name (around 8000 chars).
I was inspecting the code and found that in actor/ActorPath.scala there
is a regex which is used to validate the name.
*line 25:*val ElementRegex = (?:[-\w:@
=+,.!~*'_;]|%\p{XDigit}{2})(?:[-\w:@=+,.!~*'$_;]|%\p{XDigit}{2})*.r
I was wondering why it is necessary and what means %\p{XDigit}{2}
isn't it enough with [-\w:@=+,.!~*'$_;] ?
I guess that (a|b)* make the regex to expensive to check. Would be a
good idea to try to improve/rewrite it?
Regards,
Matias
*A test that makes it fails outside akka.*
val ElementRegex = (?:[-\w:@=+,.!~*'_;]|%\p{XDigit}{2})(?:[-\w:@
=+,.!~*'$_;]|%\p{XDigit}{2})*.r
val s =
[akka-user] Re: Akka Persistence and Kryo serialization
idstrategy = default
четверг, 20 ноября 2014 г., 18:25:05 UTC+3 пользователь Richard Bowker
написал:
I thought I'd experiment with using akka-kryo serializer to see what
difference it made to performance of persisting an event (defined by a
simple case class) compared to just allowing the default java serialization
after trying to follow the instructions in here
https://github.com/romix/akka-kryo-serialization I am stuck.
it appears to serialize the class I wanted (as I can see it in the
database), but on recovery of the actor I just get
RecoveryFailure was caused by: com.esotericsoftware.kryo.KryoException:
Encountered unregistered class ID: 1636190130
(akka.actor.ActorKilledException)
have I just got a setting wrong, or am I doing it all wrong! :)
thank you!
Rich
here are the relevant sections of the application.conf..
akka {
extensions =
[com.romix.akka.serialization.kryo.KryoSerializationExtension$]
actor {
serializers {
kryo = com.romix.akka.serialization.kryo.KryoSerializer
}
serialization-bindings {
com.example.State$DomainEvent = kryo
}
}
}
kryo {
# Possibles values for type are: graph or nograph
# graph supports serialization of object graphs with shared nodes
# and cyclic references, but this comes at the expense of a small
overhead
# nograph does not support object grpahs with shared nodes, but is
usually faster
type = nograph
# Possible values for idstrategy are:
# default, explicit, incremental
#
# default - slowest and produces bigger serialized representation.
Contains fully-
# qualified class names (FQCNs) for each class. Note that selecting
this strategy
# does not work in version 0.3.2, but is available on master and from
0.3.3 onward.
#
# explicit - fast and produces compact serialized representation.
Requires that all
# classes that will be serialized are pre-registered using the
mappings and classes
# sections. To guarantee that both sender and receiver use the same
numeric ids for the same
# classes it is advised to provide exactly the same entries in the
mappings section
#
# incremental - fast and produces compact serialized representation.
Support optional
# pre-registering of classes using the mappings and classes
sections. If class is
# not pre-registered, it will be registered dynamically by picking a
next available id
# To guarantee that both sender and receiver use the same numeric ids
for the same
# classes it is advised to pre-register them using at least the
classes section
idstrategy = explicit
# Define a default size for serializer pool
# Try to define the size to be at least as big as the max possible
number
# of threads that may be used for serialization, i.e. max number
# of threads allowed for the scheduler
serializer-pool-size = 16
# Define a default size for byte buffers used during serialization
buffer-size = 4096
# The serialization byte buffers are doubled as needed until they
exceed max-buffer-size and an exception is thrown. Can be -1 for no maximum.
max-buffer-size = -1
# If set, akka uses manifests to put a class name
# of the top-level object into each message
use-manifests = false
# Enable transparent compression of serialized messages
# accepted values are: off | lz4 | deflate
compression = off
# Log implicitly registered classes. Useful, if you want to know all
classes
# which are serialized. You can then use this information in the
mappings and/or
# classes sections
implicit-registration-logging = false
# If enabled, Kryo logs a lot of information about serialization
process.
# Useful for debugging and lowl-level tweaking
kryo-trace = true
# If proviced, Kryo uses the class specified by a fully qualified
class name
# to perform a custom initialization of Kryo instances in addition to
what
# is done automatically based on the config file.
#kryo-custom-serializer-init = CustomKryoSerializerInitFQCN
# Define mappings from a fully qualified class name to a numeric id.
# Smaller ids lead to smaller sizes of serialized representations.
#
# This section is mandatory for idstartegy=explciit
# This section is optional for idstartegy=incremental
# This section is ignored for idstartegy=default
#
# The smallest possible id should start at 20 (or even higher), because
# ids below it are used by Kryo internally e.g. for built-in Java and
# Scala types
mappings {
com.example.State$DomainEvent = 20
}
# Define a set of fully qualified class names for
# classes to be used for serialization.
# The ids for those classes will be assigned automatically,
Re: [akka-user] Re: Akka Persistence and Kryo serialization
Hey guys,
I just skimmed it, but it seems Evgeniy's suggestion should help.
If you want it to be explicit you'd have to list all messages,
including ActorKilledException
in the classes section it seems...
Let us know if that solved the problem - may be useful for other hakkers!
On Fri, Nov 21, 2014 at 3:46 PM, Evgeniy Ostapenko sml...@gmail.com wrote:
idstrategy = default
четверг, 20 ноября 2014 г., 18:25:05 UTC+3 пользователь Richard Bowker
написал:
I thought I'd experiment with using akka-kryo serializer to see what
difference it made to performance of persisting an event (defined by a
simple case class) compared to just allowing the default java serialization
after trying to follow the instructions in here
https://github.com/romix/akka-kryo-serialization I am stuck.
it appears to serialize the class I wanted (as I can see it in the
database), but on recovery of the actor I just get
RecoveryFailure was caused by: com.esotericsoftware.kryo.KryoException:
Encountered unregistered class ID: 1636190130 (akka.actor.
ActorKilledException)
have I just got a setting wrong, or am I doing it all wrong! :)
thank you!
Rich
here are the relevant sections of the application.conf..
akka {
extensions = [com.romix.akka.serialization.kryo.
KryoSerializationExtension$]
actor {
serializers {
kryo = com.romix.akka.serialization.kryo.KryoSerializer
}
serialization-bindings {
com.example.State$DomainEvent = kryo
}
}
}
kryo {
# Possibles values for type are: graph or nograph
# graph supports serialization of object graphs with shared nodes
# and cyclic references, but this comes at the expense of a small
overhead
# nograph does not support object grpahs with shared nodes, but is
usually faster
type = nograph
# Possible values for idstrategy are:
# default, explicit, incremental
#
# default - slowest and produces bigger serialized representation.
Contains fully-
# qualified class names (FQCNs) for each class. Note that selecting
this strategy
# does not work in version 0.3.2, but is available on master and from
0.3.3 onward.
#
# explicit - fast and produces compact serialized representation.
Requires that all
# classes that will be serialized are pre-registered using the
mappings and classes
# sections. To guarantee that both sender and receiver use the same
numeric ids for the same
# classes it is advised to provide exactly the same entries in the
mappings section
#
# incremental - fast and produces compact serialized representation.
Support optional
# pre-registering of classes using the mappings and classes
sections. If class is
# not pre-registered, it will be registered dynamically by picking a
next available id
# To guarantee that both sender and receiver use the same numeric ids
for the same
# classes it is advised to pre-register them using at least the
classes section
idstrategy = explicit
# Define a default size for serializer pool
# Try to define the size to be at least as big as the max possible
number
# of threads that may be used for serialization, i.e. max number
# of threads allowed for the scheduler
serializer-pool-size = 16
# Define a default size for byte buffers used during serialization
buffer-size = 4096
# The serialization byte buffers are doubled as needed until they
exceed max-buffer-size and an exception is thrown. Can be -1 for no maximum.
max-buffer-size = -1
# If set, akka uses manifests to put a class name
# of the top-level object into each message
use-manifests = false
# Enable transparent compression of serialized messages
# accepted values are: off | lz4 | deflate
compression = off
# Log implicitly registered classes. Useful, if you want to know all
classes
# which are serialized. You can then use this information in the
mappings and/or
# classes sections
implicit-registration-logging = false
# If enabled, Kryo logs a lot of information about serialization
process.
# Useful for debugging and lowl-level tweaking
kryo-trace = true
# If proviced, Kryo uses the class specified by a fully qualified
class name
# to perform a custom initialization of Kryo instances in addition to
what
# is done automatically based on the config file.
#kryo-custom-serializer-init = CustomKryoSerializerInitFQCN
# Define mappings from a fully qualified class name to a numeric id.
# Smaller ids lead to smaller sizes of serialized representations.
#
# This section is mandatory for idstartegy=explciit
# This section is optional for idstartegy=incremental
# This section is ignored for idstartegy=default
#
# The smallest possible id should start at 20 (or even higher),
because
# ids below it are used by Kryo internally e.g. for built-in Java and
#
RE: [akka-user] Use TypedActor or something else
Hello, Weren’t method calls originally referred to as messages in SmallTalk? The problem is not message passing, but the complete absence of type safety when doing so. It is quite ironic that it is developed in part by a company called “TypeSafe”. As it is, you can send any object to any actor, no matter how absurd it may be. The compiler will never catch sending the wrong object. Thanks to the robustness of Akka, a completely wrong object may not even cause much noise during runtime. If you intended to send a case class and forgot the constructor arguments, it will just send the companion object instead, with typically puzzling consequences. I am very happy to hear that typed actors are planned for Akka 3. Best, Oliver From: akka-user@googlegroups.com [mailto:akka-user@googlegroups.com] On Behalf Of Akka Team Sent: Friday, November 21, 2014 9:12 AM To: Akka User List Subject: Re: [akka-user] Use TypedActor or something else Hello Vladimir, The typed actors in 2.x are not the best solution and introduce some overhead on invoking them. In general you should accept the fact that the network is message based anyway and it's more powerful to express things as messages (you reason about messages then), instead of hiding them under what looks like a method. If you're wondering if we're going to remove the current typed actors from 2.x, the answer is no - they're still useful (mostly as integration point with legacy code though). We're aiming to reimplement typed actors to be proper and included in Akka 3, but that's a long time ahead of us yet (1+ year). -- Konrad -- 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 group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.commailto:akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.commailto:akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. *** This email message and any attachments are intended solely for the use of the addressee. If you are not the intended recipient, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. If you have received this message in error, please promptly notify the sender by reply email and immediately delete this message from your system. This message and any attachments may contain information that is confidential, privileged or exempt from disclosure. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. Message transmission is not guaranteed to be secure or free of software viruses. *** -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Reactive actor-actor communication
Hey Adam, sorry it took my a while to get to this email - been consuming the least responded / oldest email from the list throughout the week, not sure it this worked well or not yet... :-) By the way - isn't dropping demand messages a problem also in the current remote-streams implementation? There is no remote akka streams yet. If you mean tcp then the demand is just generated by the socket - not through passing tokens over the network. Sure, as we move away from peer-to-peer to more actors things do get more complex, but then, if you want to have back-pressure, you need some kind of feedback. I'd see it as a tradeoff - either lazily started actors, or backpressure. If the sharded actors are aggregate roots, for example, then lazy loading makes perfect sense. But if these are workers, of which there are a couple per host, then this wouldn't be a problem. Just depends on the type of work they are supposed to do. Yeah, exactly - I wanted to point out this distinction - as because of it the current ALOD still makes sense even once we get a fully backpressure based one. I'm wondering how many more functionalities are there in the code undiscovered ;) But that will change when the docs are there I guess :) Yeah... Soon we'll have docs, that should tremendously help in that respect :-) Right, well, originally I was wondering if Akka could replace Kafka+Zookeeper's message streams (which can be used to implement the scenario above: where there's a pool of producers, and a pool of consumers, all potentially on different hosts, and using Kafka they can stream messages reliably). With Kafka's delivery methods you bind each consumer to a number of partitions, so it would be as you describe, kind of point-to-point streams, which get re-balanced when a node goes down. Going this route, there could be a cluster-singleton service which assigns B-actors to A-actors, and creates streams between those two. These could be the reactive message streams from above. And to solve the demand-splitting problem (when a B has two As assigned), there could be simply more consumer-actors then producer-actors. This sounds like a very interesting use case. Would be awesome if you could tinker around it. Random fact is that Kafka is *so much used everywhere* that it definitely would find users/contributors I think :-) -- Cheers, Konrad 'ktoso' Malawski hAkker @ Typesafe -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Re: [akka-streams] Dynamically add route output port
Hm... I think that by using smart grouping and fanouts you'd be able to achieve this, but feels like we should perhaps think this one over with the team on a larger scale. Would you mind opening a ticket about a groupBy that an element can go into multiple groups https://github.com/akka/akka/issues please? -- konrad On Tue, Nov 18, 2014 at 4:59 PM, Oscar Broman oscar.bro...@gmail.com wrote: Some messages belong in more than one sub-stream - how would I accomplish that using groupBy? On Sunday, November 16, 2014 1:42:48 AM UTC+1, Oscar Broman wrote: Hello! I've been messing around with akka-streams lately and ran into some problems. I'm not sure where to go from this point. I have a TCP connection to an external data feed, in which I can subscribe to a wide variety of real-time data. What exactly will be subscribed to changes during runtime. Messages from the external feed can land in one or many actors, and these actors have varying lifespans. Where the messages end up depend on their type and different types of information inside them. How would I do this? From what I gather, using a FlexiRoute means I cannot add output ports after it has been materialized. At one point the stream could look like this: tcp io | transform(chop at LF) | map(_.utf8String) | map(FeedMessageParser(_)) // data is now Option(FeedMessage) | filter(_ != None) | /|\ / | \ / | \ / | \ /|\ / | \ / | \ TYPE=1 ID=3 TYPE=4,ID=4 // different prerequisites decide where the data flows next | | / \ | | / \ | | | | | | | | | | | | sub1 | | | sub2| | sub3 sub4 How do I do this best? Should I take a step back and look over my options, or is there a way to tame the river? -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- Akka Team Typesafe - The software stack for applications that scale Blog: letitcrash.com Twitter: @akkateam -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: [akka-streams] Dynamically add route output port
Alright, I have created the issue here: https://github.com/akka/akka/issues/16363 Thank you for the replies. On Sunday, November 16, 2014 1:42:48 AM UTC+1, Oscar Broman wrote: Hello! I've been messing around with akka-streams lately and ran into some problems. I'm not sure where to go from this point. I have a TCP connection to an external data feed, in which I can subscribe to a wide variety of real-time data. What exactly will be subscribed to changes during runtime. Messages from the external feed can land in one or many actors, and these actors have varying lifespans. Where the messages end up depend on their type and different types of information inside them. How would I do this? From what I gather, using a FlexiRoute means I cannot add output ports after it has been materialized. At one point the stream could look like this: tcp io | transform(chop at LF) | map(_.utf8String) | map(FeedMessageParser(_)) // data is now Option(FeedMessage) | filter(_ != None) | /|\ / | \ / | \ / | \ /|\ / | \ / | \ TYPE=1 ID=3 TYPE=4,ID=4 // different prerequisites decide where the data flows next | | / \ | | / \ | | | | | | | | | | | | sub1 | | | sub2| | sub3 sub4 How do I do this best? Should I take a step back and look over my options, or is there a way to tame the river? -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Re: [akka-streams] Dynamically add route output port
Thanks, we’ll look into it! On 21 November 2014 at 16:35:23, Oscar Broman (oscar.bro...@gmail.com) wrote: Alright, I have created the issue here: https://github.com/akka/akka/issues/16363 Thank you for the replies. On Sunday, November 16, 2014 1:42:48 AM UTC+1, Oscar Broman wrote: Hello! I've been messing around with akka-streams lately and ran into some problems. I'm not sure where to go from this point. I have a TCP connection to an external data feed, in which I can subscribe to a wide variety of real-time data. What exactly will be subscribed to changes during runtime. Messages from the external feed can land in one or many actors, and these actors have varying lifespans. Where the messages end up depend on their type and different types of information inside them. How would I do this? From what I gather, using a FlexiRoute means I cannot add output ports after it has been materialized. At one point the stream could look like this: tcp io | transform(chop at LF) | map(_.utf8String) | map(FeedMessageParser(_)) // data is now Option(FeedMessage) | filter(_ != None) | /|\ / | \ / | \ / | \ / | \ / | \ / | \ TYPE=1 ID=3 TYPE=4,ID=4 // different prerequisites decide where the data flows next | | / \ | | / \ | | | | | | | | | | | | sub1 | | | sub2 | | sub3 sub4 How do I do this best? Should I take a step back and look over my options, or is there a way to tame the river? -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- Konrad 'ktoso' Malawski hAkker @ typesafe http://akka.io -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Use TypedActor or something else
https://github.com/rkuhn/akka/tree/wip-g%C3%A5lbma-step1/akka-typed Again to remind everyone, zero guarantees about that branch and it’s contents, it’s mostly a research thing currently and quite some time away still. — k On 20 November 2014 at 18:15:01, Владимир Морозов (greenhos...@gmail.com) wrote: In one of threads (https://groups.google.com/forum/#!searchin/akka-user/Best$20way$20to$20integrate$20akka$20into$20a$20legacy$2Fexisting$20app/akka-user/SDHSJxjNYSY/cZgAdUklC28J) user Akka team write Typed actors are no longer recommended, we will eventually phase them out I already have application that use TypedActors inside, application grow up, but if Akka Team stop TypedActors improvement - my be I need to rewrite my application? I choose TypedActors because return types of all calls check at compile time. Any opinions or recommendation? Best regards, Vladimir -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- Konrad 'ktoso' Malawski hAkker @ typesafe http://akka.io -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] dependency between tests when using ImplicitSender and forget to consume a response with any of the expect-methods
Hi! I was bitten by some special behaviour when testing my actorSystem with the help of the ImplicitSender trait. I have two testmethods. In each of them, I send a message to an actor wrapped in a TestActorRef. In the first testcase, I don't consume the answer of the actor with one of TestKit's expect-Methods, because I check its state directly (testActorRef.underlyingActor) This causes the 2nd testcase to fail, because the first message was still in the receiving mailbox. Here is an example. https://gist.github.com/FloWi/55572324f2d3adb3d51b Do you have any suggestion on how to make the tests independent of each other? Or am I just using the ImplicitSender in a wrong way? (every answer *must* be consumed) Any insights are appreciated! Regards, Florian -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] System.currentTimeMillis update
Hi, i am testing my application but i need to modify actual date. I am using in whole application my custom now() method instead of System.currentTimeMillis(), so i can test more flexible. I am using akka scheduler but while scheduling jobs, System.currentTimeMillis will be used and if i set times in past in my tests, jobs will be executed immediately.I manage this using setNow before my tests but i can not do it while using akka. i can not set any date to return by System.currentTimeMillis. Is there any solution provided by akka? Kind regards, bilal -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] System.currentTimeMillis update
Hi Bilal, I'm not sure I understand, Akka's scheduler does not use System.currentTimeMillis. On Fri, Nov 21, 2014 at 10:57 PM, Bilal Günay bilalgu...@gmail.com wrote: Hi, i am testing my application but i need to modify actual date. I am using in whole application my custom now() method instead of System.currentTimeMillis(), so i can test more flexible. I am using akka scheduler but while scheduling jobs, System.currentTimeMillis will be used and if i set times in past in my tests, jobs will be executed immediately.I manage this using setNow before my tests but i can not do it while using akka. i can not set any date to return by System.currentTimeMillis. Is there any solution provided by akka? Kind regards, bilal -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- Cheers, √ -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Scala and Java Actors living together in one system.
Hello, I am being asked to leverage pre-existing actors in a Java lib but my codebase is in pure Scala. These pre-existing actors provide some aspect functionality like metrics and monitoring although I could implement my own. 1. Has anyone seen systems like this - is this a common design? I am just trying this out and find just creating those Java based actors, say using the context of a Scala based actor is confusing. Can I use a Scala Props to create a Java actor? I am not sure even what the stack traces look like for actor systems comprised of both Scala and Java actors when failures happen. I know this is a general question but am looking for lessons learned in case someone else was forced down a similar situation. Thanks -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: System.currentTimeMillis update
So you want to set the akka's scheduler's base/start/`now` time? 在 2014年11月22日星期六UTC+8上午5时57分40秒，Bilal Günay写道： Hi, i am testing my application but i need to modify actual date. I am using in whole application my custom now() method instead of System.currentTimeMillis(), so i can test more flexible. I am using akka scheduler but while scheduling jobs, System.currentTimeMillis will be used and if i set times in past in my tests, jobs will be executed immediately.I manage this using setNow before my tests but i can not do it while using akka. i can not set any date to return by System.currentTimeMillis. Is there any solution provided by akka? Kind regards, bilal -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: Scala and Java Actors living together in one system.
Just to be clear, these are all *Akka* actors, right? Parts of your post make it sound as if some other Java actor library might be involed. If it's just Akka actors written in Java, there's no problem creating Java actors in Scala and vice-versa. We have a mixed language codebase and that works just fine. On Friday, November 21, 2014 6:23:40 PM UTC-7, David wrote: Hello, I am being asked to leverage pre-existing actors in a Java lib but my codebase is in pure Scala. These pre-existing actors provide some aspect functionality like metrics and monitoring although I could implement my own. 1. Has anyone seen systems like this - is this a common design? I am just trying this out and find just creating those Java based actors, say using the context of a Scala based actor is confusing. Can I use a Scala Props to create a Java actor? I am not sure even what the stack traces look like for actor systems comprised of both Scala and Java actors when failures happen. I know this is a general question but am looking for lessons learned in case someone else was forced down a similar situation. Thanks -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
Re: [akka-user] Remoting, NAT, and Containers
Thanks for the info. I'll see if I can modify the container infrastructure at my company to make that work. If not, I'll be eagerly awaiting the Akka 2.4 release next year. On Monday, November 17, 2014 4:07:20 AM UTC-8, Akka Team wrote: On Sat, Nov 15, 2014 at 9:51 PM, Ryan Tanner ryan@gmail.com javascript: wrote: This is what we're doing in production. I'm working on a writeup which I will hopefully have up in a few weeks (I know I've said that before ;)) That would be a nice read, looking forward to it, Ryan! -- Akka Team Typesafe - The software stack for applications that scale Blog: letitcrash.com Twitter: @akkateam -- 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 group. To unsubscribe from this group and stop receiving emails from it, 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
