-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection went offline and Maximum call stack size exceeded when joining >1000 rooms #282
Comments
I turned on debug and see below in the log
|
We're seeing the same with ~1100 rooms -- I suspect it may be related to rate limiting (https://developer.atlassian.com/hipchat/guide/hipchat-rest-api/api-rate-limits) |
I am seeing the same issue on the latest version of hipchat server 2.1.3. Are you on the hosted version of Hipchat or private server? @fehwalker @ravikiranj |
I ended up opening a ticket with Hipchat support. They were able to look at the logs and realize my issue is that in 2.0.7 and newer server versions XMPP clients are disabled by default. As the Hipchat connector uses the Node JS XMPP Client this is why it started failing after we upgraded. After enabling the XMPP protocol I was able to resolve my issue. Atlassian has also written up a KB article on this issue. https://confluence.atlassian.com/hipchatkb/hubot-stopped-working-on-hipchat-server-v2-0-7-and-later-867181545.html |
@jbrodley Thank you very much for getting to the bottom of this. Yes, we are on custom hosted hipchat server of 2.0 build 1.4.1. I'll check if that article fixes this issue. |
Hi there,
I'm seeing the following errors when hubot tries to join >1000 rooms (@ALL) and I'm not sure how to debug it. I'd appreciate any insight into what's going on. The same setup works if numRooms < 500.
Also, if hubot is the right project for this issue and not hubot-hipchat, I can move it. I created it here since I'm using the hipchat adapter.
Package versions
"hubot": "^2.19.0"
"hubot-hipchat": "^2.12.0-6"
node: 4.4.7
npm: 2.15.8
The text was updated successfully, but these errors were encountered: