Upgrade to 2.6.0 Gives Copilot Error on Logout

[chicojeff (Jeff Meyers)]

Testing after upgrade from 2.5.2 to 2.6.0 and the only problem I have come across is when I login, open a view, then log out an error is logged regarding Copilot. I suspect this may be development mode only.

The vaadin copilot option is OFF:

Here is the log. The first 3 lines are my app recording the log in and out:

2025-07-06T15:19:01.278-04:00  INFO 23084 --- [cTaskExecutor-7] o.a.m.service.AccessLoggingService       : User jeff successfully logged in from: 0:0:0:0:0:0:0:1 with session: DF9333F246C02CAEBF2A5D74BC963848
2025-07-06T15:19:05.643-04:00  INFO 23084 --- [cTaskExecutor-8] o.a.m.service.AccessLoggingService       : User logged out: jeff with session: DF9333F246C02CAEBF2A5D74BC963848
2025-07-06T15:19:05.647-04:00  INFO 23084 --- [cTaskExecutor-8] o.a.m.service.AccessLoggingService       : Deleted 0 rows of old access logs in 3ms
2025-07-06T15:19:05.816-04:00  WARN 23084 --- [cat-handler-511] o.a.websocket.DefaultWebSocketProcessor  : Failed invoking AtmosphereFramework.doCometSupport()

java.lang.NullPointerException: Cannot invoke "com.vaadin.copilot.CopilotSession.handleMessage(String, elemental.json.JsonObject, com.vaadin.base.devserver.DevToolsInterface)" because the return value of "java.util.Map.get(Object)" is null
	at com.vaadin.copilot.Copilot.handleMessage(Copilot.java:65) ~[copilot-24.7.3.jar:na]
	at com.vaadin.base.devserver.DebugWindowConnection.onMessage(DebugWindowConnection.java:336) ~[vaadin-dev-server-24.7.5.jar:na]
	at com.vaadin.flow.server.communication.PushHandler.handleDebugWindowMessage(PushHandler.java:669) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushHandler.callWithServiceAndSession(PushHandler.java:237) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushHandler.onMessage(PushHandler.java:645) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushAtmosphereHandler.onMessage(PushAtmosphereHandler.java:90) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushAtmosphereHandler.onRequest(PushAtmosphereHandler.java:79) ~[flow-server-24.7.5.jar:24.7.5]
	at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:217) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:103) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:67) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:2284) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.dispatch(DefaultWebSocketProcessor.java:574) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.lambda$dispatch$2(DefaultWebSocketProcessor.java:326) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.util.VoidExecutorService.execute(VoidExecutorService.java:101) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.dispatch(DefaultWebSocketProcessor.java:323) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.invokeWebSocketProtocol(DefaultWebSocketProcessor.java:428) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.container.JSR356Endpoint.lambda$onOpen$2(JSR356Endpoint.java:261) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.apache.tomcat.websocket.WsFrameBase.sendMessageText(WsFrameBase.java:389) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.sendMessageText(WsFrameServer.java:130) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.WsFrameBase.processDataText(WsFrameBase.java:483) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:283) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.WsFrameBase.processInputBuffer(WsFrameBase.java:129) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:85) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:184) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:164) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:152) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:60) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:57) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:903) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1740) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at java.base/java.lang.VirtualThread.run(VirtualThread.java:329) ~[na:na]

2025-07-06T15:19:05.817-04:00  WARN 23084 --- [cat-handler-511] o.a.w.protocol.SimpleHttpProtocol        : java.lang.NullPointerException: Cannot invoke "com.vaadin.copilot.CopilotSession.handleMessage(String, elemental.json.JsonObject, com.vaadin.base.devserver.DevToolsInterface)" because the return value of "java.util.Map.get(Object)" is null. Unable to deliver the websocket messages to installed component. Status 500 Message Server Error
2025-07-06T15:19:05.818-04:00  WARN 23084 --- [cat-handler-511] o.a.websocket.DefaultWebSocketProcessor  : Failed invoking AtmosphereFramework.doCometSupport()

java.lang.NullPointerException: Cannot invoke "com.vaadin.copilot.CopilotSession.handleMessage(String, elemental.json.JsonObject, com.vaadin.base.devserver.DevToolsInterface)" because the return value of "java.util.Map.get(Object)" is null
	at com.vaadin.copilot.Copilot.handleMessage(Copilot.java:65) ~[copilot-24.7.3.jar:na]
	at com.vaadin.base.devserver.DebugWindowConnection.onMessage(DebugWindowConnection.java:336) ~[vaadin-dev-server-24.7.5.jar:na]
	at com.vaadin.flow.server.communication.PushHandler.handleDebugWindowMessage(PushHandler.java:669) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushHandler.callWithServiceAndSession(PushHandler.java:237) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushHandler.onMessage(PushHandler.java:645) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushAtmosphereHandler.onMessage(PushAtmosphereHandler.java:90) ~[flow-server-24.7.5.jar:24.7.5]
	at com.vaadin.flow.server.communication.PushAtmosphereHandler.onRequest(PushAtmosphereHandler.java:79) ~[flow-server-24.7.5.jar:24.7.5]
	at org.atmosphere.cpr.AsynchronousProcessor.action(AsynchronousProcessor.java:217) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.cpr.AsynchronousProcessor.suspended(AsynchronousProcessor.java:103) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.container.Servlet30CometSupport.service(Servlet30CometSupport.java:67) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:2284) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.dispatch(DefaultWebSocketProcessor.java:574) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.lambda$dispatch$2(DefaultWebSocketProcessor.java:326) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.util.VoidExecutorService.execute(VoidExecutorService.java:101) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.dispatch(DefaultWebSocketProcessor.java:323) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.websocket.DefaultWebSocketProcessor.invokeWebSocketProtocol(DefaultWebSocketProcessor.java:428) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.atmosphere.container.JSR356Endpoint.lambda$onOpen$2(JSR356Endpoint.java:261) ~[atmosphere-runtime-3.0.5.slf4jvaadin1.jar:3.0.5.slf4jvaadin1]
	at org.apache.tomcat.websocket.WsFrameBase.sendMessageText(WsFrameBase.java:389) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.sendMessageText(WsFrameServer.java:130) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.WsFrameBase.processDataText(WsFrameBase.java:483) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:283) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.WsFrameBase.processInputBuffer(WsFrameBase.java:129) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:85) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:184) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:164) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:152) ~[tomcat-embed-websocket-10.1.41.jar:10.1.41]
	at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:60) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:57) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:903) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1740) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-embed-core-10.1.41.jar:10.1.41]
	at java.base/java.lang.VirtualThread.run(VirtualThread.java:329) ~[na:na]

2025-07-06T15:19:05.819-04:00  WARN 23084 --- [cat-handler-511] o.a.w.protocol.SimpleHttpProtocol        : java.lang.NullPointerException: Cannot invoke "com.vaadin.copilot.CopilotSession.handleMessage(String, elemental.json.JsonObject, com.vaadin.base.devserver.DevToolsInterface)" because the return value of "java.util.Map.get(Object)" is null. Unable to deliver the websocket messages to installed component. Status 500 Message Server Error

[mbucan (Mladen Bucan)]

Maybe this can help. I deactivated Copilot some time ago.

How to permanently disable Vaadin Copilot

Hello, I find this Vaadin Copilot very irritating, it activates when I press shift, it is supposed activate when I hold shift or press twice. The activation treshold is very short while holding shift. Happens when I want to scroll a BPM diagram, or when I want to enter capital letter … and then I need to turn it off. [image] Also, I can’t find much information about that on their page Vaadin Copilot | Tools | Vaadin Docs and also I’m interested to learn what this copilot has access to, sin…

Kind regards,
Mladen