dev@javaserverfaces.java.net

Re: Flash scope still broken? (Mojarra 2.3m04)

From: Lenny Primak <lprimak_at_hope.nyc.ny.us>
Date: Sat, 27 Feb 2016 12:25:20 -0600

Alright,
I will try to increase FACELETS_BUFFER_SIZE some more and see if that helps at all or not.

> On Feb 27, 2016, at 7:11 AM, arjan tijms <arjan.tijms_at_gmail.com> wrote:
>
> Hi Lenny,
>
> Thanks for letting us know.
>
> The Flash has always been rather problematic in the past, and the implementation code is particularly problematic.
>
> On top of that, as you might have noticed, the resources dedicated to JSF are not entirely optimal at the moment. Since you cannot reproduce this either, I'm afraid the chances of fixing anything for this are rather slim. I simply wouldn't know where to begin fixing :(
>
> I have to say that I've occasionally seen this error in production too, but that's for an app that's actually using The Flash.
>
> If you may encounter anything in the future that could help us nail this down don't hesitate to post about it again. Thanks!
>
> Kind regards,
> Arjan Tijms
>
>
>
> On Sat, Feb 27, 2016 at 6:41 AM, Lenny Primak <lprimak_at_hope.nyc.ny.us <mailto:lprimak_at_hope.nyc.ny.us>> wrote:
> I am using Mojarra 2.3m04, and Flash scope is still broken.
> I am getting this error:
>
> -----
> JSF1095: The response was already committed by the time we tried to set the outgoing cookie for the flash. Any values stored to the flash will not be available on the next request.
> ——
>
> The weird thing is that I am not even putting anything into flash scope, and there is no flash cookie in the browser.
>
> I put this snippet in web.xml:
> <context-param>
> <param-name>javax.faces.FACELETS_BUFFER_SIZE</param-name>
> <param-value>32768</param-value>
> </context-param>
>
> which solves this problem 99% of the time, but for some large pages, the issue persists.
>
> I have no way to reproduce this as this happens very, very rarely, and only in production
> (yes, I am using 2.3m04 in production and it works great!)
>