[jboss-jira] [JBoss JIRA] (WFLY-2699) liferay portal does not work
Michał Zegan (JIRA)
issues at jboss.org
Tue Dec 31 12:05:32 EST 2013
[ https://issues.jboss.org/browse/WFLY-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933314#comment-12933314 ]
Michał Zegan commented on WFLY-2699:
------------------------------------
It seems that it only happens when a browser requests compression.
If it doesn't, it works. if it does, then the backend after receiving a request immediately closes the connection with such an exception:
18:02:41,484 ERROR [io.undertow.request] (default task-9) Blocking reques
t failed HttpServerExchange{ GET /index.jsp}: java.lang.RuntimeException:
io.undertow.server.TruncatedResponseException
at io.undertow.servlet.spec.HttpServletResponseImpl.responseDone(
HttpServletResponseImpl.java:532)
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirst
Request(ServletInitialHandler.java:287)
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchReq
uest(ServletInitialHandler.java:227)
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(
ServletInitialHandler.java:73)
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleReq
uest(ServletInitialHandler.java:146)
...
It happens only on liferay. it may be caused by some filter running on it.
> 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
More information about the jboss-jira
mailing list