<![CDATA[Event Handler Setting Meta Point Failing]]>Mango Enterprise Core 3.3.4

We are trying to set a meta point based on an Event Trigger.

if temperature is greater than 150 on point X, set point Y to 1
if temperature is less than 120 on point X, set point Y to 2
On return to normal of point X, set point Y to 0

Here's the point event detector:

0_1524773127303_point event detector.png

Here's the meta point we are trying to change:

0_1524773150271_meta alarm point.png

Here's the event handler:

0_1524773160058_event handler.png

To test the event, I changed the limit numbers to trigger the event:

Here's email proof that the alarm triggered:

0_1524773204973_alarm email.png

The meta point was not changed:

0_1524773265519_in alarm.png

]]>https://forum.mango-os.com/topic/3443/event-handler-setting-meta-point-failingRSS for NodeThu, 14 May 2026 02:04:33 GMTThu, 26 Apr 2018 20:08:37 GMT60<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 22:10:12 GMT]]>Certainly! Sorry you were inconvenienced by the queuing issue!

Alas the documentation is scattered around the forum primarily, although the context help (blue ? next to the data source name on the edit page) is useful. Virtual points are perhaps the simplest of points. You can disable polling on the data source, and then they're just points to set values into. The data source can also poll to make the points do simple things like increment, generate random values, alternate, or whatever is sensible to the data type.

Meta points are event-driven timer-driven script bodies that are an iceberg of features with limitless use cases somewhat described here: https://github.com/infiniteautomation/ma-core-public/blob/main/Core/web/WEB-INF/dox/mangoJavaScript.htm

I have posted a great many examples of meta points and scripts around the forum.

]]>https://forum.mango-os.com/post/18256https://forum.mango-os.com/post/18256Wed, 02 May 2018 22:10:12 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 21:59:35 GMT]]>Putting return UNCHANGED worked!

Just a follow up questions so we don't have to bug you as much in the future:

Can you provide us some guidance on where to find documentation on virtual points?

How does a virtual point differ from an meta data point?

Thanks again for all of your hard work in helping us get this working.

]]>https://forum.mango-os.com/post/18255https://forum.mango-os.com/post/18255Wed, 02 May 2018 21:59:35 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 21:54:20 GMT]]>Ah, screenshots. You probably want to change that script body to return UNCHANGED; or use a virtual point instead. Currently I would expect it gets a value of 0 (casting a null return value to a numeric) every time that context point updates.

]]>https://forum.mango-os.com/post/18254https://forum.mango-os.com/post/18254Wed, 02 May 2018 21:54:20 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 21:49:55 GMT]]>While I have contemplated making meta points that don't have execution conditions (would be useful to hit 'refresh point value' on, as that can also trigger the meta script), I haven't yet. So, either your meta point has a point in its context that has 'update context' checked and that triggers the meta points execution, or you have the update event set to something other than context update and it's executing at some specified rate or cron.

]]>https://forum.mango-os.com/post/18253https://forum.mango-os.com/post/18253Wed, 02 May 2018 21:49:55 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 21:49:52 GMT]]>@phildunlap said in Event Handler Setting Meta Point Failing:

We can see in the annotation that it wasn't the inactive event doing it. So, what could trigger that meta point to recompute itself? Is 0 the value it would get if it executed?

Hi,

Sorry -- unsure what you mean by if "...it was executed"

Nothing else changes that point except the event handler.

Here's a screeenshot of the metapoint details:
0_1525297871676_a1bb47c4-5c32-4c95-a108-037c02261362-image.png

]]>https://forum.mango-os.com/post/18252https://forum.mango-os.com/post/18252Wed, 02 May 2018 21:49:52 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 21:39:57 GMT]]>We can see in the annotation that it wasn't the inactive event doing it. So, what could trigger that meta point to recompute itself? Is 0 the value it would get if it executed?

]]>https://forum.mango-os.com/post/18251https://forum.mango-os.com/post/18251Wed, 02 May 2018 21:39:57 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 21:31:17 GMT]]>Thanks @phildunlap

Upgrade went smooth and what we were trying to do kind of worked, but still not working as expected.

I am now able to create an event handler to set a point to a static value if an event is triggered -- and that works just fine. However, the point we are setting almost instantly goes back to 0, despite the event still being active.

Screenshots:
Event Detector:
0_1525296572818_faf61fec-106c-4dfa-bc65-4756dd4d4552-image.png

Proof that the event is still active:
0_1525296668868_9b5b1593-820d-468e-b20c-19913201c981-image.png

Event Handler:
0_1525296709154_593ac7f2-b384-42b9-8578-9d1c60d56068-image.png

History of the point we are trying to set, note it goes active, and then 8 seconds later inactive for some reason (even though we never came close to hiting the reset limit of <60)
0_1525296761496_d8342dc6-086d-45d9-9ff2-dd591c51bb4d-image.png

]]>https://forum.mango-os.com/post/18250https://forum.mango-os.com/post/18250Wed, 02 May 2018 21:31:17 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 20:43:31 GMT]]>3.4.1 is released.

]]>https://forum.mango-os.com/post/18248https://forum.mango-os.com/post/18248Wed, 02 May 2018 20:43:31 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 16:49:13 GMT]]>@phildunlap
Thanks!

Thanks for the quick fix as well.

]]>https://forum.mango-os.com/post/18244https://forum.mango-os.com/post/18244Wed, 02 May 2018 16:49:13 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 16:43:31 GMT]]>We'll be releasing 3.4.1 today.

]]>https://forum.mango-os.com/post/18243https://forum.mango-os.com/post/18243Wed, 02 May 2018 16:43:31 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 16:29:30 GMT]]>@phildunlap said in Event Handler Setting Meta Point Failing:

Whoa, that's not good. I have committed a fix and we'll be releasing core 3.4.1 to address this. Thanks for bringing it to our attention.

Glad to hear it was discovered early :)

Any workarounds until 3.4.1?

]]>https://forum.mango-os.com/post/18241https://forum.mango-os.com/post/18241Wed, 02 May 2018 16:29:30 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 16:27:06 GMT]]>Whoa, that's not good. I have committed a fix and we'll be releasing core 3.4.1 to address this. Thanks for bringing it to our attention.

]]>https://forum.mango-os.com/post/18240https://forum.mango-os.com/post/18240Wed, 02 May 2018 16:27:06 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 14:55:15 GMT]]>@phildunlap said in Event Handler Setting Meta Point Failing:

Post the error in its entirety from your Mango/logs/ma.log file.

ERROR 2018-05-02T09:55:50,957 (com.serotonin.m2m2.web.dwr.util.ExceptionDetectionFilter.doFilter:38) - DWR invocation exception 
org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [INSERT INTO eventHandlersMapping (eventHandlerId, eventTypeName, eventTypeRef1, eventTypeRef2) values (?, ?, ?, ?) ON DUPLICATE KEY IGNORE]; nested exception is com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IGNORE' at line 1
	at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:231) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:73) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:655) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:876) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:937) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at com.serotonin.db.spring.ExtendedJdbcTemplate.update(ExtendedJdbcTemplate.java:83) ~[mango-3.4.0.jar:?]
	at com.serotonin.m2m2.db.dao.EventHandlerDao.addEventHandlerMappingIfMissing(EventHandlerDao.java:241) ~[mango-3.4.0.jar:?]
	at com.serotonin.m2m2.db.dao.EventHandlerDao.saveRelationalData(EventHandlerDao.java:210) ~[mango-3.4.0.jar:?]
	at com.serotonin.m2m2.db.dao.EventHandlerDao.saveRelationalData(EventHandlerDao.java:37) ~[mango-3.4.0.jar:?]
	at com.serotonin.m2m2.db.dao.AbstractBasicDao.lambda$saveFull$0(AbstractBasicDao.java:552) ~[mango-3.4.0.jar:?]
	at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:133) ~[spring-tx-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at com.serotonin.m2m2.db.dao.AbstractBasicDao.saveFull(AbstractBasicDao.java:548) ~[mango-3.4.0.jar:?]
	at com.serotonin.m2m2.db.dao.AbstractBasicDao.saveFull(AbstractBasicDao.java:539) ~[mango-3.4.0.jar:?]
	at com.serotonin.m2m2.web.dwr.EventHandlersDwr.save(EventHandlersDwr.java:333) ~[mango-3.4.0.jar:?]
	at com.serotonin.m2m2.web.dwr.EventHandlersDwr.saveSetPointEventHandler(EventHandlersDwr.java:272) ~[mango-3.4.0.jar:?]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]
	at org.directwebremoting.impl.ExecuteAjaxFilter.doFilter(ExecuteAjaxFilter.java:34) ~[dwr-2.0.11.jar:?]
	at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) ~[dwr-2.0.11.jar:?]
	at com.serotonin.m2m2.web.dwr.util.TranslationsFilter.doFilter(TranslationsFilter.java:37) ~[mango-3.4.0.jar:?]
	at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) ~[dwr-2.0.11.jar:?]
	at com.serotonin.m2m2.web.dwr.util.ExceptionDetectionFilter.doFilter(ExceptionDetectionFilter.java:26) [mango-3.4.0.jar:?]
	at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) [dwr-2.0.11.jar:?]
	at com.serotonin.m2m2.web.dwr.util.DwrPermissionFilter.doFilter(DwrPermissionFilter.java:46) [mango-3.4.0.jar:?]
	at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) [dwr-2.0.11.jar:?]
	at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:431) [dwr-2.0.11.jar:?]
	at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:283) [dwr-2.0.11.jar:?]
	at org.directwebremoting.servlet.PlainCallHandler.handle(PlainCallHandler.java:52) [dwr-2.0.11.jar:?]
	at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:101) [dwr-2.0.11.jar:?]
	at org.directwebremoting.servlet.DwrServlet.doPost(DwrServlet.java:146) [dwr-2.0.11.jar:?]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [javax.servlet-api-3.1.0.jar:3.1.0]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [javax.servlet-api-3.1.0.jar:3.1.0]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [jetty-servlet-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772) [jetty-servlet-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.springframework.web.filter.ShallowEtagHeaderFilter.doFilterInternal(ShallowEtagHeaderFilter.java:110) [spring-web-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at com.serotonin.m2m2.web.filter.MangoShallowEtagHeaderFilter.doFilterInternal(MangoShallowEtagHeaderFilter.java:90) [mango-3.4.0.jar:?]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759) [jetty-servlet-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at com.serotonin.m2m2.web.mvc.spring.security.PermissionExceptionFilter.doFilter(PermissionExceptionFilter.java:32) [mango-3.4.0.jar:?]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:111) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:170) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.session.ConcurrentSessionFilter.doFilter(ConcurrentSessionFilter.java:155) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:200) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:116) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.csrf.CsrfFilter.doFilterInternal(CsrfFilter.java:100) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:66) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:105) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:56) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) [spring-web-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:214) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177) [spring-security-web-4.2.5.RELEASE.jar:4.2.5.RELEASE]
	at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:347) [spring-web-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:263) [spring-web-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1751) [jetty-servlet-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582) [jetty-servlet-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [jetty-security-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [jetty-servlet-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:493) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.Server.handle(Server.java:539) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [jetty-server-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [jetty-io-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [jetty-io-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [jetty-io-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [jetty-util-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [jetty-util-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [jetty-util-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [jetty-util-9.3.23.v20180228.jar:9.3.23.v20180228]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [jetty-util-9.3.23.v20180228.jar:9.3.23.v20180228]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_162]
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IGNORE' at line 1
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_162]
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_162]
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_162]
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_162]
	at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.Util.getInstance(Util.java:386) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4190) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4122) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2818) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2157) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2460) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2377) ~[mysql-connector-java-5.1.26.jar:?]
	at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2361) ~[mysql-connector-java-5.1.26.jar:?]
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) ~[commons-dbcp-1.4.jar:1.4]
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) ~[commons-dbcp-1.4.jar:1.4]
	at org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(JdbcTemplate.java:883) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.jdbc.core.JdbcTemplate$2.doInPreparedStatement(JdbcTemplate.java:876) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:639) ~[spring-jdbc-4.3.16.RELEASE.jar:4.3.16.RELEASE]
	... 99 more
]]>https://forum.mango-os.com/post/18238https://forum.mango-os.com/post/18238Wed, 02 May 2018 14:55:15 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 14:50:41 GMT]]>Post the error in its entirety from your Mango/logs/ma.log file.

]]>https://forum.mango-os.com/post/18237https://forum.mango-os.com/post/18237Wed, 02 May 2018 14:50:41 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Wed, 02 May 2018 00:42:43 GMT]]>Hi @phildunlap ,

Still no luck. We upgraded to 3.4 today and now we're getting this error when trying to create an event handler to set a point:

0_1525221803535_1bd28374-48e9-4473-9eee-a44c59bbdaea-image.png

For reference, here is the event handler we are trying to create:
0_1525221835407_44fd7dda-dcf0-4fb1-b275-4867d0c2a2f6-image.png

]]>https://forum.mango-os.com/post/18231https://forum.mango-os.com/post/18231Wed, 02 May 2018 00:42:43 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Fri, 27 Apr 2018 16:36:34 GMT]]>Sounds good -- we will wait for 3.4 to be officially released and then upgrade and report back.

Thank you again for all of your help!

]]>https://forum.mango-os.com/post/18194https://forum.mango-os.com/post/18194Fri, 27 Apr 2018 16:36:34 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Fri, 27 Apr 2018 16:35:23 GMT]]>The second image you provided, of the /internal/queueStats.shtm page, makes me certain it is the first issue I referred to. If you update to 3.4 I would expect that issue to go away. If you restart I would expect it to be temporarily relieved.

]]>https://forum.mango-os.com/post/18193https://forum.mango-os.com/post/18193Fri, 27 Apr 2018 16:35:23 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Fri, 27 Apr 2018 16:20:11 GMT]]>Update:

I tried 'multistate' instead of numeric, got this error:

0_1524845951899_9c8ca30b-dbf8-48fc-bb81-63d26126e3bd-image.png

Here are the event handler settings:

0_1524846083436_aef62f36-381e-4ede-b60a-936335f6c050-image.png

]]>https://forum.mango-os.com/post/18191https://forum.mango-os.com/post/18191Fri, 27 Apr 2018 16:20:11 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Fri, 27 Apr 2018 16:06:13 GMT]]>Hey Phil,

Here's some info:

Here is the accurate screenshot of our event handler:

0_1524844902140_4f84d718-855c-4d0b-85c2-42c9236b273f-image.png

Here is the watchlist showing the event is active, but the meta point isn't getting set:

0_1524844950951_94edf67a-e96a-423d-bdcc-f42da0b57bb6-image.png

Here is the /internal/queueStats.shtm page

0_1524844999508_87f0fda9-f800-4fd1-bce1-c92f61e6f4bc-image.png

Is it possible we did not configure the metapoint correctly when we created it?
We weren't sure if multistate was the right option, or what we should put in 'script'
Here are the metapoint settings:

0_1524845233222_78bab6e2-62b2-4724-8297-f7151298c3a1-image.png

]]>https://forum.mango-os.com/post/18190https://forum.mango-os.com/post/18190Fri, 27 Apr 2018 16:06:13 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Fri, 27 Apr 2018 15:43:11 GMT]]>There are two issues that were handled recently that come to mind. If you go to the /internal/queueStats.shtm page do you see a large number of medium priority items queuing up, perhaps never decreasing?

That you say it tripped the email but didn't set the point is interesting. I would have expected you to get a log message but this issue could be related: https://github.com/infiniteautomation/ma-core-public/issues/1235

Both of those should go away in 3.4, which is beta released currently (pick your release channel in the system settings) and will probably be fully released next week.

Does the behavior persist a restart? I am fairly confident in the event handler being able to set a meta point to a static value.

]]>https://forum.mango-os.com/post/18188https://forum.mango-os.com/post/18188Fri, 27 Apr 2018 15:43:11 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Fri, 27 Apr 2018 14:10:58 GMT]]>Hi Phil,

As Ronak said, the screenshots are a bit deceptive. What we did to test the event is to reduce the event detector threshold to 130, then raise it again.

]]>https://forum.mango-os.com/post/18182https://forum.mango-os.com/post/18182Fri, 27 Apr 2018 14:10:58 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Fri, 27 Apr 2018 02:05:53 GMT]]>Hi @phildunlap ,

I can chime in a little as Mihai is gone for the day.

We actually do want it to reset, what we were thinking we'd do for low limit is just setup another event detector, so we'd have:

Event Detector 1: If boiler temperature is greater than 160, set point Y to 2, when boiler temperature returns to less than 160, set point Y to 0 (I know the screenshot does not reflect this)

Event Detector 2: If boiler temp is less than 120, set point Y to 1, when boiler temp returns to greater than 120, set point Y to 0. (I know the screenshot does not reflect this)

I hope that is more clear. The screenshots were just some random numbers we had thrown in. It doesn't work even if there are more accurate numbers

As far as the 190 != 150, we actually had it set to 150 initially, and then increased it (to cancel the event) prior to taking the screenshot -- so it was at one point 150, which tripped the email, but it did not set the point. The numbers are just for testing purposes, we wanted some numbers that would for sure trip (150) and some that would never trip (190)

Thanks!

]]>https://forum.mango-os.com/post/18177https://forum.mango-os.com/post/18177Fri, 27 Apr 2018 02:05:53 GMT<![CDATA[Reply to Event Handler Setting Meta Point Failing on Thu, 26 Apr 2018 20:23:16 GMT]]>Hi Mihai,

Hmm. You would have gotten an event if the set point handler had run and had an issue.

As an aside, your event detector isn't going to do what you want. A reset limit means that the event stays active until the value gets on the appropriate side of the reset limit. So, you detector means "Raise the alarm if the value exceeds 190 for two seconds and leave it active until the value falls below 120." So we've got some issues. For one, 190 != 150. Secondly, the reset limit is not the same as a low limit detector to handle the logic of setting Y to 2.

From the images, I would think the high limit being 190 is why the image of the watchlist values doesn't have the target point getting the value 2.

]]>https://forum.mango-os.com/post/18174https://forum.mango-os.com/post/18174Thu, 26 Apr 2018 20:23:16 GMT