8.3.3-RC1 Ghost designer sessions

The ghost designers are present here also. Gateway is setup as redundant which from old post I know is a cause. Is there a solution other then rebooting the gateway? That don’t seem like a good option for most.

They should expire eventually, but they're also not causing any significant harm (a tiny amount of memory, but no actual OS socket).
We're actively working on the underlying issue, hopefully to be resolved in 8.3.4.

2 Likes

It showed I had like 7 designer sessions open and would not let me save anything in designer Paul.

com.inductiveautomation.ignition.common.resourcecollection.ResourceCollectionNotFoundException: resource collection not found: resource collection not found: null
	at com.inductiveautomation.ignition.gateway.project.IgnitionProjectManager.lambda$getProjectProps$8(IgnitionProjectManager.java:243)
	at java.util.Optional.orElseThrow(:0)
	at com.inductiveautomation.ignition.gateway.project.IgnitionProjectManager.getProjectProps(IgnitionProjectManager.java:243)
	at com.inductiveautomation.ignition.gateway.project.ProjectsRpcImpl.canEditProject(ProjectsRpcImpl.java:560)
	at com.inductiveautomation.ignition.gateway.project.ProjectsRpcImpl.push(ProjectsRpcImpl.java:143)
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(:0)
	at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(:0)
	at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(:0)
	at java.lang.reflect.Method.invoke(:0)
	at com.inductiveautomation.ignition.gateway.rpc.RpcDelegate$DelegateRpcHandler.handle(RpcDelegate.java:275)
	at com.inductiveautomation.ignition.gateway.rpc.RpcRoutes.lambda$handle$1(RpcRoutes.java:209)
	at com.inductiveautomation.ignition.gateway.rpc.RpcRoutes.safelyHandle(RpcRoutes.java:225)
	at com.inductiveautomation.ignition.gateway.rpc.RpcRoutes.handle(RpcRoutes.java:209)
	at com.inductiveautomation.ignition.gateway.dataroutes.Route.service(Route.java:355)
	at com.inductiveautomation.ignition.gateway.dataroutes.RouteGroupImpl.service(RouteGroupImpl.java:117)
	at com.inductiveautomation.ignition.gateway.dataroutes.RouteGroupCollectionServlet.serviceInternal(RouteGroupCollectionServlet.java:152)
	at com.inductiveautomation.ignition.gateway.dataroutes.AbstractRouteGroupServlet.service(AbstractRouteGroupServlet.java:40)
	at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:614)
	at org.eclipse.jetty.ee10.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1385)
	at org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:751)
	at org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1622)
	at com.inductiveautomation.catapult.filters.GatewayFilter.doFilter(GatewayFilter.java:119)
	at jakarta.servlet.http.HttpFilter.doFilter(HttpFilter.java:97)
	at org.eclipse.jetty.ee10.servlet.FilterHolder.doFilter(FilterHolder.java:205)
	at org.eclipse.jetty.ee10.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1594)
	at org.eclipse.jetty.ee10.servlet.ServletHandler$MappedServlet.handle(ServletHandler.java:1555)
	at org.eclipse.jetty.ee10.servlet.ServletChannel.dispatch(ServletChannel.java:823)
	at org.eclipse.jetty.ee10.servlet.ServletChannel.handle(ServletChannel.java:440)
	at org.eclipse.jetty.ee10.servlet.ServletHandler.handle(ServletHandler.java:470)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:575)
	at org.eclipse.jetty.ee10.servlet.SessionHandler.handle(SessionHandler.java:717)
	at org.eclipse.jetty.server.handler.ContextHandler.handle(ContextHandler.java:1071)
	at org.eclipse.jetty.rewrite.handler.RewriteHandler$LastRuleHandler.handle(RewriteHandler.java:159)
	at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)
	at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)
	at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)
	at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)
	at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)
	at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)
	at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)
	at org.eclipse.jetty.rewrite.handler.HeaderPatternRule$1.handle(HeaderPatternRule.java:89)
	at org.eclipse.jetty.rewrite.handler.Rule$Handler.handle(Rule.java:108)
	at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:143)
	at org.eclipse.jetty.server.Handler$Sequence.handle(Handler.java:805)
	at org.eclipse.jetty.server.Handler$Sequence.handle(Handler.java:805)
	at org.eclipse.jetty.server.Server.handle(Server.java:182)
	at org.eclipse.jetty.server.internal.HttpChannelState$HandlerInvoker.run(HttpChannelState.java:677)
	at org.eclipse.jetty.server.internal.HttpConnection.onFillable(HttpConnection.java:416)
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:322)
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
	at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:480)
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:443)
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:293)
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.run(AdaptiveExecutionStrategy.java:201)
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:311)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:981)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1211)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1166)
	at java.lang.Thread.run(:0)

Ignition v8.3.3-rc1 (b2025122208)
Java: Azul Systems, Inc. 17.0.17

Well, yes, you're still subject to the underlying conditions of the bug. But you just have to relaunch the designer until the issue doesn't happen, there's no need to restart the gateway.