Sparkline Chart with indirect tag history errors

Hey guys,

I upgraded my servers to 7.5.1 over the weekend and now on pages that have sparkline charts with indirect tag history I get this error everytime it refreshed the tag history data, the sparkline goes red and then it actually updated the data and looks fine until the next time it refreshes.

[quote]Message: Error running query:
TagHistory(paths=[kill floor main plc/synchronization/line -1/current difference], start=Mon Jul 23 15:07:08 EDT 2012, end=Mon Jul 23 15:22:08 EDT 2012, flags=0)@15000ms
On: Line Sync.Line Sync.Sparkline
Time: Mon Jul 23 3:22:08PM
Severity: WARN
Logger: ignition.application.binding.TagHistoryAdapter
Stack Trace: java.lang.Exception: Error running query:
TagHistory(paths=[kill floor main plc/synchronization/line -1/current difference], start=Mon Jul 23 15:07:08 EDT 2012, end=Mon Jul 23 15:22:08 EDT 2012, flags=0)@15000ms
On: Line Sync.Line Sync.Sparkline
    at com.inductiveautomation.factorypmi.application.gateway.QueryManager$
    at Source)
Caused by: com.inductiveautomation.ignition.client.gateway_interface.GatewayException: null
    at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.newGatewayException(
    at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(
    at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.sendMessage(
    at com.inductiveautomation.ignition.client.gateway_interface.GatewayInterface.runTagHistoryQuery(
    at com.inductiveautomation.factorypmi.application.gateway.GWITagHistoryProvider.query(
    at com.inductiveautomation.ignition.common.sqltags.history.cache.TagHistoryCache.query(
    at com.inductiveautomation.factorypmi.application.gateway.TagHistoryQuery.execute(
    at com.inductiveautomation.factorypmi.application.gateway.QueryManager$Query.execute(
    at com.inductiveautomation.factorypmi.application.gateway.QueryManager$Query.access$500(
    at com.inductiveautomation.factorypmi.application.gateway.QueryManager$
    … 1 more
Caused by: java.lang.NullPointerException
    at com.inductiveautomation.ignition.gateway.sqltags.history.query.loaders.DatasourceHistoryLoader.getEffectiveWindowSizeMS(
    at com.inductiveautomation.ignition.gateway.sqltags.history.query.HistoryWriter.calculateBlockSize(
    at com.inductiveautomation.ignition.gateway.sqltags.history.query.HistoryWriter.execute(
    at com.inductiveautomation.ignition.gateway.sqltags.SQLTagsManagerImpl.queryHistory(
    at com.inductiveautomation.ignition.gateway.servlets.gateway.functions.QueryTagHistory.invoke(
    at com.inductiveautomation.ignition.gateway.servlets.Gateway.doPost(
    at javax.servlet.http.HttpServlet.service(
    at javax.servlet.http.HttpServlet.service(
    at com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(
    at org.apache.catalina.core.StandardWrapperValve.invoke(
    at org.apache.catalina.core.StandardContextValve.invoke(
    at org.apache.catalina.core.StandardHostValve.invoke(
    at org.apache.catalina.valves.ErrorReportValve.invoke(
    at org.apache.catalina.core.StandardEngineValve.invoke(
    at org.apache.catalina.connector.CoyoteAdapter.service(
    at org.apache.coyote.http11.Http11Processor.process(
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(

Stack Trace: com.inductiveautomation.factorypmi.application.gateway.QueryManager$ Source)

Also, if it means anything, the sparkline charts are part of templates as well.

I doubt it has anything to do with the type of chart, but instead perhaps with the binding settings & some sort of issue with the data. In particular, take a look and see if the binding on “data” is set to a sample size of “Natural”. If so, when you look at the console in the gateway, do you see any messages like “No scan class information found for tags”?

If it’s not “natural”, let me know. Otherwise I would recommend trying either on-change or fixed. Ultimately, it’s trying to figure out what the tag’s scan class was running at, and is failing for some reason. If you want, you can call in and we can try to track down what’s really going on, but trying one of the other modes should at least work around it for now.


Well, I think the actual problem is this:

Even though it's supposed to be getting an actual number for "line -1" it's putting a -1 in there, of course there is no line -1. It does this everytime it refreshes. Instead of using the indirection it's putting -1 in for the indirect value. It was working fine before the upgrade to 7.5.1 (from 7.5.0).

Ah, ok, I’ll take a look at that scenario. However, my main suggestion still applies: this is an error that should only be able to happen if using “natural” results. If you can use a different result type, you should be able to get around it until we fix the main issue.


Will do, I’ll take a look at that tomorrow.

Also, after thinking about it the indirection is pointing to a user defined datatype and the chart is part of a template whose drop target is the user defined data type. Maybe all of that has something to do with it too. FYI.

FYI, Changing the sample size to fixed seems to have gotten rid of that error on the client.

However I’m still getting a ton of these errors in the gateway console:


It seems to be having some difficulty dealing with tags that don’t exist (the paths have -1, so I’m guessing these are happening in the designer when you don’t have a valid property there). It shouldn’t hurt anything, but I’ll take a look- it’s supposed to just return bad quality.


Looking at your latest log, I think we’ve fixed all of the actual errors. The log message about “no tag info found” is a nuisance, but technically correct, and useful for troubleshooting. However, I’ve changed that logger to only log once per minute, so it should cut down on the number of messages.


Ok, that’s fair. Thank you!