kelly_js1087
|
Posted: October 08, 2009 20:51 by kelly_js1087
|
|
Hello, This - unlike my last post, is not on operator error - or in more blunt parlance, RTFM!  I've only had the sync process complete successfully one time. Most other times, it fails with the error "java.net.SocketTimeoutException: Read timed out". A few times, it even fails earlier in the process, saying it can't erase my calendar but the above read error is by far and away the most common - at least 95% of the failures are due to this error. Now the odd thing is that even when I receive this error, about 1/2 the time JCalendarCopy succeeds in writing my MAC iCal calenday to my Edgecal calendar anway. Go figure. So when this error occurs (again, about 95% of the time), I always look at the Edgecal calendar to see if the Mac calendar was actually written (even though I received the error). Is this typical behavior? Is there some setting in JCalendarCopy that I'm overlooking? Thanks, Kelly PS I'm using a PPC-based Mac Mini, running 10.5.8 (Build 9L31a) to access Edgecal. I'm not logged into SWAN, although I've tried that and the results are the same. |
java.net.SocketTimeoutException: Read timed out
3 posts
Replies: 2 - Last Post: October 13, 2009 05:29
by: kelly_js1087
by: kelly_js1087
showing 1 - 3 of 3
|
kelly_js1087
|
Posted: October 13, 2009 05:29 by kelly_js1087
|
|
Thanks. Worked fineI kw |
Replies: 2 - Last Post: October 13, 2009 05:29
by: kelly_js1087
by: kelly_js1087
