Streaming engine manager session logs me out too quickly after 4.8.5 update

Wowza Streaming Engine
1

I just updated my Wowza Streaming Engine perpetual license Windows servers from 4.8.0 to 4.8.5. Now I can connect as normal to the Wowza Streaming Engine Manager however I get logged out of my session after only 5 to 10 minutes.

How can I change auto logout time to be longer for the Streaming engine manager?

2

I don’t think it’s configurable. Sometimes I’ll click on Stream Targets, which uses an auto-refresh script, to keep the session alive.

3

To clarify, I am getting logged out of streaming engine manager server | server monitoring page. Prior to the upgrade to 8.4.5 and installing the pre-packaged OpenJDK 9.0.4 the server monitor page stayed logged in most of the day. Can this unexpectedly frequent logout be looked into by Wowza?

Thanks,
Mike

4

We have an update on this and you can configure it now, sorry for the inconvenience, we’ll get the doc updated on it.

It is configurable in conf/Manager.xml through a property. The property name is sessionTimeout, type Integer units of minutes. The default is 30 minutes. Setting the value to zero will disable session timeouts.

WMSLoggerFactory.getLogger(SessionTimeoutFilter.class).info("SesssionTimeoutFilter.init: Session timeout: "+(this.timeout <= 0?"disabled":this.timeout+" minute(s)"));
    WMSLoggerFactory.getLogger(SessionTimeoutFilter.class).info("SesssionTimeoutFilter.init: Session skipURLPatterns: "+Arrays.toString(this.skipURLPatterns));
    WMSLoggerFactory.getLogger(SessionTimeoutFilter.class).info("SesssionTimeoutFilter.init: Session redirectURL: "+this.redirectURL);

The values are logged at WSEM startup

5

If you don’t mind sharing, our engineers would like to understand the reasons for keeping WSEM open most of the day without a timeout. Monitoring? Other reason?

Appreciate the feedback @Michael_Thorpe.

6

The only manager.xml file I can find is in C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine\manager\conf\Manager.xml and it has no properties. It is the same on all of my Windows servers.

<?xml version="1.0" encoding="UTF-8"?>
7

Hi Rose, We have a popular ongoing live event now and so I need to spot check the server monitor periodically through the day and respond to any system issues like, video sources, network, or server hardware limits, etc, as quickly as possible. Its not difficult to log back in however I didn’t need to prior to the upgrade. Also I did notice that some WSEM pages don’t logout at all. I have had the application SMIL Files page open for 2 days without a logout on one of my servers. Thanks.

8

Thank you for that information and I’ll pass it on to the Engine manager today. Please let us know if the properties I shared above works or not for you.

9

The properties did not work. I updated Manager.xml and restarted both the WSE and WSEM services, the logs still show the 30 minute timeout.

screenshot.22-09-2020 11.02.15
screenshot.22-09-2020 11.02.15388×317 18.9 KB

10

I also tried this to stop the Manager killing my monitoring session, but it didnt work. Is there an alternative?

FWIW, We want to use this feature to have a permanent monitor on vhost activity.

Wowza Streaming Engine Manager Version
4.8.17+1 (build 20211216162410)

thanks

	<Properties>
			<Property>
				<Name>sessionTimeout</Name>
				<Value>0</Value>
				<Type>Integer</Type>
			<Property>
	</Properties>
11

Consider using grafana and Prometheus for professional, robust monitoring sessions.

12

Hey there @George_Bray, this was not honoring the time change in the code, you are correct and we corrected this bug in Engine version 4.8.15

  • Fixed an issue with not honoring setting the session timeout for Wowza Streaming Engine Manager to greater than 30 minutes.

https://www.wowza.com/docs/wowza-streaming-engine-4-8-15-release-notes