NetConnection.Connect.Rejected
I've got a (more-or-less) working application which has suddenly stopped working. My dev computer (which is also running WMS) turned off on me when the power went out, and when it started back up, the application is suddenly uable to connect to WMS, even though the code hasn't changed, and WMS is up and (apparently) running. The NetStatusEvent that is being returned is "NetConnection.Connect.Rejected".
The Windows Service applet shows Wowza running. I can telnet to port 1935. When I launch WMS from the "startup.bat", it seems to start successfully, and doesn't register any error messages, i.e.:
Configure logging: file:///C:/Program Files/Wowza Media Systems/Wowza Media Serv
er Pro 1.7.0/conf/log4j.properties
INFO server server-start Wowza Media Server Pro10 1.7.0 build11414 -
INFO server comment - Serial number: XXXXX-XXXXX-XXXXX-XXXXX-CUGNB
INFO server comment - Maximum connections: 10
INFO server comment - Hardware Available Processors: 4
INFO server comment - Hardware Physical Memory: 1119MB/2047MB
INFO server comment - Hardware Swap Space: 3723MB/4095MB
INFO server comment - Max File Descriptor Count: Unlimited
INFO server comment - OS Name: Windows Vista
INFO server comment - OS Version: 6.0
INFO server comment - OS Architecture: x86
INFO server comment - OS CPU: pentium_pro+mmx pentium_pro pentium+mmx pentium i4
86 i386 i86
INFO server comment - Java Name: Java HotSpot(TM) Client VM
INFO server comment - Java Vendor: Sun Microsystems Inc.
INFO server comment - Java Version: 1.6.0_10-rc
INFO server comment - Java VM Version: 11.0-b15
INFO server comment - Java Spec Version: 1.6
INFO server comment - Java Home: C:\Program Files\Java\jre6
INFO server comment - Java Max Heap Size: 762MB
INFO server comment - Java Architecture: 32
INFO server comment - CMDInterface now listening: [any]:8083
INFO server comment - vhost home directory: C:\Program Files\Wowza Media Systems
\Wowza Media Server Pro 1.7.0
INFO vhost vhost-start _defaultVHost_ -
INFO vhost comment _defaultVHost_ RTMP/RTMPT bind attempt ([any]:1935)
INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
When I try to connect with my app, nothing registers in the WMS console.
Any thoughts on how to troubleshoot this?
Ken Smith
The Windows Service applet shows Wowza running. I can telnet to port 1935. When I launch WMS from the "startup.bat", it seems to start successfully, and doesn't register any error messages, i.e.:
Configure logging: file:///C:/Program Files/Wowza Media Systems/Wowza Media Serv
er Pro 1.7.0/conf/log4j.properties
INFO server server-start Wowza Media Server Pro10 1.7.0 build11414 -
INFO server comment - Serial number: XXXXX-XXXXX-XXXXX-XXXXX-CUGNB
INFO server comment - Maximum connections: 10
INFO server comment - Hardware Available Processors: 4
INFO server comment - Hardware Physical Memory: 1119MB/2047MB
INFO server comment - Hardware Swap Space: 3723MB/4095MB
INFO server comment - Max File Descriptor Count: Unlimited
INFO server comment - OS Name: Windows Vista
INFO server comment - OS Version: 6.0
INFO server comment - OS Architecture: x86
INFO server comment - OS CPU: pentium_pro+mmx pentium_pro pentium+mmx pentium i4
86 i386 i86
INFO server comment - Java Name: Java HotSpot(TM) Client VM
INFO server comment - Java Vendor: Sun Microsystems Inc.
INFO server comment - Java Version: 1.6.0_10-rc
INFO server comment - Java VM Version: 11.0-b15
INFO server comment - Java Spec Version: 1.6
INFO server comment - Java Home: C:\Program Files\Java\jre6
INFO server comment - Java Max Heap Size: 762MB
INFO server comment - Java Architecture: 32
INFO server comment - CMDInterface now listening: [any]:8083
INFO server comment - vhost home directory: C:\Program Files\Wowza Media Systems
\Wowza Media Server Pro 1.7.0
INFO vhost vhost-start _defaultVHost_ -
INFO vhost comment _defaultVHost_ RTMP/RTMPT bind attempt ([any]:1935)
INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
When I try to connect with my app, nothing registers in the WMS console.
Any thoughts on how to troubleshoot this?
Ken Smith
check that when your lost power wowza wasnt writing to your application, i have seen an instance on FMS where a power loss caused the application folder to become corrupt
go back and check that the application folder is still there and the conf file is still ok
go back and check that the application folder is still there and the conf file is still ok
Turns out that I had a couple other RTMP apps installed (for testing/evaluation). When my computer restarted, one of the other apps grabbed the port first. Uninstalling those got things working.
