[
https://issues.apache.org/jira/browse/FLINK-23437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394049#comment-17394049
]
Roman Khachatryan commented on FLINK-23437:
-------------------------------------------
The option added and merged into master as
0b4d17e7894fa0f3624f182e2222edff447cf5a8 and into 1.13 as
898419ebedc0a4c8005347c848e2b004187d0672.
Let's track the remaining issues with pooling in FLINK-22889.
I'm going to rename and resolve this ticket.
> Connection leak in XaFacadePoolingImpl
> --------------------------------------
>
> Key: FLINK-23437
> URL: https://issues.apache.org/jira/browse/FLINK-23437
> Project: Flink
> Issue Type: Bug
> Components: Connectors / JDBC
> Affects Versions: 1.13.1
> Reporter: Maciej Bryński
> Priority: Major
> Labels: pull-request-available
>
> Hi,
> I'm using JDBC XA connector to put data into Oracle database.
> I'm facing issue with too many concurrent connection to database.
> I changed this method to return XaFacadeImpl instead of XaFacadePoolingImpl
> and problem was solved.
> {code:java}
> static XaFacade fromXaDataSourceSupplier(
> Supplier<XADataSource> dataSourceSupplier, Integer timeoutSec) {
> return new XaFacadePoolingImpl(() -> new XaFacadeImpl(dataSourceSupplier,
> timeoutSec));
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
