[jboss-jira] [JBoss JIRA] (WFLY-3136) SRV 7.7.2 non-compliance

Paul Ferraro (JIRA) issues at jboss.org
Tue Mar 18 18:32:10 EDT 2014


     [ https://issues.jboss.org/browse/WFLY-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated WFLY-3136:
-------------------------------

    Description: 
>From SRV 7.7.2: Distributed Environments
Within an application marked as distributable, all requests that are part of a session must be handled by one JVM at a time.

Our default configuration for the Infinispan cache used for web sessions uses PESSIMISTIC locking.  However, Infinispan only acquires locks on cache write operations.  This only prevents concurrent writes to a session.  We need to make sure both reads and writes to a session use cluster exclusive access, by default at least.

  was:
>From SRV 7.7.2: Distributed Environments
Within an application marked as distributable, all requests that are part of a session must be handled by one JVM at a time.

Our default configuration using PESSIMISTIC locking.  However, Infinispan only acquires locks on cache write operations.  This only prevents concurrent writes to a session.  We need to make sure both reads and writes to a session use cluster exclusive access, by default at least.


    
> SRV 7.7.2 non-compliance
> ------------------------
>
>                 Key: WFLY-3136
>                 URL: https://issues.jboss.org/browse/WFLY-3136
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 8.0.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 8.0.1.Final
>
>
> From SRV 7.7.2: Distributed Environments
> Within an application marked as distributable, all requests that are part of a session must be handled by one JVM at a time.
> Our default configuration for the Infinispan cache used for web sessions uses PESSIMISTIC locking.  However, Infinispan only acquires locks on cache write operations.  This only prevents concurrent writes to a session.  We need to make sure both reads and writes to a session use cluster exclusive access, by default at least.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list