The last thing that you said on December 29 was:
“Or you could start a Wowza AMI and get jar file(s) needed for this. You will have to review the difference, I don’t remember which one off the top of my head, but I think it is obvious when you compare.”
So I followed your advice and compared my install to a large AMI. There were some jars missing (all of which looked like: aws-plugin-xxx.jar) on my install. I then added those plugin jars to my install and responded on December 31 2011:
Things look improved, but still no joy getting vods3 to work. We’re now getting a “item not in cache” error.
2011-12-31 14:41:14 EST connect session INFO 200 71.58.43.38 - defaultVHost vods3 definst 0.036 [any] 1935 rtmp://ec2-107-22-140-189.compute-1.amazonaws.com/vods3/definst/ 71.58.43.38 rtmp http://ec2-107-22-140-189.compute-1…ostreaming.swf MAC 11,1,102,55 334465385 3622 3073 - - - - - - - rtmp://ec2-107-22-140-189.compute-1.amazonaws.com/vods3/definst/ -
2011-12-31 14:41:14 EST create stream INFO 200 - defaultVHost vods3 definst 0.001 [any] 1935 rtmp://ec2-107-22-140-189.compute-1.amazonaws.com/vods3/definst/ 71.58.43.38 rtmp http://ec2-107-22-140-189.compute-1…ostreaming.swf MAC 11,1,102,55 334465385 3694 3413 1 - 0 0 - - - - 0 0.0 rtmp://ec2-107-22-140-189.compute-1.amazonaws.com/vods3/definst/ rtmp://ec2-107-22-140-189.compute-1.amazonaws.com/vods3/definst/ - rtmp://ec2-107-22-140-189.compute-1.amazonaws.com/vods3/definst/ -
2011-12-31 14:41:15 EST comment server INFO 200 - ModuleStreamNameAlias.nameToAlias[play]: streamName:mp4:amazons3/testbucketdc/sample.mp4 alias:{pattern: “*” alias:"${Stream.Name}" wildcardMatches:{[0]: “mp4:amazons3/testbucketdc/sample.mp4”}} result:mp4:amazons3/testbucketdc/sample.mp4 1174.452 - - - - - - - - - -
2011-12-31 14:41:15 EST comment server WARN 404 amazons3/testbucketdc/sample.mp4 MediaReaderH264.open[1]: java.io.IOException: MediaCacheRandomAccessReader.open: Item not in cache: amazons3/testbucketdc/sample.mp4 - - - 1174.457
So I’m looking for a response to the above error message so that I can get out of the box vods3 application working. I’d rather not (even though I did so) use mediacache because there is manually tuning that would be required (as you noted. The documentation also says that vods3 is a customized medicacache module). I’d rather leverage the Wowza team work on customizing vods3 than try to bumble my way through duplicating that work on my own.