Netxms 2.2.15 WebUI - The server session has timed out

Started by wetfish, July 03, 2019, 12:37:03 PM

Previous topic - Next topic

wetfish

Hi,
Can someone please help me? I have a windows 2016 server running mySQL and NetXMS 2.2.15. I installed the WebUI feature as well.

After approx 15 - 20 hours, I am getting an error on the Windows client monitoring system stating that the Server Session has timed out. I have to reboot the netxms server to be able to run the web interface on the windows client again. Basically, I have a windows 10 machine that continuously displays the NetXMS webpage with all the alarms.

I've tried creating a file called nxmc.properties in the path "C:\NetXMS\WebUI\nxmc\lib" with the following content an played around with the sessionTimout but to no avail:

#
# This properties file contains configuration for NetXMS WebUI application
# Rename nxmc.properties.sample to nxmc.properties after installation.
#

# Name: server
# Description: Host name or IP address of NetXMS server.
server=192.168.0.4

# Name: sessionTimeout
# Description: Client session inactivity timeout in seconds.
sessionTimeout=300

# Name: enableAdvancedSettings
# Description: Enable (true) or disable (false) access to "Settings" button on login page.
enableAdvancedSettings=false

# Name: loginFormImage
# Description: Custom image to be displayed in login form instead of NetXMS logo.
#              Image file must be located within application server's class path
#              and file name must be given relative to class path root with
#              leading slash.
#loginFormImage = /custom_logo.jpg

Is there a way I can fix this problem once and for all please?

Any help is appreciated.

Thanks a lot in advance

paul

Similar setup - no problem here though - one huge difference.

The console does not time out.

We went the console path instead of WebUI as it required no install, we have created Object Tools(only works on Consoles), and it was one less thing I needed to worry about compared to my four browsers I currently have, depending on what program is picky about what browser.

Does not solve your web problem but it does provide a workaround - once and for all :)