1.2.4d: AIM Gateway Not Working

Ever since upgrading Openfire to 3.6.0a and then the IM Gateway plugin to 1.2.4d, our users have not been able to use AIM. I can see their registrations in the console, but they are greyed out, indicating that no connection has been established (and the Last Login = never). In Spark, the AIM icon is not greyed out, indicating that a connection has been established, but no AIM contacts are displayed and they are not reported as being logged in and available from the other side of the transport. I have deleted and reinstalled the plugin, but it didn’t seem to make any difference. Any ideas or advice?

We just upgraded to 3.6.0a and 1.2.4d and we are having the exact same issue. However, we also cannot get the Yahoo transport to function. MSN seems to be working perfectly.

Like you mentioned, the AIM transport shows up in Spark as “Online”, but no AIM contacts are listed. (also confirmed this to be the case using the Psi client). Yahoo shows up as offline in Spark and we receive a logon failure message in Spark specifying an “unknow error.”

I can successfully log on to AIM and Yahoo Messenger when going directly to each service and connection tests run from the Gateways section of the Admin Console show success for MSN, Yahoo, and AIM.

Adding Log Entries:

When logging on to Yahoo via transport:

2008.09.17 15:06:36 JettyLog: EXCEPTION
javax.net.ssl.SSLException: Inbound closed before receiving peer’s close_notify: possible truncation attack?
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLEngineImpl.closeInbound(Unknown Source)
at org.mortbay.jetty.security.SslHttpChannelEndPoint.fill(SslHttpChannelEndPoint.j ava:448)
at org.mortbay.jetty.security.SslHttpChannelEndPoint.fill(SslHttpChannelEndPoint.j ava:200)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:282)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)
2008.09.17 15:06:36 JettyLog: EOF
2008.09.17 15:06:36 Received iq packet:
2008.09.17 15:06:36 yahoo: Sending packet:
2008.09.17 15:06:37 Yahoo login caused IO exception:
java.io.InterruptedIOException: Login timed out
at org.openymsg.network.Session.login(Unknown Source)
at org.jivesoftware.openfire.gateway.protocols.yahoo.YahooSession$1.run(YahooSessi on.java:95)
2008.09.17 15:06:37 yahoo: Sending packet: Failed to log into Yahoo! messenger account. (unknown error)
2008.09.17 15:06:44 session 890 timeout
2008.09.17 15:06:44 session 890 sent message PNG

Debug log entry when attempting to logon to AIM:

2008.09.17 15:12:56 Received iq packet:
2008.09.17 15:12:56 aim: Sending packet:
2008.09.17 15:12:57 Received presence packet: da39a3ee5e6b4b0d3255bfef95601890afd80709</ph oto>da39a3ee5e6b4b0d3255bfef95601890afd80709</ x>
2008.09.17 15:12:57 005575 (01/05/00) - Connection #10 tested: OK
2008.09.17 15:12:57 005576 (01/05/00) - Connection #10 tested: OK
2008.09.17 15:12:57 005576 (01/05/00) - Connection #6 tested: OK
2008.09.17 15:12:57 005577 (01/05/00) - Connection #6 tested: OK
2008.09.17 15:12:57 An existing resource has changed status: jdoe@imserver.company.com/spark
2008.09.17 15:12:57 Sending SNAC command: SetInfoCmd: info=InfoData:
2008.09.17 15:12:57 Setting up SNAC request and listener: SetInfoCmd: info=InfoData:,null
2008.09.17 15:12:57 Handling request SnacRequest for SetInfoCmd: info=InfoData:: listeners: null, responses: null
2008.09.17 15:12:57 Sending SNAC command: ServiceRequest for family 0x2
2008.09.17 15:12:57 Setting up SNAC request and listener: ServiceRequest for family 0x2,null
2008.09.17 15:12:57 Handling request SnacRequest for ServiceRequest for family 0x2: listeners: null, responses: null
2008.09.17 15:12:57 eep! can’t find a service redirector server.
2008.09.17 15:12:57 Sending SNAC command: SetExtraInfoCmd: blocks=[ExtraInfoBlock: type=0x2 (TYPE_AVAILMSG), extraData=<ExtraInfoData: flags=0x4 (FLAG_AVAILMSG_PRESENT), data=00 00 00 00>]
2008.09.17 15:12:57 Setting up SNAC request and listener: SetExtraInfoCmd: blocks=[ExtraInfoBlock: type=0x2 (TYPE_AVAILMSG), extraData=<ExtraInfoData: flags=0x4 (FLAG_AVAILMSG_PRESENT), data=00 00 00 00>],null
2008.09.17 15:12:57 Handling request SnacRequest for SetExtraInfoCmd: blocks=[ExtraInfoBlock: type=0x2 (TYPE_AVAILMSG), extraData=<ExtraInfoData: flags=0x4 (FLAG_AVAILMSG_PRESENT), data=00 00 00 00>]: listeners: null, responses: null
2008.09.17 15:12:57 Sending SNAC command: ServiceRequest for family 0x1
2008.09.17 15:12:57 Setting up SNAC request and listener: ServiceRequest for family 0x1,null
2008.09.17 15:12:57 Handling request SnacRequest for ServiceRequest for family 0x1: listeners: null, responses: null
2008.09.17 15:12:57 Updating status [available,null] for TransportSession[jdoe@imserver.company.com]
2008.09.17 15:12:57 aim: Sending packet:
2008.09.17 15:13:12 session 920 timeout
2008.09.17 15:13:12 session 920 sent message PNG

Jeff

Anyone else out there experiencing this issue? We just rolled out Spark to our company and now look quite foolish for upgrading / breaking two of the three transports people were using (Yahoo & AIM)…just as end-user adoption was on the rise.

Daniel (assuming you would be eventually replying to this post/thread) - do you have any suggestions on what we should try to resolve on our end? Also, is there any other info can I provide to you? I’ve seen some MSN Transport issues reported in other discussions where you indicate there is some SSL issue “going around.”

Lastly, we used the Red Hat (RPM) build of Openfire 3.6.0a. AngryPenguin - which build did you use?

Any advice/reply would be much-appreciated.

Jeff