Wowza Community

error: java.io.IOException: The handle is invalid

I am trying to perform on an install of Wowza Media Server 2.1.2 (yesterday i also tried 2.2.3) on an IBM x3650 M2 server, with a Windows 2008 Server 64bit Edition. So far, no matter what i’ve tried, as soon as I start the Wowza Service, the log file is getting full of:

ERROR server comment 2011-04-06 21:51:43 - - - - - 1.2 - - - - - - - - error: java.io.IOException: The handle is invalid

This does not happen when i perform the exact same install, using Windows 2008 Server 32bit Edition (or any other Windows 32bit Edition). Even when using the exact settings of an existing 32bit server. Or when having a clean install of a server with just JRE (either 32bit or 64bit installed) and Wowza (2.1.2 and 2.2.3).

Could you please assist me in finding what may be the cause of this?

Regards,

Sefy

Sefy,

Install the Java JDK that is just labeled “Windows”, instead of the “Windows 64” version.

http://www.oracle.com/technetwork/java/javase/downloads/index.html

Richard

Make sure the /conf/Server.license is plain text.

What are the rest of the startup lines?

What is java version:

java -version

Check the Wowza environment variables WMSAPP_HOME and WMSCONFIG_HOME to see if there is a slash at the end, and if so, edit that out.

echo %WMSAPP_HOME%
echo %WMSCONFIG_HOME%

If you see a slash at the end, something like this:

C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server 2\

Remove the slash.

Richard

I’m not sure. In a very similar case, the last post was Charlie’s advice to uninstall thoroughly then re-install:

http://www.wowza.com/forums/showthread.php?6644-SERIOUSLY!-install-troubles/page2#12

Before you re-install, make sure your java -version command returns something like this (adjust for version):

java version “1.6.0”

Java™ SE Runtime Environment (build 1.6.0-b105)

Java HotSpot™ 64-Bit Server VM (build 1.6.0-b105, mixed mode)

I installed regular Windows JDK over/after the 64 bit version because of problem with just 64 bit version with Wowza, which fixed the problem and still java -version reports 64-bit server VM (I am not at all sure why that worked or if that is entirely correct, but it did work).

Richard

Sefy,

Java version looks okay. Go ahead with complete uninstall, remove everything and reboot for good measure, then re-install.

Richard

Was the output of java -version the same after re-installing Java? Seems like that was okay and did not have been to be re-installed.

I am not sure what the problem is. Zip up conf and logs folders and send them to support@wowza.com. Include a reference to this thread.

Richard

Sefy,

Actually, in this case, zip up the entire Wowza folder and send.

Richard

Sefy,

Yes, post the zip file on YousendIt service or on your web server if you have one.

Richard

Hi Richard,

I tried that originally with the JRE 32bit, but now as per your suggestion, i’ve tried with the JDK 32bit and i’m getting the exact same results. This system Windows 2008 Server R2 64 bit Edition, which contains ALL updates including SP1, JDK(was JRE before) and the Wowza server latest 2.2.3 using it’s default installation settings.

Still getting the same error as before.

Regards,

Sefy

Service.license is in plain text

Startup lines of which files? the log file?

Java version is: 1.6.0_24

Result of %WMSAPP_HOME% = C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server 2.2.3

Result of %WMSCONFIG_HOME% = Result of %WMSAPP_HOME% = C:\Program Files (x86)\Wowza Media Systems\Wowza Media Server 2.2.3

Anything else that might help ?

Hi Richard,

The machine i’m using has Windows 2008 R2 x64 which includes all updates, i’ve made a Ghost of it before i did any other installation. So all it has now is Java x64 with Wowza. My java -version result is similar to yours, with only a difference in the build, which looks like this:

java version “1.6.0_24”

Java™ SE Runtime Environment (build 1.6.0_24-b07)

Java HotSpot™ 64-Bit Server VM (build 19.1-b02, mixed mode)

Even just trying to start Wowza using it’s own default settings, causes the logs to be filled up with that line of error.

Regards,

Sefy

Hi Richard,

Nope, tried as you suggested, i uninstalled, removed everything (even made sure folders are deleted), rebooted.

Then installed Java x64 and then Wowza, tried to start it (using it’s own default settings) and same errors keep showing up in the logs.

In like a few seconds, it already goes to 1mb log file.

Thanks,

Sefy

Yes, Java -version was the same, i just did a re-install so i could eliminate all possible issues.

Won’t zipping up the entire folder be a bit large for an email? the zip file (using 7z Ultra compression) is 70mb size.

I can use YouSendIt or any other file service, but my email won’t allow me to attach a file this big.

Thanks for all your help!

Sefy

Hi Richard,

The email is being sent now with the file on YouSendIt, i’ve been asked by my boss to remove the Server.license file, but other then that, this is the entire Wowza Folder.

Regards,

Sefy