Hello, It seems linked to the new PPR code, but your specific problem sounds new to me so please log a JIRA issue.
Thanks, ~ Simon On Dec 15, 2007 12:02 PM, Harald Stangl <[EMAIL PROTECTED]> wrote: > Ok, I tried the newest version of Tomcat (6.0.14) which reduced the > number of ClientAbortExceptions, although they still occur. > The problem still persists that after closing a dialog, the link for > opening it up again is not clickable for about 10 seconds (meaning > nothing happens when you click on it). > > Oh, and for Opera, dialogs won't work at all. After clicking on a link > that should launch a dialog, Opera seems to hang in a loop, reloading > the base page over and over again. > > So, anyone here who can provide me with some help? A developer who can > tell me what changes have been made to the dialog framework between > 1.2.2 and 1.2.3? > Also, should I file this as a bug? > > Harald. > > Harald Stangl schrieb: > > Hello, > > > > we're developing a browser game using JSF 1.2_04 (Sun RI) and Trinidad. > > > > Until now we are using Trinidad 1.2.2 where the lightweight dialogs > > work fine for both Internet Explorer and Firefox. > > > > But when we switched to Trinidad 1.2.4, the lightweight dialogs no > > longer worked reliably in Firefox. When clicking on a link that should > > launch a dialog often nothing happens at all, and sometimes the > > following Exception is thrown: > > ClientAbortException: java.net.SocketException: Software caused > > connection abort: socket write error > > > > When trying to spot the error, I made a peculiar observation: > > I included a Phase Listener for the RestoreViewPhase (although the > > phase is irrelevant in this case) that does nothing but gives me the > > possibility to set a break point. With Trinidad 1.2.2, the phase > > listener is called twice sequentially from the same thread upon the > > call of the dialog. I assume the first call is for the processing of > > the base page and the second one for the dialog page. > > > > But starting with Trinidad 1.2.3, the phase listener is called *four* > > times, where the two first calls occur sequentially as before, and the > > third and forth call happen in two different threads in parallel. This > > behaviour is special to Firefox; opening the dialog with Internet > > Explorer, only two sequential calls as with Trinidad 1.2.2 are being > > executed. > > > > I created a very simple test setup consisting of only two nearly empty > > pages (the base page and the dialog page), and a backing bean that > > handles the closing of the dialog when the "close" link in the dialog > > page is clicked. I also disabled any other filters or listeners to > > eliminate potential error sources. If there is any interest, I will be > > glad to post my demo files. Any help to solve this problem is > > appreciated. > > > > Thanks, > > Harald. > > > >
