Skip to content
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

Publishing to null channel (Publishing to channels: /observer : [object Object]) #12

Open
lolomarx opened this issue Apr 5, 2011 · 7 comments

Comments

@lolomarx
Copy link

lolomarx commented Apr 5, 2011

I use sudo node server.js to start juggernaut,
I can see the juggernaut receive the msg which i send. but it can publish to the channel.
The error msg is below:
Publishing to channels: /observer : [object Object]

@lolomarx
Copy link
Author

lolomarx commented Apr 5, 2011

more details :
5 Apr 12:40:21 - Received: {"channels":["/observer"],"data":{"type":"create","id":"8A3B83FF-78A5-4BCB-BA33-B219D58356AA","klass":"Message","record":{"bo dy":"1111111111111","channel_id":"01DAC934-315B-4FD3-B8DA-D65A55A181FF","created_at":"2011-04-05T04:40:21Z","id":"8A3B83FF-78A5-4BCB-BA33-B219D58356AA", "name":"\u6613\u5f18","updated_at":"2011-04-05T04:40:21Z"}}}
5 Apr 12:40:21 - Publishing to channels: /observer : [object Object]

@lolomarx
Copy link
Author

I use two account to login and talk on same channels but can't get any msg from other. The issues is : i can't see the subscribe message on the juggernaut server side . just see the Publishing to channels: /observer : [object Object] when new message created. I thin they can't get the message due to not do subscription. Any suggestion ? Thx

@lolomarx
Copy link
Author

the test demo url is http://mchat.bugutang.com:9998/ the account is from www.douban.com

@lolomarx
Copy link
Author

I found the reason . The Demo work on firefox 3.6 but not work on firefox 4.0. FF 4.0 can't link with the juggernaut

@ngzax
Copy link

ngzax commented Jun 23, 2011

I am seeing this same issue when setting up Holla + Juggernaut on my internal server here. It worked fine as long as server + clients are all on localhost, but as soon as its a separate server, no one is getting the messages. You have to refresh the browser to see new messages. Errors as follows:

23 Jun 19:41:43 - Serving /application.js - OK
23 Jun 19:41:58 - Received: {"channels":["/observer"],"data":{"type":"create","id":"B1425167-ACFD-458E-A0DD-76F59B07552C","klass":"Message","record":{"body":"from Chrome","channel_id":"438F06F8-7E23-43E9-8C0F-68DFBCF18D75","created_at":"2011-06-23T19:41:58Z","id":"B1425167-ACFD-458E-A0DD-76F59B07552C","name":"Daryl Richter","updated_at":"2011-06-23T19:41:58Z"}}}
23 Jun 19:41:58 - Publishing to channels: /observer : [object Object]

Additionally, I see this error in Safari, which would appear to be related:

Invalid url for WebSocket ws://[object Object]:80/socket.io/websocket
SYNTAX_ERR: DOM Exception 12: An invalid or illegal string was specified. application.js:790

@ngzax
Copy link

ngzax commented Jun 23, 2011

Update on my last comment... that behavior is only seen when using the latest Juggernaut code from Github. When I use a Juggernaut installed by "npm install juggernaut" it works fine.

@olivierlacan
Copy link

Getting the same issue running juggernaut installed from NPM, and running redis, juggernaut & holla on localhost.

If someone connects to my localhost instance of Holla, they can send messages and I will see them appear.
They (remote client) on the other hand don't receive my messages unless they refresh.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants