|
|
|
[
Permlink
| « Hide
]
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.
I can not duplicate this and it
I'm still not sure this is happening anymore. Hrm.
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 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 We're running on Linux 2.6.9-42.0.8.ELsmp #1 SMP, i686 i686 i386 GNU/Linux. 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). |
|||||||||||||||||||||||||||||||||||||||||||||||||||