Functions aren't serializable, they can't be sent across the network so
this would break location transparency.
Perhaps with spores/SIP-21 you could shoehorn something in but there still
seem to be a lot of pitfalls. And of course I don't think there's anything
similar for the Java API.
To
Charles, as Heiko pointed out you need to have an implicit Materializer in
scope. This resolved my compilation error
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search
Hi everyone,
it seems that node/cluster information reported by JMX isn't reliable. I
getting into the situation when leader can't perform it's duties, because
some nodes are unreachable (they were shutdown) and others are joined. Here
is what is reported in log by leader node:
https://gist.gi
Greetings,
When I look at standard examples with Akka we always see very specific
typed actors that handle messages of a certain type and return certain
values. This tends to lead to big recieve methods with large amounts of
code in them or a plethora of helper messages. I got to thinking abou
I get the following log messages every time I send a message to to the
remote system:
backend [DEBUG] [08/21/2015 23:26:40.513]
[default-akka.actor.default-dispatcher-23]
[akka://default/system/IO-TCP/selectors/$a/18] Attempting connection to
[/127.0.0.1:]
backend [DEBUG] [08/21/2015 23:26
Andrew-
There should be no problem using mapAsync in the handler since mapped
elements will be emitted in order and, thus, joined with the proper message
for the ack sink.
Quote from the docs: "These Futures may complete in any order, but the
elements that are emitted downstream are in the same
/java.lang.ClassNotFoundException: akka.event.slf4j.Slf4jLogger/
are you sure that akka-slf4j.jar is on your classpath? see
http://doc.akka.io/docs/akka/2.3.12/scala/logging.html#SLF4J
-Michael
On 08/21/15 06:50, M.Ahsen Taqi Kazmi wrote:
i am using hazelcast 3.5 with Scala 2.11.1 and akka
Well, I was able to achieve needed behavior with following flow scheme:
Flow() { implicit builder ⇒
val promises = builder add Source(() ⇒ Iterator continually Promise[O]())
val fan = builder add Broadcast[Promise[O]](2)
val zip = builder add Zip[I, Promise[O]]()
val flow = builder add F
i am using hazelcast 3.5 with Scala 2.11.1 and akka 2.3.8
i have implemented StoreLoad class, in store method i want to send the
object to an actor which stores the object in mongo
here is store method from my StoreLoad class
override def store ( uuid : Int, abc : Abc){
Try the JVM option -XX:+UseG1GC, assuming you are using at least JVM
7uLatest where latest should be 79 or 80. The new GC algorithm doesn't stop
world, it works more often and can make your application a bit slower (on a
very hyper micro-level) but GC will now be consistent.
On Friday, August 2
Hi Andrew,
The way I have solved that problem was to broadcast the flow, Flow.map out
the Job wrapper, go into the premade flow, then zip the two together before
mapping the resultant back into the Job wrapper
~> broadcast ~> mapOutWrapper ~> f1 ~> zip ~> mapIntoWrapper ~>
broadcast
11 matches
Mail list logo
