You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jeanne Waldman (JIRA)" <de...@myfaces.apache.org> on 2009/05/30 03:55:07 UTC

[jira] Commented: (TRINIDAD-1078) Application View Cache is broken

    [ https://issues.apache.org/jira/browse/TRINIDAD-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714648#action_12714648 ] 

Jeanne Waldman commented on TRINIDAD-1078:
------------------------------------------

I created JIRA Issue TRINIDAD-1492 to log an error if USE_APPLICATION_VIEW_CACHE is true. If it gets fixed, this error can be deleted.

(Also see JIRA Issue TRINIDAD-1487 Improve the application view cache)

> Application View Cache is broken 
> ---------------------------------
>
>                 Key: TRINIDAD-1078
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1078
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.7-core
>         Environment: Jdeveloper 10g,
> OC4J 10g,
> MyFaces 1.1.5,
> JSF 1.1
>            Reporter: Mark Robinson
>
> The application view cache is broken.  When multiple users are using a site with it enabled and they both execute a query at the same time the environment will allow data from user A's session into user B's session.  This likely made it into production because it's a race condition bug rather than a functional bug.
> Execution example:
> User A and user B execute a function at the same time which modifies a display table of theirs.
> Back-end function runs and updates the DB as expected
> User A gets the result they expect(correct rows in the table)
> User B also gets the result user A is seeing.
> Resolution:
> Disable Application View cache in web.xml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.