-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Hudson: 1.389
OS: Centos 5.3
Latest released instant-messaging and jabber plugins as of date ticket opened
-
Powered by SuggestiMate
Everything was working great for a few minutes. We issued a bunch of commands and all was good. We then went back awhile later and no output was being received. We are using a standard jabber.org account. We can see from the server log that messages from our IM client are reaching the server but we just don't get anything back. If we bounce the config (not rebooting or restarting hudson) we can see the hudson jabber disconnect/reconnect. We can then send 1 command and get a response. After that we get nothing back (the !status command for example).
Hudson Server Log:
Jan 5, 2011 1:46:35 PM hudson.plugins.jabber.im.transport.JabberIMConnection$PrivateChatListener processPacket
INFO: Message from myusername@gmail.com/gmail.071F0034 : !status
Jan 5, 2011 1:46:31 PM hudson.plugins.jabber.im.transport.JabberIMConnection$PrivateChatListener processPacket
INFO: Message from myusername@gmail.com/gmail.071F0034 : !help
Jan 5, 2011 1:46:21 PM hudson.plugins.jabber.im.transport.JabberIMConnection connect
INFO: Connected to XMPP on jabber.org:5222/jabber.org using TLS
Jan 5, 2011 1:46:21 PM hudson.plugins.jabber.im.transport.JabberIMConnection setupSubscriptionMode
INFO: Accepting all subscription requests
Jan 5, 2011 1:46:20 PM hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run
INFO: Trying to reconnect
[JENKINS-8426] after first message, jabber doesn't return any messages
BTW: you can try to the the log level of the Jabber bot the FINEST to get more log output in Hudson. The logger name is hudson.plugins.jabber.im
Ok, I added the logger for just the plugin, reset the hudson server config to bounce the jabber client.
When messaging from a jabber-client account to the jabber-hudsonserver account everything worked fine.
When messaging from a gtalk account to the jabber-hudsonserver, the first message we got a status response. Then nothing.
If we go back to our jabber-client account and try to message, we also get nothing back.
Here is the log output:
Jan 6, 2011 3:51:08 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Jan 6, 2011 3:50:45 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: !help
Jan 6, 2011 3:50:45 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: !help{7CCA5408-A1F4-4DEC-B89D-1AD4DD0ABC11}
Jan 6, 2011 3:50:44 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: Qjyz757
Jan 6, 2011 3:50:44 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: {7CCA5408-A1F4-4DEC-B89D-1AD4DD0ABC11}
Jan 6, 2011 3:50:38 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Jan 6, 2011 3:50:22 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: !helpQjyz756
Jan 6, 2011 3:50:22 PM hudson.plugins.jabber.im.transport.JabberIMConnection$PrivateChatListener processPacket
INFO: Message from myusername@gmail.com/gmail.071FDF03 : !help
Jan 6, 2011 3:50:22 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: !helpgjk4_Q-1NQX6MPbbHSTLzChSnBE
Jan 6, 2011 3:50:14 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: !statusQjyz755
Jan 6, 2011 3:50:14 PM hudson.plugins.jabber.im.transport.JabberIMConnection$PrivateChatListener processPacket
INFO: Message from myusername@gmail.com/gmail.071FDF03 : !status
Jan 6, 2011 3:50:14 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: !statuso6t1o2pmohqqNJvjO3a1MQgQhBs
Jan 6, 2011 3:50:07 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT: Available commands:
abort <job> - specify which job to abort
alias [<alias> [<command>]] - defines a new alias, deletes one or lists all existing aliases
botsnack [<snack>] - om nom nom
build <job> [now|<delay>[s|m|h]] [<parameterkey>=<value>]* - schedule a job build, with standard, custom or no quiet period
comment <job> <build-#> <comment> - adds a description to a build
h [<job>|-v <view>] - show the health of a specific job, jobs in a view or all jobs
health [<job>|-v <view>] - show the health of a specific job, jobs in a view or all jobs
jobs [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs
q - show the state of the build queue
queue - show the state of the build queue
s [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs
schedule <job> [now|<delay>[s|m|h]] [<parameterkey>=<value>]* - schedule a job build, with standard, custom or no quiet period
status [<job>|-v <view>] - show the status of a specific job, jobs in a view or all jobs
testresult [<job>|-v <view>] - show the test results of a specific job, jobs in a view or all jobs
userstat <username> - prints information about a Hudson userQjyz753
Jan 6, 2011 3:50:07 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: !helpQjyz754
Jan 6, 2011 3:50:07 PM hudson.plugins.jabber.im.transport.JabberIMConnection$PrivateChatListener processPacket
INFO: Message from myusername@gmail.com/gmail.071FDF03 : !help
Jan 6, 2011 3:50:07 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: !help2bV2J16--oUGBdNgHWTTcPpukuo
Jan 6, 2011 3:50:07 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: Working: 2 out of 30 executors are busy.1away
Jan 6, 2011 3:50:07 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: Working: 2 out of 30 executors are busy.1away
Jan 6, 2011 3:50:07 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT: Working: 2 out of 30 executors are busy.1away
Jan 6, 2011 3:49:38 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Jan 6, 2011 3:49:08 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Jan 6, 2011 3:48:12 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: Working: 1 out of 30 executors are busy.1away
Jan 6, 2011 3:48:12 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: Working: 1 out of 30 executors are busy.1away
Jan 6, 2011 3:48:12 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT: Working: 1 out of 30 executors are busy.1away
Jan 6, 2011 3:47:48 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT: status of all projects:
You are using 2 different clients to connect to jabber.org and talk to the bot?
If you're using googletalk clients, maybe this is related to JENKINS-5345.
Can you specify which bot commands where issued in which order from which clients? Otherwise it's difficult to read the log.
Is this the complete log - I would expect more output after "FINE: SENT: status of all projects:" (are there any projects?)
I am having the same issue.
Environment: Hudson 1.394 on Mac OS X 10.6 Snow Leopard, with Hudson instant-messaging plugin 1.13, and Hudson Jabber notifier plugin 1.13.
After a restart, the first command will succeed and the second command gets nothing but silence.
I usually use Google Talk through Digsby, although if I open Gmail.com and chat from there, that seems to open another "session" and I can get one command to succeed in that session as well.
Jabber plugin is configured to connect to talk.google.com and has the Enable SASL authentication checkbox unchecked. The Hudson Jabber ID is a Gmail account.
Here are some log snippets - I will indicate the breaks where I send the command in Digsby. After that, the logs are displayed in the normal most-recent-on-top format:
-----> Me: !botsnack tacos
-----> Received: thanks a lot! om nom nom. I really like that tacos
Jan 28, 2011 2:02:25 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT: Yawn, I'm so bored. Don't you have some work for me?1
Jan 28, 2011 2:02:21 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT: david.boike: thanks a lot! om nom nom. I really like that tacose2g7c0
Jan 28, 2011 2:02:21 PM hudson.plugins.jabber.im.transport.JabberIMConnection$PrivateChatListener processPacket
INFO: Message from my-email-removed@gmail.com/Digsby7026FB6B : !botsnack tacos
Jan 28, 2011 2:02:21 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: !botsnack tacos!botsnack tacos
Jan 28, 2011 2:02:21 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV:
Jan 28, 2011 2:02:21 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: !botsnack tacos!botsnack tacos
-----> Me: !botsnack burritos
Jan 28, 2011 2:04:33 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Jan 28, 2011 2:04:23 PM hudson.plugins.jabber.im.transport.JabberIMConnection$PrivateChatListener processPacket
INFO: Message from my-email-removed@gmail.com/Digsby7026FB6B : !botsnack burritos
Jan 28, 2011 2:04:23 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINEST: RCV PKT: !botsnack burritos!botsnack burritos
Jan 28, 2011 2:04:23 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV:
Jan 28, 2011 2:04:23 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: RECV: !botsnack burritos!botsnack burritos
Jan 28, 2011 2:04:03 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Jan 28, 2011 2:03:33 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Jan 28, 2011 2:03:03 PM hudson.plugins.jabber.im.transport.JabberConnectionDebugger
FINE: SENT:
Please try the plugins attached to JENKINS-7060. They use a new, beta version of the Smack library which should fix a lot of bugs.
FYI: The new beta plugins seem to have resolved this particular issue for us on Win32/Tomcat 6.0.30/Jenkins 1.397
Thank you very much!
Code changed in jenkins
User: kutzi
Path:
pom.xml
src/main/java/hudson/plugins/jabber/im/transport/JabberConnectionDebugger.java
http://jenkins-ci.org/commit/jabber-plugin/242722157b444737390857d5c341e590ae655804
Log:
Upgrade Smack library to 3.2.0. Fixes JENKINS-7060, JENKINS-8426 and JENKINS-5345
Code changed in jenkins
User: kutzi
Path:
pom.xml
src/main/java/hudson/plugins/jabber/im/transport/JabberConnectionDebugger.java
http://jenkins-ci.org/commit/jabber-plugin/242722157b444737390857d5c341e590ae655804
Log:
Upgrade Smack library to 3.2.0. Fixes JENKINS-7060, JENKINS-8426 and JENKINS-5345
I've never heard of anything like this before. By "server log" you mean the log of jabber.org? Are there no other log entries in Hudson's log?
My best guess wouzld be the jabber.org log (is there any way to access it?). There should be hopefully why the messages are not forwarded to the Jabber bot OR why the answers from the jabber bot are not reaching your clients.