2.2.1 - Java error?

Newsgator Forums
Home       Members    Calendar    Who's On
Welcome Guest ( Login | Register )
        


««12

2.2.1 - Java error? Expand / Collapse
Author
Message
Posted 10/11/2007 3:25:49 PM
Forum Member

Forum Member

Group: Forum Members
Last Login: 5/19/2008 7:45:20 AM
Posts: 62, Visits: 137
Great news, thanks!
Post #32080
Posted 10/12/2007 3:01:32 PM
Rockstar

Rockstar

Group: Forum Members
Last Login: 7/13/2008 11:08:12 AM
Posts: 110, Visits: 145
Now I'm getting a new error:

Update failed: java.net.Socket Exception: Connection Reset.

-Matt


Matt Zur
zurnet.com
zsubway.com
Post #32106
Posted 10/12/2007 4:57:02 PM
Forum Member

Forum Member

Group: Forum Members
Last Login: 10/12/2007 4:45:55 PM
Posts: 1, Visits: 1
FWIW, I continue to get a variety of Java errors. I've actually just switched from a Verizon 7130 to a Sprint 8830. I had errors on the 7130 with 2.1x and then with 2.2.5. The issues continue with 2.2.5 on the 8130. NG has become basically unusable. If I can't get this resolved I'd like a refund on the service. Thanks,
Rich
Post #32112
Posted 10/12/2007 6:17:36 PM
Forum Member

Forum Member

Group: Forum Members
Last Login: 5/19/2008 7:45:20 AM
Posts: 62, Visits: 137
zurdog (10/12/2007)
Now I'm getting a new error:

Update failed: java.net.Socket Exception: Connection Reset.

I'm getting the same error as well (pretty often, on T-Mobile's network), this is probably also related to the web server.

Due to the bug in Go! in which it doesn't handle network errors properly (items are marked as read on the device even though an error was encountered when attempting to mark it as read on the server), the unread counts on the device are wrong and can only be corrected by reading the same feed using one of the other NG readers.
Post #32113
Posted 10/14/2007 1:21:54 PM
Forum Deity

Forum Deity

Group: Forum Members
Last Login: 6/19/2008 12:21:17 PM
Posts: 1,095, Visits: 1,551
We apologize for the connection issues during the past week. We had a routing issue that affected one of the servers in the cluster. We had a tough time identifying the problem, and the affected server.

Our Operations team had been working through the weekend, and we now believe this problem to be resolved. Again, we apologize for any inconvenience, and thank you for your patience.

Keith Franklin

Post #32125
« Prev Topic | Next Topic »

««12

All times are GMT -7:00, Time now is 11:30pm

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.031. 8 queries. Compression Disabled.

NewsGator.com | Support | Developers | Partners | Press | Company
© Copyright 2003-2008  NewsGator Technologies, Inc. All Rights Reserved.
Copyright Information | Privacy Policy | Terms of Service
Microsoft Gold Certified Partner