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

Chat not working. Please help. #24

Open
brunosimioni opened this issue Jul 25, 2014 · 0 comments
Open

Chat not working. Please help. #24

brunosimioni opened this issue Jul 25, 2014 · 0 comments

Comments

@brunosimioni
Copy link

Scenario:

  • eXo: platform-community-4.0.6
  • users: LDAP readonly repo, with only users synced. sync job active for new ldap users.
  • chat: running in two servers mode: 1 in tomcat 7.0.54 version (chatServer.war - standalone) and eXo as second one.
  • maven: chat build with maven procedure.
  • host: both are places in different ports, with apache anti phising trick done (and successully working).
  • JAVA_HOME and JRE_HOME both pointing to a openjdk-1.7 installation.

After the login screen, I just got in Chrome console a request error:

http://central.ampliato.com.br:10700/chatServer/notification?user=root&token=979412bd16bee4627624db838ee489f289d27000

returning 404 HTTP status and "Petit malin !" text.

Entering in chat "open chat" dropdown menu option (topmost bar), I got a black screen "Service Not Available. Please, come back later.", with several requests to (again in Chrome console):

http://central.ampliato.com.br:10700/chatServer/whoIsOnline?user=root&token=979412bd16bee4627624db838ee489f289d27000&filter=&isAdmin=false&timestamp=1406328682562

With the same 404 HTTP status and the same text.

Both eXo and Tomcat console has no errors messages during this requests.

Tomcat Chat Server Log: http://pastebin.mozilla.org/5622869
eXo community Tomcat Log: http://pastebin.mozilla.org/5622912
httpd log: http://pastebin.mozilla.org/5622921
httpd.conf http://pastebin.mozilla.org/5622932
chat.properties http://pastebin.mozilla.org/5622933 (mongodb is listening in 10717 port)

Some questions:

  1. Why isn't this working?
  2. Is there any trick to get it working with LDAP users?
  3. I was using a self-signed certified and just get a lot of different errors with HttpClient requests in chat application. We can try to fix this second problem in another moment, but I was forced to remove my certificate to analyse these first-one problems.

Some considerations:

  1. I entered in "chat" database, "users" collection in mongodb, manually, and it is empty. It looks like the "register user" procedure is not working, since they are different entries (a user in eXo and a user in chat mongodb)
  2. I tried to search in github the addUser method, but I could not understand who the "enter eXo user" event is chained to chat portlet. I guess that there is a problem around this. Maybe wrong.
  3. There is some blind points in your documentation. May I update your wiki pages?
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

1 participant