Details

    • Branch Version/s:
      6.1.x
    • Backported to Branch:
      Committed
    • Story Points:
      12
    • Similar Issues:
      Show 4 results 

      Description

      Steps to Reproduce
      Steps to reproduce / testing done:
      Set up was done referencing this wiki: http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/ch-4

      1. Download ejabberd http://www.process-one.net/en/ejabberd/downloads , use the default settings
      1a. Make sure to start your ejabberd server. The installer should create a Start and Stop icon on your Desktop.
      2. Download the Chat Portlet (attached)
      3. Create a portlet-ext.properties (yes that's right, portlet) as such

      ## Jabber ##
      
      jabber.enabled=true
      jabber.import.user.enabled=true
      jabber.host=liferay-xdc49dh
      jabber.port=5222
      jabber.service.name=liferay-xdc49dh
      jabber.resource=Liferay
      jabber.sock5.proxy.enabled=false
      jabber.sock5.proxy.port=-1
      

      4. Place this properties file inside the Chat portlet in WEB-INF/classes
      5. Deploy your chat portlet and startup Liferay
      6. Within Liferay, create another user and sign in with him in another browser
      7. Chat with each other.

      Here is the issue:
      On initial startup, Spark can see that Liferay is online, but Liferay sees 0 friends. At this time, Spark's chats do not go through to Liferay.
      Workaround is to sign into Liferay as the Spark user simultaneously with Spark, then sign out. This "reboots" the connection and then Spark and Liferay can chat. This does not happen when the "jabber.host" is set to an IP address.

        Activity

        Hide
        Christopher Lui added a comment -

        Ejabberd was fairly simple to setup, I downloaded it (http://www.process-one.net/en/ejabberd/downloads) and followed the setup instructions.
        Just use default for everything.

        Then chance jabber.host= and jabber.service.name= to the hostname of your machine.

        Show
        Christopher Lui added a comment - Ejabberd was fairly simple to setup, I downloaded it ( http://www.process-one.net/en/ejabberd/downloads ) and followed the setup instructions. Just use default for everything. Then chance jabber.host= and jabber.service.name= to the hostname of your machine.
        Hide
        Ginson Ren added a comment -

        PASSED Manual Testing using the following steps:

        1. Start Ejabberd server. Add a new user renshen@ginson-ren with password "1234".
        2. Add portlet-ext to chat plugin.
        3. Start tomcat and deploy chat plugin.
        4. Create a new user renshen with password "1234". Add this user to liferay site.
        5. Sign in as test with spark
        6. Sign in as renshen with browser.
        7. Send messages between each other.

        Fixed on:
        Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 8ab18eb354a1540fbd021f8958743980a88ea705.
        Plugins 6.1.x EE GIT ID: ace9e6c847162b655095c2b9b16f26e6f9c8c9cc.
        Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 908fbfec0f183fc699bff2a1af592695ce63535f.
        Plugins 6.2.x EE GIT ID: 540f54d02fe0c71a80d6413eef0a36b0974faf76.

        No matter the "jabber.host" is set to an IP address or a hostname, the chat portlet can resolve.

        Show
        Ginson Ren added a comment - PASSED Manual Testing using the following steps: 1. Start Ejabberd server. Add a new user renshen@ginson-ren with password "1234". 2. Add portlet-ext to chat plugin. 3. Start tomcat and deploy chat plugin. 4. Create a new user renshen with password "1234". Add this user to liferay site. 5. Sign in as test with spark 6. Sign in as renshen with browser. 7. Send messages between each other. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 8ab18eb354a1540fbd021f8958743980a88ea705. Plugins 6.1.x EE GIT ID: ace9e6c847162b655095c2b9b16f26e6f9c8c9cc. Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 908fbfec0f183fc699bff2a1af592695ce63535f. Plugins 6.2.x EE GIT ID: 540f54d02fe0c71a80d6413eef0a36b0974faf76. No matter the "jabber.host" is set to an IP address or a hostname, the chat portlet can resolve.

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Days since last comment:
              1 year, 45 weeks, 3 days ago

              Development

                Structure Helper Panel