[
http://jira.nuxeo.org/browse/NXP-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florent Guillaume updated NXP-3505:
-----------------------------------
Description:
When using JCA, it is the case currently that when you open a connection from a
repository, all the other connections are in "standby" and cannot be used until
the newer connection has been closed. This imposes a "nested" mode of access to
the connections which is painful.
It is actually allowed by the JCA spec (JCA 1.5 §6.5.4.2) to support concurrent
access to a ManagedConnection instance from multiple connection handles.
This would allow several different connections (CoreSessions for the
application) to coexist without crashing.
Note as well that because the datasource has <track-connection-by-tx/>, then in
a single transaction all Connections requested from the same repository
(ConnectionFactory) will be based on the same ManagedConnection, so will share
their data.
was:
When using JCA, it is the case currently that when you open a connection from a
repository, all the other connections are in "standby" and cannot be used until
the newer connection has been closed. This imposes a "nested" mode of access to
the connections which is painful.
It is actually allowed by the JCA spec (JCA 1.5 §6.5.4.2) to support concurrent
access to a ManagedConnection instance from multiple connection handles.
> SQL Storage: allow JCA connection sharing to support concurrent access
> ----------------------------------------------------------------------
>
> Key: NXP-3505
> URL: http://jira.nuxeo.org/browse/NXP-3505
> Project: Nuxeo Enterprise Platform
> Issue Type: Improvement
> Components: Core SQL Storage
> Affects Versions: 5.2 M1
> Reporter: Florent Guillaume
> Assignee: Florent Guillaume
> Fix For: 5.2 GA
>
>
> When using JCA, it is the case currently that when you open a connection from
> a repository, all the other connections are in "standby" and cannot be used
> until the newer connection has been closed. This imposes a "nested" mode of
> access to the connections which is painful.
> It is actually allowed by the JCA spec (JCA 1.5 §6.5.4.2) to support
> concurrent access to a ManagedConnection instance from multiple connection
> handles.
> This would allow several different connections (CoreSessions for the
> application) to coexist without crashing.
> Note as well that because the datasource has <track-connection-by-tx/>, then
> in a single transaction all Connections requested from the same repository
> (ConnectionFactory) will be based on the same ManagedConnection, so will
> share their data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
