topic Re: MySQL / MariaDB Connection Pool Issues in Talend Studio

MySQL / MariaDB Connection Pool Issues

_AnonymousUser — Sat, 16 Nov 2024 10:12:45 GMT

Hey all - hoping someone can point me in the right direction here. I've defined a connection pool in the ESB runtime for a MariaDB database (hosted on Amazon RDS, if it matters). The datasource XML that I've defined and deployed in the runtime looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<blueprint xmlns=" http://www.osgi.org/xmlns/blueprint/v1.0.0"
default-activation="lazy">
<bean id="CDHDataSource" class="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource">
<property name="url" value="jdbc:mysql:///?noDatetimeStringSync=true"/>
<property name="user" value="xxxxxxxx"/>
<property name="password" value="xxxxxxxxx"/>
</bean> <bean id="cdh" class="org.apach

To see the whole post, download it here

Re: MySQL / MariaDB Connection Pool Issues

Anonymous — Mon, 12 Dec 2016 07:29:59 GMT

Hi,
Have you already checked document about:TalendHelpCenter:Using datasources and connection pooling in Talend Runtime?
Best regards
Sabrina

Re: MySQL / MariaDB Connection Pool Issues

_AnonymousUser — Mon, 12 Dec 2016 16:09:18 GMT

No, I'm reviewing that document now. Thank you. A couple questions that immediately come to mind, based on what I'm reading there:
- I have multiple database connection pools that I need to create. It's not obvious how I would do that. For example, if I follow the document, I end up with a single MySQL datasource named "ds-mysql". I see how I can edit the configuration for this datasource under container/etc/org.talend.esb.datasource.mysql.cfg. But, how do I create multiple datasources of the same database type?
- I see various connection pool settings in the default org.talend.esb.datasource.mysql.cfg that is created. Where can I find the additional parameters that I can use here?
- The method I have been using to create connection pools was to start with the template provided in the add-ons/datasources/dataservice folder. I've been creating individual datasource connection pool XML files based on the template from here and then deploying them into the container/deploy directory. This "functionally" works, except for the issues I've described here. I don't recall how I landed on going with this method for creating connection pools. What's the use case scenarios for using this method vs what's described in the document you've referenced?

Re: MySQL / MariaDB Connection Pool Issues

_AnonymousUser — Wed, 14 Dec 2016 14:45:50 GMT

Anyone have any thoughts on my followup questions? I can't imagine i'm the only one who uses multiple db connection pools?