ICEfaces
  1. ICEfaces
  2. ICE-11053

Push connection not established in Liferay 6.1.2

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Invalid
          • Affects Version/s: EE-3.3.0.GA_P03
          • Fix Version/s: EE-3.3.0.GA_P04
          • Component/s: Bridge, Framework
          • Labels:
            None
          • Environment:
            Liferay 6.1.2 GA3 - Tomcat 7.0.40, Liferay Faces Bridge 3.1.3-GA4

            Description

            When testing the Chat Portlet sample (as well as the code from the Easy Ajax Push tutorial) in Liferay 6.1.2 the blocking connection for ICEpush is not being established. The following warning is seen once the portlet is loaded:

            unknown content in response - application/xml;charset=UTF-8, expected text/xml

            Once this is in the logs, the push connection is not active so none of the updates from other windows/browsers are applied. If the an action happens on the client then these updates are applied.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Arran Mccullough added a comment -

              Attached chat portlet demo to reproduce the issue.

              Steps:

              • Load the Chat portlet in two different browsers.
              • Login with a different username in each browser.
              • Enter in a message and click the send button.
              • The update is not seen in the other browsers until they send a message.
              Show
              Arran Mccullough added a comment - Attached chat portlet demo to reproduce the issue. Steps: Load the Chat portlet in two different browsers. Login with a different username in each browser. Enter in a message and click the send button. The update is not seen in the other browsers until they send a message.
              Hide
              Permalink
              Arran Mccullough added a comment -

              Issue is not reproducible with Liferay 6.2 using the Liferay Faces Bridge 3.2.4

              Show
              Arran Mccullough added a comment - Issue is not reproducible with Liferay 6.2 using the Liferay Faces Bridge 3.2.4
              Hide
              Permalink
              Mircea Toma added a comment - - edited

              Yeah, I cannot reproduce the issue with Liferay Faces Bridge 3.2.5-ga6 libraries that we have in the repository. I don't think we need to support older (/buggy) portlet bridge libraries so I'm marking this issue as invalid.
              Feel free to reopen the issue if there is a valid reason to make things work with Liferay 6.1.2-ga3.

              Show
              Mircea Toma added a comment - - edited Yeah, I cannot reproduce the issue with Liferay Faces Bridge 3.2.5-ga6 libraries that we have in the repository. I don't think we need to support older (/buggy) portlet bridge libraries so I'm marking this issue as invalid. Feel free to reopen the issue if there is a valid reason to make things work with Liferay 6.1.2-ga3.
              Hide
              Permalink
              Mircea Toma added a comment -

              It does not look like we can do anything on the Icefaces side. The resource URL that corresponds to the blocking connection is generated by Liferay but then is not recognized as a resource by Liferay itself. It seems that really the Liferay Bridge needs to be fixed.

              Show
              Mircea Toma added a comment - It does not look like we can do anything on the Icefaces side. The resource URL that corresponds to the blocking connection is generated by Liferay but then is not recognized as a resource by Liferay itself. It seems that really the Liferay Bridge needs to be fixed.
              Hide
              Permalink
              Mircea Toma added a comment -

              It seems that com.liferay.faces.bridge.application.ResourceImpl.getRequestPath method is not constructing a path that later on would be recognized by GenericPortlet as corresponding to a resource.

              Show
              Mircea Toma added a comment - It seems that com.liferay.faces.bridge.application.ResourceImpl.getRequestPath method is not constructing a path that later on would be recognized by GenericPortlet as corresponding to a resource.
              Hide
              Permalink
              Ken Fyten added a comment -

              Please ask the customer to upgrade all of their Liferay Faces jars to 3.1.5-ga6 and see if it is still a problem.

              The GA5 release contains fixes for security vulnerabilities:
              https://web.liferay.com/web/neil.griffin/blog/-/blogs/announcement-patches-for-liferay-faces-ga5

              But upgrading to GA6 would be even better since that also contains the vulnerability fixes but fixes for other defects as well.

              Thanks,
              Neil

              Show
              Ken Fyten added a comment - Please ask the customer to upgrade all of their Liferay Faces jars to 3.1.5-ga6 and see if it is still a problem. The GA5 release contains fixes for security vulnerabilities: https://web.liferay.com/web/neil.griffin/blog/-/blogs/announcement-patches-for-liferay-faces-ga5 But upgrading to GA6 would be even better since that also contains the vulnerability fixes but fixes for other defects as well. Thanks, Neil
              Hide
              Permalink
              Mircea Toma added a comment -

              When testing with Liferay Faces 3.1.5-ga6 jars the issue does not occur anymore.

              Show
              Mircea Toma added a comment - When testing with Liferay Faces 3.1.5-ga6 jars the issue does not occur anymore.
              Hide
              Permalink
              Ken Fyten added a comment -

              Marking Invalid as the resolution to this issue is to update the Liferay Faces Bridge to the specified version.

              Show
              Ken Fyten added a comment - Marking Invalid as the resolution to this issue is to update the Liferay Faces Bridge to the specified version.

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Arran Mccullough
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: