I started a project last year on Vaadin 24.3.5
I’ve recently started working on it again and updated the pom.xml Vaadin version to 24.6.1, Now I see this server error every time i run a local build from intellij or through command line using mvnw -Dspring.profiles.active=dev
reactor.core.Exceptions$ErrorCallbackNotImplemented: java.net.UnknownHostException: Failed to resolve 'copilot.vaadin.com' [A(1), AAAA(28)] after 2 queries
Caused by: java.net.UnknownHostException: Failed to resolve 'copilot.vaadin.com' [A(1), AAAA(28)] after 2 queries
at io.netty.resolver.dns.DnsResolveContext.finishResolve(DnsResolveContext.java:1120) ~[netty-resolver-dns-4.1.105.Final.jar:4.1.105.Final]
at io.netty.resolver.dns.DnsResolveContext.tryToFinishResolve(DnsResolveContext.java:1067) ~[netty-resolver-dns-4.1.105.Final.jar:4.1.105.Final]
at io.netty.resolver.dns.DnsResolveContext.query(DnsResolveContext.java:440) ~[netty-resolver-dns-4.1.105.Final.jar:4.1.105.Final]
at io.netty.resolver.dns.DnsResolveContext.access$700(DnsResolveContext.java:68) ~[netty-resolver-dns-4.1.105.Final.jar:4.1.105.Final]
at io.netty.resolver.dns.DnsResolveContext$2.operationComplete(DnsResolveContext.java:508) ~[netty-resolver-dns-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:583) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:559) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:629) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:118) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.resolver.dns.DnsQueryContext.finishFailure(DnsQueryContext.java:373) ~[netty-resolver-dns-4.1.105.Final.jar:4.1.105.Final]
at io.netty.resolver.dns.DnsQueryContext$5.run(DnsQueryContext.java:308) ~[netty-resolver-dns-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) ~[netty-transport-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.105.Final.jar:4.1.105.Final]
at java.base/java.lang.Thread.run(Thread.java:1589) ~[na:na]
Caused by: io.netty.resolver.dns.DnsNameResolverTimeoutException: [26085: /192.168.50.1:53] DefaultDnsQuestion(copilot.vaadin.com. IN AAAA) query '26085' via UDP timed out after 5000 milliseconds (no stack trace available)
With these config lines, you’ve basically turned off Copilot (which seems to be causing the issue in your case).
Could you provide some more info, please?
What OS are you using?
Can you confirm that version 24.3.5 works fine and the DNS checking breaks for you somewhere between 24.3.5 and 24.6.1 versions? (Asking to close out other things like network, etc) (If you could retry 24.3.5 if 24.6.1 fails, it would be very helpful)
Anything else worth to mention?
I’m asking because we’re having a hard time reproducing this issue.
Also, could you update to latest 24.6 version which is Vaadin 24.6.4
What is weird that you have 4.1.105 version in the exception, but Copilot is using netty-resolver-dns 4.1.115.Final so some version, dependency mismatch is possible.
Maybe, hopefully, the latest Copilot platform (24.6.4) would solve your issue.
<vaadin.version>24.3.5</vaadin.version>
GOOD: I do not see the UnknownHostException in the server logs, I used the application to load and save rows in the database just fine. but this version does not have Copilot
<vaadin.version>24.5.0</vaadin.version>
GOOD: I do not see the UnknownHostException in the server logs, I used the application to load and save rows in the database just fine. i think this is the first version of vaadin to have copilot