Control Solutions Inc.

PROBLEM
Workbench Platform Daemon session will not stay connected. Workbench running with a console (wb.exe) will show a WARNING message '[platform.daemonSession] connection failed, retrying GET...'.  There are also connect exceptions 'Read timed out'.

Workbench Console-
WARNING [14:41:45 18-Jul-19 CDT][platform.daemonSession] connection failed, retrying GET station?action=getoutput&station=demo&follow=true&updatesonly=false at localhost:3011 (500 ms timeout)
javax.baja.sys.BajaRuntimeException
at com.tridium.platDaemon.ui.BOutputPane.getInputStream(BOutputPane.java:81)
at com.tridium.platform.ui.util.BInputStreamPane.load(BInputStreamPane.java:57)
at com.tridium.platDaemon.ui.BOutputPane.loadApp(BOutputPane.java:108)
at com.tridium.platDaemon.ui.appsurrogate.BAppSurrogateView.doLoadValue(BAppSurrogateView.java:322)
at com.tridium.platDaemon.ui.appsurrogate.BStationSurrogateView.doLoadValue(BStationSurrogateView.java:158)
at javax.baja.workbench.BWbEditor.loadValue(BWbEditor.java:251)
at javax.baja.workbench.BWbEditor.loadValue(BWbEditor.java:276)
at com.tridium.platDaemon.ui.console.BApplicationDirector.loadAppSurrogate(BApplicationDirector.java:128)
at com.tridium.platDaemon.ui.console.BApplicationDirector.access$500(BApplicationDirector.java:63)
at com.tridium.platDaemon.ui.console.BApplicationDirector$AppSurrogateTableSelection.updateTable(BApplicationDirector.java:299)
at javax.baja.ui.table.TableSelection.select(TableSelection.java:77)
at javax.baja.ui.table.TableSelection.select(TableSelection.java:60)
at com.tridium.platDaemon.ui.console.BApplicationDirector.doLoadSession(BApplicationDirector.java:194)
at com.tridium.platDaemon.ui.BDaemonSessionView$ValueLoader.run(BDaemonSessionView.java:640)
Caused by: java.net.ConnectException: Read timed out
at com.tridium.platform.daemon.BDaemonSession.processException(BDaemonSession.java:782)
at com.tridium.platform.daemon.BDaemonSession.processException(BDaemonSession.java:759)
at com.tridium.platform.daemon.BDaemonSession.sendNewRequest(BDaemonSession.java:2229)
at com.tridium.platform.daemon.BDaemonSession.getConnection(BDaemonSession.java:1785)
at com.tridium.platform.daemon.BDaemonSession.getInputStream(BDaemonSession.java:1219)
at com.tridium.platform.daemon.BDaemonSession.getInputStream(BDaemonSession.java:1137)
at com.tridium.platform.daemon.BAppSurrogate.getAppOutput(BAppSurrogate.java:548)
at com.tridium.platDaemon.ui.BOutputPane.getInputStream(BOutputPane.java:72)
... 13 more

SOLUTION
The Application Director having trouble staying connected can be a session timing issue. Possibly the computer system is slow or heavily loaded. Or there is a dialup or VPN connection in use.

'niagara.daemonsession.streamtimeout' is a 'system.properties' setting used to adjust the daemon's stream timeout (in milliseconds). Increasing this value often corrects a daemon connection timeout issue.

By default the line is a remark statement (ignored), designated by a '#' sign at the head of the line. Also the default value is 500ms.
Remove the # and edit the millisecond value as needed.
#niagara.daemonsession.streamtimeout=500

To resolve a deamon session timeout issue try increasing the streamtimeout to 1000. If timeouts persist systematically increase the value in small millisecond increments until the daemon session is stable. Make sure to restart Workbench each time the value is changed and 'system.properties' is saved.

Niagara4 system.properties location - \Niagara\Niagara-4.x.x.xxx\defaults
NiagaraAX system.properties location -  \Niagara\<build version>\lib