system.alarm.queryJournal return error in 7.9.2

Since we upgrade to 7.9.2, we have an error when we use system.alarm.queryJournal in the vision client.
I think this issue was not in previous release :disappointed:

(IA support [#49100]: system.alarm.queryJournal error with source filter)

It seems to occur with the source filter or the displaypath filter.
Something go wrong with the queryJournal executed in gateway.

Vision client script :

results = system.alarm.queryJournal(includeData=True, journalName=filtreJournalName, startDate=filtreStartDate, endDate=filtreEndDate, state=filtreState, priority=filtrePriority,source=filtreSource, includeSystem=True,provider=filtreProvider)

Vision client log :

filtreJournalName=alarme_long
filtreStartDate=Mon May 08 00:00:00 CEST 2017
filtreEndDate=Tue May 09 23:59:59 CEST 2017
filtreState=['ClearUnacked', 'ClearAcked', 'ActiveUnacked', 'ActiveAcked']
filtrePriority=['Low', 'Medium', 'High', 'Critical']
filtreSource=['*TMA/*']
filtreProvider= ['L2_NORD']
13:36:21.961 [Thread-184] WARN com.inductiveautomation.factorypmi.application.script.builtin.WindowUtilities - Erreur interrogation historiques !
13:36:21.961 [Thread-184] ERROR RL2_LOG.RL2_ClientIHM - Fct: 'longProcessQueryJournal'   Contexte: Type='<type 'com.inductiveautomation.ignition.client.gateway_interface.GatewayException'>' Err='com.inductiveautomation.ignition.client.gateway_interface.GatewayException: java.util.UnknownFormatConversionException: Conversion = ','' Stack=Traceback (most recent call last):     File "<event:actionPerformed>", line 87, in longProcessQueryJournal   GatewayException: com.inductiveautomation.ignition.client.gateway_interface.GatewayException: java.util.UnknownFormatConversionException: Conversion = ','   

Gateway log :

Logger	Time	Message
Query	09May2017 13:30:04	(id=ECF92BDC) Error executing query.
java.util.UnknownFormatConversionException: Conversion = ','

at java.util.Formatter.checkText(Unknown Source)

at java.util.Formatter.parse(Unknown Source)

at java.util.Formatter.format(Unknown Source)

at java.util.Formatter.format(Unknown Source)

at com.inductiveautomation.ignition.common.util.LoggerEx.createMessage(LoggerEx.java:200)

at com.inductiveautomation.ignition.common.util.LoggerEx.tracef(LoggerEx.java:236)

at com.inductiveautomation.ignition.common.util.LoggerEx.trace(LoggerEx.java:476)

at com.inductiveautomation.ignition.gateway.alarming.journal.JournalQuery.execute(JournalQuery.java:146)

at com.inductiveautomation.ignition.gateway.alarming.journal.AlarmJournal.query(AlarmJournal.java:212)

at com.inductiveautomation.ignition.gateway.alarming.journal.AlarmJournalManager.query(AlarmJournalManager.java:184)

at com.inductiveautomation.ignition.gateway.alarming.AlarmManagerImpl.queryJournal(AlarmManagerImpl.java:366)

at com.inductiveautomation.ignition.gateway.servlets.gateway.functions.Alarming.queryJournal(Alarming.java:62)

at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.inductiveautomation.ignition.gateway.servlets.gateway.AbstractGatewayFunction.invoke(AbstractGatewayFunction.java:209)

at com.inductiveautomation.ignition.gateway.servlets.Gateway.doPost(Gateway.java:391)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)

at com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(MapServlet.java:85)

at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837)

at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)

at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)

at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)

at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)

at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)

at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)

at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)

at org.eclipse.jetty.server.Server.handle(Server.java:518)

at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)

at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)

at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)

at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)

at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)

at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)

at java.lang.Thread.run(Unknown Source)


Query	09May2017 13:30:04	(id=ECF92BDC) Starting query for datasource 'histo_long' with filter: (_state_:[[Cleared, Unacknowledged, Cleared, Acknowledged, Active, Unacknowledged, Active, Acknowledged]] , _provider_:[[L2_NORD]] , _prio_:[[Low, Medium, High, Critical]] , _eventtime_:between Mon May 08 00:00:00 CEST 2017 and Tue May 09 23:59:59 CEST 2017, inclusive , _path_:matches_any [*TMA/*] ,)

It seems that the error occur if the alarm.Journal.Query and alarm.Journal log level are set to TRACE !

Yes, it’s a trace logging statement that’s found on those lines. The odd thing is that the code on those lines is pretty much unchanged since 2012.

I don’t see anything unusual in the code, so I’m not sure why it’s throwing the error it is. The only thing I can think of that might be different in our setups would be the locale – we’ll need to check into it for sure.

Yes not sure the issue is related to 7.9.2. When the log level is INFO, there is no error in gateway log and the system.alarm.queryJournal return the results.
With a log level to TRACE, we have the exception in gateway and vision client and no data are returned.
Error must be inside the log ? Message : java.util.UnknownFormatConversionException: Conversion = ‘,’
logs end with … , path:matches_any [TMA/] ,)