[
https://issues.apache.org/jira/browse/CALCITE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved CALCITE-2003.
---------------------------------
Resolution: Fixed
Fixed in
https://git-wip-us.apache.org/repos/asf?p=calcite-avatica.git;a=commit;h=fcb1342a404a38b14ddefb1f4d81fd2c4c953718
> Avoid global synchronization around openConnection in JdbcMeta
> --------------------------------------------------------------
>
> Key: CALCITE-2003
> URL: https://issues.apache.org/jira/browse/CALCITE-2003
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: avatica-1.11.0
>
>
> Had a report from a user where opening new connections to Avatica were stuck.
> Upon investigation, there was a single thread which had grabbed the local on
> the JdbcMeta instance in {{JdbcMeta#openConnection(ConnectionHandle)}}, but
> was not returning out of the {{DriverManager.getConnection(...)}} call.
> Using the {{ConcurrentMap}} API over the Guava {{Cache}} API gives us enough
> flexibility that we can handle this safely without the total synchronization.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
