Server Timeout. How do I see if I can stop this from happening.
-
All of a sudden last night around 12AM, this one Modbus Connection started aborting. I have this setup on a single Modbus connector looking at 4 devices. I am getting the data from the other devices but not this one. What causes the Task Currently Running
WARN 2016-11-22 08:11:30,779 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:11:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:13:30,764 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:13:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:20:30,777 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:20:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:22:30,772 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:22:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:30:30,766 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:30:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:32:30,766 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:32:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:41:30,776 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:41:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:43:30,771 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:43:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:50:30,768 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:50:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:52:30,776 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:52:30.764 aborted because Task Currently Running
WARN 2016-11-22 08:59:30,765 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 08:59:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:01:30,776 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:01:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:08:30,767 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:08:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:10:30,779 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:10:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:17:30,777 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:17:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:19:30,772 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:19:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:26:30,767 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:26:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:28:30,765 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:28:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:35:30,770 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:35:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:37:30,764 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:37:30.764 aborted because Task Currently Running
ERROR 2016-11-22 09:42:41,356 (com.serotonin.m2m2.rt.maint.UpgradeCheck.run:54) - org.apache.http.HttpException: Invalid response code 503, reason=Service Unavailable:
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.WARN 2016-11-22 09:44:30,772 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:44:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:46:30,773 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:46:30.764 aborted because Task Currently Running
WARN 2016-11-22 09:50:30,770 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:50:30.764 aborted because Task Currently Running
INFO 2016-11-22 09:51:04,321 (com.serotonin.m2m2.rt.RuntimeManager.stopDataSource:375) - Data source 'GFSB' stopped
INFO 2016-11-22 09:51:12,774 (com.serotonin.m2m2.rt.RuntimeManager.initializeDataSource:302) - Data source 'GFSB' initialized
INFO 2016-11-22 09:51:12,774 (com.serotonin.m2m2.rt.RuntimeManager.initializeDataSource:307) - Data source 'GFSB' took 403.4739ms to start
WARN 2016-11-22 09:51:31,729 (com.serotonin.m2m2.meta.MetaPointLocatorRT.execute:264) - Context not created for meta point with xid: DP_261613 attempting to create context now.
WARN 2016-11-22 09:51:56,468 (com.serotonin.m2m2.meta.MetaPointLocatorRT.execute:264) - Context not created for meta point with xid: DP_425720 attempting to create context now.
WARN 2016-11-22 09:51:56,484 (com.serotonin.m2m2.meta.MetaPointLocatorRT.execute:264) - Context not created for meta point with xid: DP_967443 attempting to create context now.
WARN 2016-11-22 09:52:00,015 (com.serotonin.m2m2.meta.MetaPointLocatorRT.execute:264) - Context not created for meta point with xid: DP_833829 attempting to create context now.
WARN 2016-11-22 09:52:01,015 (com.serotonin.m2m2.meta.MetaPointLocatorRT.execute:264) - Context not created for meta point with xid: DP_064995 attempting to create context now.
WARN 2016-11-22 09:54:12,783 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:54:12.774 aborted because Task Currently Running
WARN 2016-11-22 09:56:12,789 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 09:56:12.774 aborted because Task Currently Running
WARN 2016-11-22 10:00:12,776 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 10:00:12.774 aborted because Task Currently Running
WARN 2016-11-22 10:03:12,781 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 10:03:12.774 aborted because Task Currently Running
WARN 2016-11-22 10:05:12,785 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 10:05:12.774 aborted because Task Currently Running
WARN 2016-11-22 10:08:12,785 (com.serotonin.m2m2.rt.dataSource.PollingDataSource$2.execute:226) - GFSB: poll scheduled at 2016/11/22 10:08:12.774 aborted because Task Currently Running -
Hi Chris,
I'm not sure I understand what you're saying about your setup. This is one Modbus data source talking to four devices, or four Modbus data sources? Serial or IP?
Regardless, the answer probably is in your timeout and retries settings. The actual maximum time waited is the number of requests, multiplied by the number of retries, multiplied by the timeout. A "poll aborted because Task Currently Running" means exactly that, the previous poll is still running. To see your poll times, you can check the "Runtime status" above the data source in question.
I believe "Latest aborted poll times" should only show up if you've already made the move to 2.8, but the "Latest poll times" should be there.