Adding custom HTTPProvider makes the VHost not starting.

Wowza Streaming Engine
1

So I had my Wowza set up in another computer running on Ubuntu. Now I want to connect my custom HTTP Provider. I edited the VHost.xml in the conf directory. But after I restart my server, the vhost won’t start automatically. Also, the ports indicated in the VHost.xml won’t bind. I’ve made sure that the xml is correct but still it won’t work. Later, I’ve reverted my the changes I made in the VHost.xml and it worked. But I tried adding again, still the vhost won’t start.

My Wowza is in its latest version.

com.wowza.wms.http.HTTPCrossdomain

*crossdomain.xml

none

com.wowza.wms.http.HTTPClientAccessPolicy

*clientaccesspolicy.xml

none

com.wowza.wms.http.HTTPProviderMediaList

*jwplayer.rss|*jwplayer.smil|*medialist.smil|*manifest-rtmp.f4m

none

com.wowza.wms.timedtext.http.HTTPProviderCaptionFile

.ttml|.srt|.scc|.vtt

none

com.wowza.wms.webapps.MyNewProvider

testprovider*

none

com.wowza.wms.http.HTTPServerVersion

*

none

Am I missing something? Thanks. :slight_smile:

2

Hello,

Do you see any indication of the issue in the logs? You can start Wowza in stand alone mode and view the output in the console [install-dir]/bin/startup.bat|startup.sh

Thank you,

Salvadore

3

Cool, thanks for the update and glad you got this sorted out.

Salvadore

4

Hello,

Do you see any indication of the issue in the logs? You can start Wowza in stand alone mode and view the output in the console [install-dir]/bin/startup.bat|startup.sh

Thank you,

Salvadore

Hey, thanks for the reply. The logs get stuck before binding the virtual ports. I don’t know why this doesn’t work while it works in my EC2. No errors.

5

Oh, I saw it. Here’s the exception:

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at com.wowza.wms.bootstrap.Bootstrap.startServer(Bootstrap.java:555)

at com.wowza.wms.bootstrap.Bootstrap.main(Bootstrap.java:67)

Caused by: java.lang.UnsupportedClassVersionError: com/wowza/wms/webapps/WinOneCaster : Unsupported major.minor version 52.0

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClass(ClassLoader.java:800)

at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)

at java.net.URLClassLoader.access$100(URLClassLoader.java:71)

at java.net.URLClassLoader$1.run(URLClassLoader.java:361)

at java.net.URLClassLoader$1.run(URLClassLoader.java:355)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:354)

at java.lang.ClassLoader.loadClass(ClassLoader.java:425)

at java.lang.ClassLoader.loadClass(ClassLoader.java:358)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:191)

at com.wowza.wms.util.VHostUtils.loadHTTPProvider(VHostUtils.java:61)

at com.wowza.wms.util.VHostUtils.loadHostPort(VHostUtils.java:609)

at com.wowza.wms.util.VHostUtils.loadHostPortList(VHostUtils.java:686)

at com.wowza.wms.util.VHostUtils.loadConfigFile(VHostUtils.java:978)

at com.wowza.wms.vhost.VHost.c(VHost.java:1185)

at com.wowza.wms.vhost.VHost.init(VHost.java:501)

at com.wowza.wms.vhost.VHostSingleton.init(VHostSingleton.java:62)

at com.wowza.wms.server.Server.startVHost(Server.java:2242)

at com.wowza.wms.server.Server.startVHosts(Server.java:2791)

at com.wowza.wms.server.Server.start(Server.java:1016)

… 6 more

6

I got it now. My EC2 and my other server have two different java versions. Thanks for helping. :slight_smile: