|
|
|
Rockstar
Group: Forum Members
Last Login: 6/17/2008 6:41:16 PM
Posts: 108,
Visits: 144
|
|
For the past week or so, I keep getting errors on GO. The error is:
12 communciation error: 503 Service Unavailable java.io.IOException - 503 service unavailable
Any ideas?
Also on a side note, I know there is a beta version of GO for Windows, when will it be available for Blackberry?
Matt Zur
zurnet.com
zsubway.com
|
|
|
|
|
Forum Deity
Group: Forum Members
Last Login: 6/19/2008 12:21:17 PM
Posts: 1,095,
Visits: 1,551
|
|
| We are aware of this error and have notified the development team. Can you tell me what version of the reader you have? Is it the personal or the corporate version? If it is the corporate version, are you going through a BES? Regarding your second question; There are separate development teams for the Blackberry (J2ME) reader and the Windows Mobile reader. They do collaborate on ideas and goals, but are not on the same developmental timeline. That said, we just released an update, version 2.2.5, for the J2ME reader. It is available here.
Keith Franklin
|
|
|
|
|
Forum Member
Group: Forum Members
Last Login: 5/19/2008 7:45:20 AM
Posts: 62,
Visits: 137
|
|
I've been seeing the same error for at least the past week using the BIS version on T-Mobile's network.
I get the error sometimes when opening feed items and sometimes when opening feeds. When I get the error opening a feed item the item is displayed (since it was already downloaded) but the article is not marked as read on the server (since the web server Go! communicates with returned the "503 Service Unavailable" error). After this happens Go! shows that the feed I was in contains unread items but when you open the feed they are all marked as read, the only way to correct this is to use one of the other Newsgator readers to mark the feed as read (Mark all as read in Go! has no effect in this case).
There are actually two problems here:
1) When Go! notifies the server that a feed item is read and the server returns the 503 HTTP error, it should not mark the item as read on the device to prevent the feed from getting out of sync.
2) The server Go! communicates with is having problems which is causing it to return "503 Service Unavailable" when clients are requesting the contents of feeds and when marking articles as read/unread.
Thanks,
Gordon
|
|
|
|
|
Forum Deity
Group: Forum Members
Last Login: 6/19/2008 12:21:17 PM
Posts: 1,095,
Visits: 1,551
|
|
| Thanks for the detailed input guys. I have created a bug report for this problem and have sent it to the development team. I will respond here when new information comes in. (Case 112238) If anyone has anything else to add, please feel free to throw in your observations.
Keith Franklin
|
|
|
|
|
Rockstar
Group: Forum Members
Last Login: 6/17/2008 6:41:16 PM
Posts: 108,
Visits: 144
|
|
I'm using the personal version on my Blackberry 8100 on ATT. Hope this helps.
Matt Zur
zurnet.com
zsubway.com
|
|
|
|
|
Forum Member
Group: Forum Members
Last Login: 12/17/2007 6:44:15 PM
Posts: 3,
Visits: 14
|
|
I'm having the same problem using a Blackberry 8703e over Verizon using versions 2.2.1 and 2.2.5.
Thanx,
M
|
|
|
|
|
Forum Deity
Group: Forum Members
Last Login: 6/19/2008 12:21:17 PM
Posts: 1,095,
Visits: 1,551
|
|
Thank you. If anyone else is having this problem, please tell us what version you are using. The latest available download is version 2.2.5 but it appears that this is a cross-version problem and not a bug in the new build.
Keith Franklin
|
|
|
|
|
Rockstar
Group: Forum Members
Last Login: 6/17/2008 6:41:16 PM
Posts: 108,
Visits: 144
|
|
I just dl'ed the new build and am still having an issue. As I had said, it's only been happening within the past few weeks or so... prior to that I had never received the error.
-Matt
Matt Zur
zurnet.com
zsubway.com
|
|
|
|
|
Forum Member
Group: Forum Members
Last Login: 5/19/2008 7:45:20 AM
Posts: 62,
Visits: 137
|
|
The error, 503 Service Unavailable, indicates it is a problem with the server that Go! is communicating with to retrieve feed information and to mark items as read.
The following, from Microsoft's web site, are possible reasons why Microsoft's IIS server (the type of server Go! communicates with) would return this error:
• IIS cannot start any new worker processes because of limited system resources or because starting a new worker process would exceed the DemandStartThresholdproperty.
• Bandwidth throttling is enabled, but the filter addition fails.
• The control channel or internal configuration group for the URL is inactive.
• The send for a request that was serviced from the cache failed (typically under low memory conditions).
|
|
| |