[jboss-jira] [JBoss JIRA] Updated: (JBAS-6587) Unnecessary Locking in WrappedConnection and WrappedPreparedStatement

[Jesper Pedersen (JIRA)]

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

Jesper Pedersen updated JBAS-6587:
----------------------------------

    Priority: Minor  (was: Major)


> Unnecessary Locking in WrappedConnection and WrappedPreparedStatement
> ---------------------------------------------------------------------
>
>                 Key: JBAS-6587
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6587
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>         Environment: Windows 
> Sun JDK 1.6
>            Reporter: Deyan Bektchiev
>            Assignee: Jesper Pedersen
>            Priority: Minor
>
> The JBoss JDBC Connection and PreparedStatement wrapper classes all acquire and release a lock when entering and exiting most of their methods.
> JDBC connections are not supposed to be thread safe and even if you coded your wrapper this way there is no guarantee that the underlying Connection would behave properly if accessed by multiple threads concurrently.
> In one particular use case when profiling obtaining the locks for Statements (that obtain the Connection locks) took 5% of the total time.
> I can provide a YourKit CPU profiler snapshot.
> Regards,
> Deyan

-- 
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