History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: GATE-104
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Daniel Henninger
Reporter: Daniel Henninger
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
IM Gateway

Yahoo getting 'infinite' InputError's

Created: 10/27/06 07:21 AM   Updated: 05/15/07 10:19 PM
Component/s: Yahoo Transport
Affects Version/s: 1.0 Beta 4
Fix Version/s: 1.1.0

Time Tracking:
Not Specified

Support Plan Customer Issue: No
Resolution Date: 05/15/07 10:19 PM
Acceptance Test - Add?: No


 Description  « Hide
Something is causing some Yahoo users to get relentless input errors and have their cpu usage spike to 100%. No idea what is causing this yet.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Daniel Henninger - 11/05/06 07:01 PM
Turns out the 100% cpu part was due to my crappy threading implementation. The inputerror problem probably still exists though.

Daniel Henninger - 11/07/06 06:21 PM
I can not duplicate this and it may be fixed via GATE-111. (the cpu 100% thing is represented in that issue) Will reevaluate it in the next version after some testers can work with it.

Daniel Henninger - 12/17/06 04:04 PM
I'm still not sure this is happening anymore. Hrm.

Greg Campbell - 04/11/07 12:21 PM
We just saw this with Wildfire 3.2.0 and transports v 1.0.

No idea if this is normal or not, but shortly before the InputErrors started happening, we got:

2007.04.11 11:59:49 [org.jivesoftware.wildfire.gateway.protocols.yahoo.YahooSessionListener.inputExceptionThrown(YahooSessionListener.java:191)] Input error from yahoo: Source: InputThread
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:113)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at ymsg.network.YMSG9InputStream.readBuffer(Unknown Source)
at ymsg.network.YMSG9InputStream.readPacket(Unknown Source)
at ymsg.network.DirectConnectionHandler.receivePacket(Unknown Source)
at ymsg.network.Session$InputThread.run(Unknown Source)

Then, at 2007.04.11 12:00:33 we got the first of many of:

2007.04.11 12:02:34 [org.jivesoftware.wildfire.gateway.protocols.yahoo.YahooSessionListener.inputExceptionThrown(YahooSessionListener.java:191)] Input error from yahoo: Source: InputThread
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:113)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
at ymsg.network.YMSG9InputStream.readBuffer(Unknown Source)
at ymsg.network.YMSG9InputStream.readPacket(Unknown Source)
at ymsg.network.DirectConnectionHandler.receivePacket(Unknown Source)
at ymsg.network.Session$InputThread.run(Unknown Source)

We're running on Linux 2.6.9-42.0.8.ELsmp #1 SMP, i686 i686 i386 GNU/Linux.
We're using 1.5.0_10 Sun Microsystems Inc. – Java HotSpot(TM) Server VM

For what it's worth, I went to the "Sessions" tab in the Wildfire admin console, killed the last session in the list, and the problem was resolved (in that the CPU usage went to normal levels and the error stopped being generated).


Daniel Henninger - 05/15/07 10:19 PM
Fixed via openymsg.