What steps will reproduce the problem? 1. send 'status' or 'somehost/someservice' to the molniya XMPP contact

What is the expected output? What do you see instead? expected: a message that says something about the status, e.g. incoming ICBM

actual output on the command line: W, [2010-08-08T19:37:55.011034 #18667] WARN -- : Reconnecting after exception in close: W, [2010-08-08T19:37:55.014241 #18667] WARN -- : Reconnecting after exception in start: Server Disconnected! /usr/lib/ruby/1.8/xmpp4r/streamparser.rb:68:in parse' /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:186:incall' /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:186:in handle' /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:186:ineach' /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:186:in handle' /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:95:inparse' /usr/lib/ruby/1.8/xmpp4r/streamparser.rb:79:in parse' /usr/lib/ruby/1.8/xmpp4r/stream.rb:75:instart' /usr/lib/ruby/1.8/xmpp4r/stream.rb:72:in initialize' /usr/lib/ruby/1.8/xmpp4r/stream.rb:72:innew' /usr/lib/ruby/1.8/xmpp4r/stream.rb:72:in start' /usr/lib/ruby/1.8/xmpp4r/connection.rb:119:instart' /usr/lib/ruby/1.8/xmpp4r/client.rb:87:in start' /usr/lib/ruby/1.8/xmpp4r/client.rb:175:inauth_sasl' /usr/lib/ruby/1.8/xmpp4r/client.rb:110:in auth' ./molniya.rb:200:inconnect' ./molniya.rb:193:in initial_connect' /usr/lib/ruby/1.8/timeout.rb:67:intimeout' ./molniya.rb:192:in initial_connect' ./molniya.rb:172:ininitialize' ./molniya.rb:526:in new' ./molniya.rb:526:ininitialize' ./molniya.rb:765:in new' ./molniya.rb:765:inlaunch' -e:1 /usr/lib/ruby/1.8/xmpp4r/errors.rb:43:in to_s': undefined methoderror' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/xmpp4r/connection.rb:111:in accept_features' from /usr/lib/ruby/1.8/xmpp4r/connection.rb:79:inconnect' from /usr/lib/ruby/1.8/xmpp4r/client.rb:70:in connect' from ./molniya.rb:198:inconnect' from ./molniya.rb:205:in reconnect' from ./molniya.rb:182:ininitialize' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:150:in call' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:150:inparser_end' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:147:in initialize' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:147:innew' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:147:in parser_end' from /usr/lib/ruby/1.8/xmpp4r/streamparser.rb:60:inparse' from /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:142:in call' from /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:142:inparse' from /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:142:in each' from /usr/lib/ruby/1.8/rexml/parsers/sax2parser.rb:142:inparse' from /usr/lib/ruby/1.8/xmpp4r/streamparser.rb:79:in parse' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:75:instart' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:72:in initialize' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:72:innew' from /usr/lib/ruby/1.8/xmpp4r/stream.rb:72:in start' from /usr/lib/ruby/1.8/xmpp4r/connection.rb:119:instart' from /usr/lib/ruby/1.8/xmpp4r/client.rb:87:in start' from /usr/lib/ruby/1.8/xmpp4r/client.rb:175:inauth_sasl' from /usr/lib/ruby/1.8/xmpp4r/client.rb:110:in auth' from ./molniya.rb:200:inconnect' from ./molniya.rb:193:in initial_connect' from /usr/lib/ruby/1.8/timeout.rb:67:intimeout' from ./molniya.rb:192:in initial_connect' from ./molniya.rb:172:ininitialize' from ./molniya.rb:526:in new' from ./molniya.rb:526:ininitialize' from ./molniya.rb:765:in new' from ./molniya.rb:765:inlaunch' from -e:1

What version of the product are you using? On what operating system? 0.3

Please provide any additional information below. 'help' works, so does '$hostname', bogus input is also properly answered to

'status' works actually if there is nothing to report. If there is but one warning, it dies.

Hello,

The stack traces you pasted are from a reconnection attempt; I'm guessing the error in handling the 'status' command made it lose its connection somehow and attempt to reconnect. Can you please try the current code in the trunk, run it in debug mode with -d, and attach the complete log output?

Thanks!

This is trunk code (thanks for fixing the other issues!). To me it looks like it gets disconnected while trying to send the response and then is unable to recover? See attached log.

yeah, usr/lib/ruby/1.8/ try 1.9.