On 5/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
This seems to have worked.  I went into StateManagerImpl and changed the
TokenCache size from 15 to 60 and the problem went away.  Perhaps the
problem will reappear if I enter 4 times as many items but we are unlikely
to encounter that situation in a production environment.

There's a config flag for that;  you don't need to change any code.
Of course, the downside to increasing the size of the cache is
memory usage.  This would have a negative impact on scalability
(though, as with any question of scalability, "how much" is difficult
to answer without measuring in your specific app.)

I wonder if it would be possible to back up the TokenCache in
LaunchListener and then restore it in the submit action?  Perhaps dialogs
should have their own cache seperate from the main body of the
application?

Perhaps.  Another possibility - since this is an LRU cache - is that every
time a dialog saves some state, we "touch" the state of the parent page
to keep it from getting flushed.

-- Adam

>> Hrm, it might be an issue where the TokenCache has expunged
>> some necessary bit of state - it's an LRU cache, by default of size 15,
>> so perhaps after 15 requests, the parent page is gone?  Just a theory.
>>
>> -- Adam
>>
>>
>> On 5/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>> I'm having a problem with ADF dialogs in EA19 and I was wondering if
>>> anyone has seen this problem before, has any suggestions, if it had
>>> been
>>> fixed, etc.   If noone has seen this I'm going to go digging in the
>>> DialogService source for an answer but if it's been fixed that will of
>>> course be a wild goose chase.
>>>
>>> The issue:  When I call a dialog there are certain circumstances where
>>> my
>>> returnListener never gets called.  It seems to be related to the amount
>>> of
>>> partial submit activity on the dialog.
>>> AdfFacesContext.getCurrentInstance().returnFromDialog is always called
>>> on
>>> a full submit.  I can replicate the problem every time but I can't
>>> determine what's getting lost/changed.
>>>
>>> Thanks for any help,
>>> Brady
>>>
>>>
>>
>
>



Reply via email to