I'm getting an error "suds.WebFault: Server raised fault: 'java.lang.NullPointerException'" when I try to play any of the three 12:00 games. The official player is working. Anyone else getting this?

Mlbviewer seems to be down. I get this error after hitting enter "An error occurred in locating the game stream:"

The games are working on the website and yesterday's archives play fine in Mlbviewer, just todays are hosed.

you need to upgrade nexdef to 109:

http://mlb.mlb.com/nexdef-jars/

I still have the same problem with regular non nexdef mlbviewer. And Roy Halladay's starting for the Phils, and Domonic Brown is playing his first MLB game (#1 prospect in all of baseball!)

So darnit.


And, I tried the latest autobahn.jar, and I get the same error on Nexdef mlbviewer. So now we're really screwed!!

Looks like they may have done away with the SOAP. Let's see what tomorrow brings. If it's not working tomorrow, I may not get around to re-working this until the weekend.

If you're a patient coder type, you can get everything you need from using Firebug and the official client. You can re-work the soapevent.py script to just make a GET request of the sort:

The response should be very similar to what we were getting with SOAP but the response parser code probably needs to be reworked.

There is one other uri that needs to be requested after this using info from this response:

It shouldn't be too hard to rework this but I'm short on time and sleep these days. Worst case scenario, I start my vacation next weekend and will definitely have a couple of "do nothing" days to work this over. But likely, I'll want it fixed earlier than that so I can get my own baseball fix satisfied. ;)

Looks like they may have done away with the SOAP. Let's see what tomorrow brings. If it's not working tomorrow, I may not get around to re-working this until the weekend.

If you're a patient coder type, you can get everything you need from using Firebug and the official client. You can re-work the soapevent.py script to just make a GET request of the sort:

The response should be very similar to what we were getting with SOAP but the response parser code probably needs to be reworked.

There is one other uri that needs to be requested after this using info from this response:

It shouldn't be too hard to rework this but I'm short on time and sleep these days. Worst case scenario, I start my vacation next weekend and will definitely have a couple of "do nothing" days to work this over. But likely, I'll want it fixed earlier than that so I can get my own baseball fix satisfied. ;)

Oh no, and all this during my vacation. Hasn't MLB ever heard of "never change a running system" ;)?
Thanks for fixing it ASAP!

Let's help out
 

Listen, I know not all of us can contribute code to this project, but mlbviewer adds a *lot* of value to my mlb.tv subscription. Once again there's a problem and, once again, daftcat is saying he'll step up and get it figured out. He's invested a lot of time and energy so many of us can better enjoy our downtime.

I just donated another few bucks as both a 'thank you' and, hopefully, a bit more motivation. If any of you haven't done so, or haven't done so recently, I'd recommend doing the same.

Thanks Clark! Every little bit helps.

So I did a quick test constructing the first request URL above and I got the correct response. So that's the good news. The bad news is that it is one fugly piece of XML. I'm sure it still follows the same structure and I already have XML parsing code. It will just take awhile for me to swap out the soap code for an XML handler and verify all the information is still in the correct places in the response. Maybe this weekend but definitely sometime next week. There's a whole Dodgers-Giants series I'll be missing this weekend that I'll want to catch up on soon (especially now that the Giants are actually an interesting team this year.)

There are a lot of places where I place http requests and it would make sense if I could streamline that into a shared opener. That way if we needed to support a proxy, it would be one place to change. Unfortunately, that's not the case. And while yours is definitely a valid case, most people asking for proxy support want to use it to circumvent the blackout restrictions. This is such a big no-no that it is one of the few places in the MLB.TV Terms Of Service THAT THEY USE ALL CAPS.

So the risk outweighs the reward and I'm going to say proxy will not be supported.

You shouldn't be using your corporate bandwidth for personal use anyway. :p

I really like the iPhone At Bat app because I have a $2 GoGoStand (http://gogostand.com and can watch games over 3G without raising any eyebrows in the IT department.

The other problem with proxy support is that I'm not sure rtmpdump has proxy support so even if mlbviewer had it, you'd still be stuck further down the road.

Following daftcat's direction and being the patient coder type :) I hacked together a patch for soapevent.py that lets me get games again. It could use a little love/error checking, but it seems to work for me...

I've attached the patch. It can be applied from the trunk of a svn checkout. For those of you who don't deal with patches, I attached the whole test/soapevent.py file.

Hope this helps someone else get their baseball fix ;)

Thanks a lot carpie! It's a good workaround until mlbviewer itself is updated. Good job!

How can I donate?
 

How can I send a few pounds to say a big thank-you, and also encourage a fix to the current problems?

Check out the very end of the README file to see the address where Daftcat can receive your Paypal donations.