You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Thomas Andraschko (JIRA)" <de...@myfaces.apache.org> on 2018/03/19 10:18:00 UTC
[jira] [Commented] (MYFACES-4200) Issues with JSF 2.3 resource
pushing using PushBuilder
[ https://issues.apache.org/jira/browse/MYFACES-4200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404587#comment-16404587 ]
Thomas Andraschko commented on MYFACES-4200:
--------------------------------------------
Got notified that it's fixed by tomcat: [https://github.com/javaserverfaces/mojarra/issues/4329#issuecomment-374162481]
Will close it for now.
> Issues with JSF 2.3 resource pushing using PushBuilder
> ------------------------------------------------------
>
> Key: MYFACES-4200
> URL: https://issues.apache.org/jira/browse/MYFACES-4200
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.3.0
> Environment: Apache Tomcat 9.0.4/9.0.5
> JDK 1.8.0.152
> Windows 8
> MyFaces-2.3.0-SNAPSHOT
> Reporter: Holger Sunke
> Priority: Major
>
> When Servlet 4 PushBuilder is used with complex web applications requiring many resources (e.g. Primefaces Showcase), I keep getting plenty of Exceptions with Apache Tomcat 9:
> org.apache.coyote.CloseNowException: Connection [3], Stream [111], This stream is not writable
> caused by HTTPS streams gotten closed due to protocol violations. The final output is not usable most of the times.
> Opening the same application using a HTTP/1.1 connector works fine.
> Resource Push with implemented thru #MYFACES-4141.
>
> A similar issue already exists for JSF 2.3.3 RI Mojarra: https://github.com/javaserverfaces/mojarra/issues/4329
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)