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 <[email protected]>:
> 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 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/channel/ChannelHandler >> at java.lang.Class.getDeclaredConstructors0(Native Method) ~[?:1.8.0_92] >> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671) >> ~[?:1.8.0_92] >> at java.lang.Class.getConstructor0(Class.java:3075) ~[?:1.8.0_92] >> at java.lang.Class.getDeclaredConstructor(Class.java:2178) ~[?:1.8.0_92] >> at >> akka.actor.ReflectiveDynamicAccess$$anonfun$createInstanceFor$2.apply(ReflectiveDynamicAccess.scala:30) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at scala.util.Try$.apply(Try.scala:192) ~[scala-library-2.11.8.jar:?] >> at >> akka.actor.ReflectiveDynamicAccess.createInstanceFor(ReflectiveDynamicAccess.scala:27) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at >> akka.actor.ReflectiveDynamicAccess$$anonfun$createInstanceFor$3.apply(ReflectiveDynamicAccess.scala:38) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at >> akka.actor.ReflectiveDynamicAccess$$anonfun$createInstanceFor$3.apply(ReflectiveDynamicAccess.scala:38) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at scala.util.Success.flatMap(Try.scala:231) ~[scala-library-2.11.8.jar:?] >> at >> akka.actor.ReflectiveDynamicAccess.createInstanceFor(ReflectiveDynamicAccess.scala:38) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at akka.remote.EndpointManager$$anonfun$9.apply(Remoting.scala:813) >> ~[akka-remote_2.11-2.4-ARTERY-M2.jar:?] >> at akka.remote.EndpointManager$$anonfun$9.apply(Remoting.scala:805) >> ~[akka-remote_2.11-2.4-ARTERY-M2.jar:?] >> at >> scala.collection.TraversableLike$WithFilter$$anonfun$map$2.apply(TraversableLike.scala:683) >> ~[scala-library-2.11.8.jar:?] >> at scala.collection.Iterator$class.foreach(Iterator.scala:893) >> ~[scala-library-2.11.8.jar:?] >> at scala.collection.AbstractIterator.foreach(Iterator.scala:1336) >> ~[scala-library-2.11.8.jar:?] >> at scala.collection.IterableLike$class.foreach(IterableLike.scala:72) >> ~[scala-library-2.11.8.jar:?] >> at scala.collection.AbstractIterable.foreach(Iterable.scala:54) >> ~[scala-library-2.11.8.jar:?] >> at >> scala.collection.TraversableLike$WithFilter.map(TraversableLike.scala:682) >> ~[scala-library-2.11.8.jar:?] >> at >> akka.remote.EndpointManager.akka$remote$EndpointManager$$listens(Remoting.scala:805) >> ~[akka-remote_2.11-2.4-ARTERY-M2.jar:?] >> at >> akka.remote.EndpointManager$$anonfun$receive$2.applyOrElse(Remoting.scala:537) >> ~[akka-remote_2.11-2.4-ARTERY-M2.jar:?] >> at akka.actor.Actor$class.aroundReceive(Actor.scala:484) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at akka.remote.EndpointManager.aroundReceive(Remoting.scala:433) >> ~[akka-remote_2.11-2.4-ARTERY-M2.jar:?] >> at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at akka.actor.ActorCell.invoke(ActorCell.scala:495) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at akka.dispatch.Mailbox.run(Mailbox.scala:224) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at akka.dispatch.Mailbox.exec(Mailbox.scala:234) >> ~[akka-actor_2.11-2.4-ARTERY-M2.jar:?] >> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) >> ~[scala-library-2.11.8.jar:?] >> at >> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) >> ~[scala-library-2.11.8.jar:?] >> at >> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) >> ~[scala-library-2.11.8.jar:?] >> at >> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) >> ~[scala-library-2.11.8.jar:?] >> Caused by: java.lang.ClassNotFoundException: >> org.jboss.netty.channel.ChannelHandler >> at java.net.URLClassLoader.findClass(URLClassLoader.java:381) >> ~[?:1.8.0_92] >> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_92] >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) >> ~[?:1.8.0_92] >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_92] >> ... 32 more >> >> >> >> On Saturday, June 11, 2016 at 2:01:05 PM UTC+1, Patrik Nordwall wrote: >>> >>> 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 questions. >>> >>> /Patrik >>> >>> lör 11 juni 2016 kl. 13:11 skrev Guido Medina <[email protected]>: >>> >>>> 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: >>>>> >>>>> Dear hakkers, >>>>> >>>>> We’re excited to announce that we have released the second development >>>>> milestone of the new Akka Remoting, which has the code named Artery. It’s >>>>> an early development preview and we encourage you to try it out and give >>>>> us >>>>> feedback, but it’s not intended for production usage yet. >>>>> >>>>> The version number is 2.4-ARTERY-M2 with same artifacts as usual. >>>>> >>>>> It is enabled with the following configuration: >>>>> >>>>> akka.remote.artery { >>>>> >>>>> enabled = on >>>>> >>>>> # The hostname or ip clients should connect to. >>>>> >>>>> hostname = localhost >>>>> >>>>> # use 0 if you want a random available port >>>>> >>>>> port = 20200 >>>>> >>>>> } >>>>> >>>>> The protocol part of the actor system address is artery (*), so you >>>>> need to change previous akka.tcp to artery in for example >>>>> configuration of cluster seed-nodes. >>>>> >>>>> A summary of what is included in M2 compared to M1 >>>>> <https://groups.google.com/d/msg/akka-user/z05q9-cEULw/qCJqqYlwAAAJ>: >>>>> >>>>> >>>>> - >>>>> >>>>> performance improvements >>>>> - >>>>> >>>>> initial flight recorder to capture low and high frequency events >>>>> in memory mapped files for debugging (also production issues) and >>>>> testing >>>>> - >>>>> >>>>> make it possible to use efficient serialization with ByteBuffers >>>>> directly >>>>> - >>>>> >>>>> various bug fixes, including issues with remote deployment >>>>> - >>>>> >>>>> test coverage by porting most of the old remoting tests >>>>> >>>>> >>>>> The full list of changes since the last milestone is available under >>>>> the 2.4-ARTERY-M2 >>>>> <https://github.com/akka/akka/issues?q=milestone%3A2.4-ARTERY-M2+is%3Aclosed> >>>>> milestone on github for your reference. >>>>> >>>>> We are using Aeron <https://github.com/real-logic/Aeron> as the >>>>> underlying transport and are implementing the layers on top using Akka >>>>> Streams. You find more details in the design document >>>>> <https://github.com/akka/akka-meta/issues/16>. >>>>> >>>>> The development branch is artery-dev >>>>> <https://github.com/akka/akka/tree/artery-dev>, in case you want to >>>>> take a look or contribute. Issues are labeled with t:remoting:artery >>>>> <https://github.com/akka/akka/issues?q=is%3Aopen+is%3Aissue+label%3At%3Aremoting%3Aartery> >>>>> . >>>>> >>>>> (*) The protocol name is not final and may change before the new >>>>> remoting infrastructure goes stable. >>>>> >>>>> -- >>>>> >>>>> Patrik Nordwall >>>>> Akka Tech Lead >>>>> Lightbend <http://www.lightbend.com/> - Reactive apps on the JVM >>>>> Twitter: @patriknw >>>>> >>>>> -- >>>> >>>>>>>>>> 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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
