[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-752) Create safe mode where session concurrent access is checked

[Tim Fox (JIRA)]

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

Tim Fox updated JBMESSAGING-752:
--------------------------------

    Fix Version/s: 2.1.0.beta
                       (was: 2.0.0 Beta)


> Create safe mode where session concurrent access is checked
> -----------------------------------------------------------
>
>                 Key: JBMESSAGING-752
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-752
>             Project: JBoss Messaging
>          Issue Type: Task
>            Reporter: Tim Fox
>            Assignee: Tim Fox
>            Priority: Minor
>             Fix For: 2.1.0.beta
>
>
> As per JMS spec, a JMS session is supposed to be only accessed from one thread at a time.
> This is so the implementor does not have to synchronize access which might degrade performance.
> However, users are often unaware of this and use the session concurrent by multiple threads, resulting in subtle or hard to identify bugs.
> We should create a "safeMode", where if enabled, concurrent access is checked.
> safeMode should be turned on for development and off for production, so no performance penalty is incurred in production.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira