I'm having the same problem. My code just stopped working with a "java.net.ConnectException: Connection refused". Does anybody know if this library will be udpated?
Hmm ... well my code just started working again. I came across this note from an AOL Technical Product Support rep that might explain it:
Severity: Sev 2 (degradation to functionality of presence updates to the buddy list)
Start Date: 03 Sept 2008 4:40 AM ET
End Date: 04 Sept 2008, 3:30 PM ET
Description: AOL IM services (AIM and ICQ) was impacted yesterday morning following a scheduled maintenance upgrade on one of the core messaging infrastructure components supporting both desktop and mobile IM products. The end user may have experienced delays to presence updates on the buddy list. The binary was backed out at approximately 3 PM ET yesterday. Residual affects of the installation caused delays in stabilization of the service for an additional 24 hours. As of 3:30 PM today, the service is expected to be fully restored and stabilized.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
http://www.bigblueball.com/forums/t31856-cannot-connect-to-tocoscaraolcom.html
I can't connect to http://toc.oscar.aol.com:8080 anymore, and it looks like the TOC protocol is no longer supported. But TOC2 appears to be supported.
Any plans on converting JAim to TOC2?
John
I'm having the same problem. My code just stopped working with a "java.net.ConnectException: Connection refused". Does anybody know if this library will be udpated?
Karim Varela
http://www.i-booze.com
Hmm ... well my code just started working again. I came across this note from an AOL Technical Product Support rep that might explain it:
Severity: Sev 2 (degradation to functionality of presence updates to the buddy list)
Start Date: 03 Sept 2008 4:40 AM ET
End Date: 04 Sept 2008, 3:30 PM ET
Description: AOL IM services (AIM and ICQ) was impacted yesterday morning following a scheduled maintenance upgrade on one of the core messaging infrastructure components supporting both desktop and mobile IM products. The end user may have experienced delays to presence updates on the buddy list. The binary was backed out at approximately 3 PM ET yesterday. Residual affects of the installation caused delays in stabilization of the service for an additional 24 hours. As of 3:30 PM today, the service is expected to be fully restored and stabilized.