I am trying to achieve two way real time communication between akka-http
websocket server and client
server code :
object EchoService {
def route: Route = path("ws-echo") {
get {
handleWebSocketMessages(getFlow())
}
} ~ path("send-client") {
get {
sourceQueue.map(q
What if I dont want any auto join at all. I took out the seed nodes and I
get the same problem.
On Saturday, June 11, 2016 at 2:24:10 PM UTC-5, Rafał Siwiec wrote:
>
> akka.remote.netty.tcp.port - instead of 0 you should use 2551.
--
>> Read the docs: http://akka.io/docs/
>
akka.remote.netty.tcp.port - instead of 0 you should use 2551.
--
>> 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
The use case is I have a bunch of entities that are in an RDBMS and they
are represented in memory by an actor per entity and those entities are
spread across the cluster using ClusterSharding (assuming I can figure out
why it wont start for me). However, on a per-node basis I would like to be
You need to pass something, but it can any object, e.g. a String that you
don't use.
/Patrik
lör 11 juni 2016 kl. 01:15 skrev Aditya Prasad :
> Newb question: what if I don't have an event for the deferAsync() call? I
> just want to execute a block with the guarantee that it runs after
> persist
That's Aeron threads. We launch the Aeron media driver embedded in the same
jvm as the application by default. It's also possible to run it as a
separate process, which can be an advantage if you have several jvms on the
same machine.
You will also see a new thread named taskrunner, that is create
Hi Patrik,
I got it running and will test it during the week with low frequency
messages (FX market data)
I see now two new threads which I assume are event loops threads:
- driver-conductor
- aeron-client-conductor
I'm guessing the load falls now into the remote-dispatcher?, do you have
Leave the netty dependency in. We have not made a clean separation of that
yet.
/Patrik
lör 11 juni 2016 kl. 16:19 skrev Guido Medina :
> I got this exception because I'm explicitly excluding Netty 3 as
> dependency, should I leave it? but then, why is Netty 3 still in there?
>
>
> On Saturday, Ju
I got this exception because I'm explicitly excluding Netty 3 as
dependency, should I leave it? but then, why is Netty 3 still in there?
On Saturday, June 11, 2016 at 3:05:45 PM UTC+1, Guido Medina wrote:
>
> This stack trace is better as it shows the jar it comes from:
>
> ERROR 15:03:06,933 Act
This stack trace is better as it shows the jar it comes from:
ERROR 15:03:06,933 ActorSystemImpl - Uncaught error from thread
[DevCluster-akka.remote.default-remote-dispatcher-8] shutting down JVM
since 'akka.jvm-exit-on-fatal-error' is enabled
java.lang.NoClassDefFoundError: org/jboss/netty/cha
My first try failed, I thought Netty-3 wasn't being used so I excluded it
as it is being pulled by akka-remote artery version, and I got the
following exception:
java.lang.NoClassDefFoundError: org/jboss/netty/channel/ChannelHandler
at java.lang.Class.getDeclaredConstructors0(Native Method)
at j
Hi Guido,
The mini-doc is in this announcement email.
1. Change the version number in your build.
2. Add the config listed
3. Replace akka.tcp with artery in any address paths that you use, e.g.
seed-nodes
That should be all. Then it should just work. Let us know how it goes or if
you have more q
Roland, thanks - all is absolutely clear now! :)
On Saturday, June 11, 2016 at 2:20:48 PM UTC+3, rkuhn wrote:
>
> Andrew,
>
> there seem to be a few misunderstandings here:
>
>
>- HTTP by design requires TCP as its transport
>- akka-http implements HTTP using akka-streams which in turn us
Andrew,
there seem to be a few misunderstandings here:
HTTP by design requires TCP as its transport
akka-http implements HTTP using akka-streams which in turn uses Akka IO for the
TCP part—no Netty anywhere
akka-remote has nothing to do with Akka IO, akka-stream, or akka-http
Regards,
Roland
Hi Patrik,
Firstable many thanks for the great effort you guys are putting into this
project.
I would like to test it, where can I find a mini-doc to make akka-cluster
and akka-remote work with Artery?
Regards,
Guido.
On Friday, June 10, 2016 at 4:46:09 PM UTC+1, Patrik Nordwall wrote:
>
> De
Patrik, sorry I wasn't clear. If my guess is valid, at the moment akka-http
is using TCP/Netty transport provided by akka-remote. As far as you are
introducing new light-speed transport for remote, what are the plans wrt
netty transport used for http? Is it going to just be kept intact? Or - I'm
I'm not sure I understand the context of the question? Are you looking for
Akka Remoting (actor messaging) over TCP or are you just curious in general
of any plans for Akka Http transport, such as HTTP/2?
fre 10 juni 2016 kl. 19:10 skrev Andrew Gaydenko :
> Patrik,
>
> In the Aeron-as-a-transport
17 matches
Mail list logo
