Smarts application logs contain numerous LOGIN and LOGOUT messages similar to the following Broker log messages:
[December 31, 2066 9:49:48 AM GMT+00:00 +925ms] t@428 SM_ProtocolEngine-380 unknown Java
SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from [email protected][10.0.0.1]:53808 session 380[December 31, 2066 9:49:49 AM GMT+00:00 +484ms] t@18 HTTP #4
SYS_MSG-*-LOGIN-Login by BrokerNonsecure from [email protected][10.0.0.1]:53809 session 381[December 31, 2066 9:49:49 AM GMT+00:00 +492ms] t@16 HTTP #2
SYS_MSG-*-LOGIN-Login by BrokerNonsecure from [email protected][10.0.0.1]:53810 session 382[December 31, 2066 9:49:49 AM GMT+00:00 +499ms] t@429 SM_ProtocolEngine-381 unknown Java
SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from [email protected][10.0.0.1]:53809 session 381[December 31, 2066 9:49:49 AM GMT+00:00 +506ms] t@430 SM_ProtocolEngine-382 unknown Java
SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from [email protected][10.0.0.1]:53810 session 382[December 31, 2066 9:49:51 AM GMT+00:00 +469ms] t@16 HTTP #2
SYS_MSG-*-LOGIN-Login by BrokerNonsecure from [email protected][10.0.0.1]:53811 session 383[December 31, 2066 9:49:51 AM GMT+00:00 +747ms] t@16 HTTP #2
SYS_MSG-*-LOGIN-Login by BrokerNonsecure from [email protected][10.0.0.1]:53812 session 384[December 31, 2066 9:49:51 AM GMT+00:00 +759ms] t@432 SM_ProtocolEngine-384 unknown Java
SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from [email protected][10.0.0.1]:53812 session 384[December 31, 2066 9:49:51 AM GMT+00:00 +816ms] t@16 HTTP #2
SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@Localhost[127.0.0.1]:49743 session 385[December 31, 2066 9:49:51 AM GMT+00:00 +834ms] t@433 SM_ProtocolEngine-385 13155 ISIN-ESM-9
SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from root@Localhost[127.0.0.1]:49743 session 385[December 31, 2066 9:49:52 AM GMT+00:00 +707ms] t@16 HTTP #2
SYS_MSG-*-LOGIN-Login by BrokerNonsecure from [email protected][10.0.0.1]:53813 session 386
Smarts IP by default does not automatically suppress Login and Logout messages in a log file and must be configured to do so.
To suppress Login and Logout messages in a Smarts log file, you must add or edit the SM_NO_LOG_CLIENTS parameter and set its value to TRUE in the runcmd_env.sh file on the server where the broker resides. This disables the client logging feature subscription for broker messages. This can be done as follows: