[jboss-jira] [JBoss JIRA] (WFLY-2699) liferay portal does not work

[Stuart Douglas (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933583#comment-12933583 ] 

Stuart Douglas commented on WFLY-2699:
--------------------------------------

So looking at the code here:

http://grepcode.com/file/repo1.maven.org/maven2/com.liferay.portal/portal-impl/6.0.6/com/liferay/portal/servlet/filters/gzip/GZipResponse.java#GZipResponse

One possible issue is that setContentLength(long) is not overridden, so if portlet uses this method compression will not work. This seems unlikely though. 

Basically we need to figure out how the content length is being set. Undertow will automatically set a content length header if the output stream is closed without being flushed, and the response fits entirely in the buffer, however I can't see how that would be the cause. 
                
> liferay portal does not work
> ----------------------------
>
>                 Key: WFLY-2699
>                 URL: https://issues.jboss.org/browse/WFLY-2699
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Michał Zegan
>            Assignee: Stuart Douglas
>
> Hello.
> I have commpiled the full wildfly package and set gerrit, jenkins, and the nexus repo manager on it, all works perfectly.
> The problem:
> I tried to deploy liferay on the same instance.
> I did everything and then deployed the webapp.
> The deploy was successful, but it didn't work.
> I have the appserver behind apache reverse proxy, trying to load a page displays error 502 proxy error.
> I checked with telnet what happens by telnetting to the backend appserver and sending a GET request for /.
> The response was incorrect, I got the expected document but without the status line and headers, that makes it clear why apache sait error 502.
> Liferay probably works with jboss as 7 and tomcat/etc, so I think undertow must have something to do with it

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira