No, there is not a way.
Richard
The player is just playing out the stream buffer, I’m sure
Richard
You have to change /conf/Server.xml /JMXRemoteConfiguration /Enable to “true”, then restart Wowza
https://www.wowza.com/docs/quick-start-guides
Richard
I just set that all up and tested, vod mediacache, then shutdown the application instance with JConsole like this:
Then the player stopped right away.
Richard
Stefan,
The ApplicationInstance is the run-time, instantiated Application. Application.shutdownAppInstance(instanceName) is how to do what you want to do.
Richard
You will have to provide much more info/detail as to what you are doing and what you want to accomplish.
Richard
A live stream? What is the source? Is it a MediaCaster source, e.g. IP camera or mpeg-ts encoder? Those you can control with the MediaCaster system. If it is a Live RTMP encoder, those are hard to stop from Wowza. You can shutdown the client, but some of them will re-connect right away.
Richard
Wowza cannot control a RTMP Live encoder, except to disconnect it. You have to re-start in the encoder
Richard
FMLE keeps trying to re-connect. It’s not Wowza doing that, it’s FMLE.
Richard
If you shut down the FMLE connection’s connectection you cannot turn that back on. I’m not really sure what you are seeing in terms of reboot, but you can only disconnect a live RTMP encoder client. You cannot turn that client back on. It can re-connect, but it will have another clientID.
Richare
No, I would have told you already.
With MediaCaster streams that are pulled from a source (IP camera, mpeg-ts encoders) you have the server-side control that you describe but, not from a Live RTMP Encoder.
Richard
The screenshot shows that no applications are started. There would be an application folder that you can expand to drill-down to application instances, etc.
You can start an application by connecting to it with any type of client. For example if you try to play a stream, even one that does not exist, in any playback client, Wowza will start the application if it exists. Then you will see it in JConsole.
You can also start an application in JConsole, just below were you are in VHost > Operations > startApplicationInstance: enter an app name in the first box, and an app instance name (or blank) in the 2nd box.
Richard
Hello Richard,
If I shutdown livestream application with jconsole like described in screenshot from upper thread I have to start all streams in Stream Manager again.
Is there a way just to reload application so I have all started streams saved?
Thakns,
K
I’ve configured my EC2 instance to allow remote JConsole connection, and I can connect from my desktop Linux machine just fine. I see the WowzaMediaServerPro entry on the MBeans tab. If I wanted to restart my ccrepeater application, how would I do so using JConsole?
Perfect - exactly what I was looking for. Thanks.
Can I schedule it? I need to restart different services during a normal day but in different moments without restarting the entire wowza service.
I have installed on my server the 2.1.2 wowza version and I don’t see Wowza Media Server Pro in MBEANS menu . Is this a problem? Can I manage different applications with this version?
Thanks!
Has the behavior for Application shutdown been changed in Wowza 3?
I’m testing Wowza 3.1.0 and after shutdown of an application through JMX, I observe that ongoing VOD RTMP streams continue playing while the Application is stopped. If I start playing a new stream (e.g. same content in other player), the application is started again.
So it seems like you now have support for graceful restart of applications. Is my observation correct or do you have any other explanation to what I have observed.
I could not find anything in the release notes about this.
/Stefan
Thanks for your response.
I updated my earlier post to state that I was testing VOD and not live. I am pulling files from the file system through the Media Cache.
But I still see that after stopping the application, the player continues playing the file for at least 10 minutes without a problem, and it is pulling the content from Wowza and not from any local buffer. It seems like the stream just lives on in Wowza 3.1 although the application is dead. What am I missing?
/Stefan
