Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatibility with DotNetty 0.4.7 #3409

Closed
vasily-kirichenko opened this issue Apr 20, 2018 · 4 comments · Fixed by #3410
Closed

Incompatibility with DotNetty 0.4.7 #3409

vasily-kirichenko opened this issue Apr 20, 2018 · 4 comments · Fixed by #3410

Comments

@vasily-kirichenko
Copy link
Contributor

13:31:11 FATAL [DomainUnhandled, 1] Domain unhandled exception of type AggregateException occured (System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.MissingMethodException: Method not found: 'Void DotNetty.Buffers.UnpooledByteBufferAllocator..ctor()'.
   at Akka.Remote.Transport.DotNetty.DotNettyTransport.ServerFactory()
   at Akka.Remote.Transport.DotNetty.DotNettyTransport.<NewServer>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Akka.Remote.Transport.DotNetty.DotNettyTransport.<Listen>d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Akka.Remote.Transport.DotNetty.DotNettyTransport.<Listen>d__21.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Akka.Remote.Transport.AbstractTransportAdapter.<>c__DisplayClass11_0.<<Listen>b__0>d.MoveNext()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Akka.Remote.EndpointManager.<>c__DisplayClass48_1.<get_Listens>b__4(Task`1 result)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Akka.Remote.EndpointManager.<>c.<get_Listens>b__48_5(Task`1 transportResults)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait(TimeSpan timeout)
   at Akka.Remote.Remoting.Start()
   at Akka.Remote.RemoteActorRefProvider.Init(ActorSystemImpl system)
   at Akka.Cluster.ClusterActorRefProvider.Init(ActorSystemImpl system)
   at Akka.Actor.Internal.ActorSystemImpl.Start()
   at Akka.Actor.ActorSystem.Create(String name, Config config)
@vasily-kirichenko
Copy link
Contributor Author

This is having Akka 1.3.6 package. It claims it's compatible with DotNetty 0.4.6+, but it's clearly not the case. It should depends on 0.4.6, strictly.

@vasily-kirichenko
Copy link
Contributor Author

Yes, pinning DotNetty to 0.4.6 has solved the problem.
I think it's a major bug and it should be fixed ASAP.

@vasily-kirichenko
Copy link
Contributor Author

image

@vasily-kirichenko
Copy link
Contributor Author

Fixed via #3410

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant