Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: vods3 setup nullpointerexception

  1. #1

    Unhappy vods3 setup nullpointerexception

    Sorry, I know that this must be a silly setup mistake, but I've been banging my head on this for most of a day. We are migrating from wowza2 server to wowza 3. Everything (live/vod) is going fine except for vods3 not working

    ERROR server comment 2011-12-29 08:26:35 - - - - - 56327.821play: error opening file (/usr/local/WowzaMediaServer/content/amazons3/testbucketdc/sample.mp4): java.lang.NullPointerException

    rtmp://[instance]/vods3/_definst_/
    or
    rtmp://[instance]/vods3/

    mp4:amazons3/[bucketname]/sample.mp4

    Whether we use _definst_ or not, vods3 seems to not be accessing S3. Instead it appears to be accessing vod via the local wowza content folder.

    Server.xml has the S3 license key pair. bucket name has simple alphabet characters w/o any uppercase.

    Is there debug that I can turn on or something? NullPointerException is rather generic.

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Your vods3 app is not configured correctly. You might want to start over with a new instance. Do not use a Startup package, then check the vods3 application that is included.

    Richard

  3. #3

    Default

    by "configure", I assume that you mean conf/vods3/Application.xml. I freshed copied in Application.xml from the default_3.0.zip downloaded, unzipped, and copied it in unmodified only yesterday.

  4. #4
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Make sure you got the right one, it is acting like a regular vod application, appears to be missing the MediaReader property necessary in the Application.xml for vods3.

    Or start a new instance without a startup package to get a working copy that you can refer to.

    Otherwise, zip up and send conf and logs folders to support@wowza.com. Include a link to this thread for reference. (due to the holidays, it might be a few days to turn-around)

    Richard

  5. #5

    Default

    zipped and sent. Okay since I'm stuck I did some more digging.

    1. Why are you guys output errors into wowza_access.log instead of wowza_error.log? I missed some (what appear to be major) clues because of this.

    2011-12-29 13:00:24 EST comment server ERROR 500 - RandomAccessReaderFactory: createRandomAccessReader: java.lang.ClassNotFoundException: com.wowza.wms.plugin.amazonaws.ec2.mediacache.MediaCacheRandomAccessReaderAmazonEC2 - - - 31.398 - - - - - - - - - - - - - - - - - - - - - - - - -
    2011-12-29 13:00:24 EST comment server ERROR 500 - play: error opening file (/usr/local/WowzaMediaServer/content/amazons3/testbucketdc/sample.mp4): java.lang.NullPointerException -

    2. Looks like I'm missing MediaCachRandomAccessReaderAmazonEC2 class file.
    3. Downloaded fresh Linux install from the store.
    4. Examined every jar file in lib and none of them contain this Class file.
    5. Looked at the fresh new install and there isn't a vods3 conf folder. So I'm guessing that I did the correct thing in downloading the default_3.0.zip to get vods3 conf/Application.xml

    That Application.xml from default_3.0.zip contains a MediaReader (as you note above) which references this class file. Where can I get this class from since it does not seem to come from the installer in the store?

    <MediaReader>
    <Properties>
    <Property>
    <Name>randomAccessReaderClass</Name>
    <Value>com.wowza.wms.plugin.amazonaws.ec2.mediacache.MediaCacheRandomAccessReaderAmazonEC2</Value>
    </Property>
    <Property>
    <Name>bufferSeekIO</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
    </Property>
    </Properties>
    </MediaReader>

  6. #6
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    It is not included in the installer, vods3 is part of pre-built Wowza AMIs. You can use MediaCache instead:

    http://www.wowza.com/forums/content....nd-scalability

    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.

    I would just use one of the pre-built lickey AMIs:
    http://www.wowza.com/forums/content.php?23#lickey

    Richard
    Last edited by rrlanham; 12-29-2011 at 11:52 AM.

  7. #7

    Unhappy

    Sorry for the delay, but we lost our instance and had to restore it. After restoring, I pushed the aws-plugin-xxx.jar files over to it that I downloaded from the post link that you put above.
    Things look improved, but still no joy. I tried with and without _definst_ w/o difference. 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

  8. #8

    Default

    It's pretty disappointing that you guys don't support the installer on EC2 and require us to take one of the images instead.

  9. #9
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    It's not a requirement. You can install Wowza on a EC2 instance using the installer.

    Be sure to tune:
    http://www.wowza.com/forums/content....ormance-Tuning

    The pre-built AMIs are self-tuning.

    Richard

  10. #10

    Default unanswered error message

    Okay well if you do support it, can you answer my question from: 12-31-2011, 12:49 PM posted above?

    I gave up on you guys responding especially after the sales guy told me that we need to use the AMI to get vods3 working. After giving up, I installed and got running mediacache module, but I'd really prefer to use the standard vods3. Even though mediacache works, I fear that there is something still wrong with my install that I'd like to get to the bottom of.

Page 1 of 2 12 LastLast

Similar Threads

  1. MediaCache NullPointerException
    By rminari in forum Wowza Media Server 3 for Amazon EC2 Discussion
    Replies: 1
    Last Post: 05-15-2012, 05:16 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •