Configuration headaches for a custom module

Hi all,

I'm handling a long-overdue upgrade of a Wowza Media Server Pro instance for our product to WSE. I've ported our vods3 app config over without too much trouble, but we have a recording app with a custom recording module that's giving me an enormous headache. AFAICT, the module is loaded in the server, but the application never responds to rtmp requests from our Flash client. Strangely, the client tries to connect but apparently blocks without a response to the RTMP connection... and eventually the server shows just the
disconnect in the logs. Likewise, our custom module's onAppStart logging never shows up my development instance's logs. The app does show up correctly in the WSE Manager.

I've also tried configuring ServerListenerLoadAndLockAppInstances to force the load of our application, as a means of debugging the app load itself separate from any possible application configuration/routing issues. That provided little help, except to verify that WSE would indeed complain if, for example, our module couldn't be loaded due to a configuration issue.

Our WMS Pro app configuration follows. I'm relatively new to Wowza, but AFAICT this is a fairly boring recording app that loads our custom module to do the heavy lifting. This whole thing has the smell of One Key Misconfiguration that's preventing WSE from correctly invoking our app.

2 Replies

Adding a bit more context here: the module in question has been rebuilt using the current WSE dev tools.

The big thing I'm blocked on is that I have no idea how to debug this any further. Normally, I'd turn a server up to "DEBUG ALL THE THINGS" log level and work from there, but I haven't yet found any configuration that will produce more informative logs, etc.

I rebuilt the config above using the
upgrade guide, adding the Name, AppType (LiveEdge ??), and Transcoder (required, even if empty config; app failed to start without it) elements under Application. Still no dice.

I also tried streaming a test .flv to this application via ffmpeg to see if that revealed anything, but that was of no help either.