Deserializing resource failed for WebDev module in Debian


I have recently installed the WebDev module to try and develop an HTML based mobile app for a project in Ignition.

I have two testing environments set up, a Windows 7 gateway running Ignition 7.8.4, and a Debian gateway running Ignition 7.8.4.

My WebDev directory contains a couple of HTML pages, a jquery.js source for scripting and some python resources for server side code.

Everything is running fine on my Windows 7 gateway, but when I copy the exact same files over to my Debian gateway i get a error in the gateway console as follows:

ERROR	11:24:02 AM	Dispatch	Deserializing resource failed.
at com.inductiveautomation.webdev.gateway.handlers.PythonResourceHandler.<init>(
at com.inductiveautomation.webdev.gateway.servlets.WebDevDispatch$ProjectDispatcher$1.load(
at com.inductiveautomation.webdev.gateway.servlets.WebDevDispatch$ProjectDispatcher$1.load(
at com.inductiveautomation.webdev.gateway.servlets.WebDevDispatch$ProjectDispatcher.get(
at com.inductiveautomation.webdev.gateway.servlets.WebDevDispatch.doGet(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(
at org.eclipse.jetty.servlet.ServletHolder.handle(
at org.eclipse.jetty.servlet.ServletHandler.doHandle(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.session.SessionHandler.doHandle(
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
at org.eclipse.jetty.servlet.ServletHandler.doScope(
at org.eclipse.jetty.server.session.SessionHandler.doScope(
at org.eclipse.jetty.server.handler.ContextHandler.doScope(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.handler.HandlerList.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.server.Server.handle(
at org.eclipse.jetty.server.HttpChannel.handle(
at org.eclipse.jetty.server.HttpConnection.onFillable(
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
at org.eclipse.jetty.util.thread.QueuedThreadPool$

This occurs when i try and execute an Ajax GET method.

I have spent about a day trying to get to the bottom of it, and I am fairly sure its not an issue with my code or syntax, as the exact same resources are working in my Windows 7 gateway.

The strange thing is, I had an earlier version of the same code working on my Debian gateway. And i can’t recall any changes i could have done to affect the gateway.

I’m pretty new to WebDev stuff so any help would be much appreciated.

At first glance this looks like it has to be a bug on our side somewhere, but I’m not super familiar with the webdev codebase so I’m not certain what it is.

Is there a difference between the two gateways in staging vs published project setup or anything like that?

Hi Kevin,

No I don’t use staging/published versions. Always just push out the latest version.

I seem to get the same error when I go to Web Dev section and try “Import Text Resource”, such as a .css file.
So it seems to be an underlying issue with simply interpreting/reading the files. Not specific to my jquery.js file.

I also get a “NullPointerException” error when trying to save/publish a newly imported Web Dev resource.

The project isn’t disabled by any chance, is it?

ah… yes it was disabled… the Win7 one was not… So that has fixed the run time issue. Thanks, good catch!

There is still something funny going on when importing resources though. Still giving a deserialization error when importing text file such as a .css file. This isnt reported in the gateway console, just a popup error in the designer.

This seems to be avoided by creating a new “Text Resource” and copying in the text.