+

Database Connector Release Notes - Mule 4

Support Category: Select

Anypoint Connector for Database (Database Connector) enables you to connect to relational databases through the JDBC API.

1.13.8

October 4, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

The XA Bitronix configuration pool no longer throws DB:QUERY_EXECUTION when the Store procedure operation has an output parameter.

W-11743085

The Store procedure operation no longer returns an issue with a CLOB output while using a local transaction.

W-11721963

The warn message at attempting to override property no longer have the braces with number ({0}.{1}..) displayed.

W-11755478

The MuleRuntimeException shown during resolving query will show the stack trace now.

W-11762357

1.13.7

September 12, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Memory leaks no longer occur in transaction operations when using LOBs fields.

W-11582039

The XA Bitronix configuration pool no longer throws the createArray or createStruct unsupported exceptions when the Store procedure operation has an array as a parameter.

W-11425936

1.13.6

August 3, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

The DataWeave mapping input issue to a CLOB in the Insert operation no longer occurs.

W-11524839

1.13.5

July 11, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Using the Select operation with CLOB output no longer causes a connection leak.

W-11259976

1.13.4

June 6, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

When using stored procedures, connections no longer leak. Connections are now released at the end of the flow and when consuming CLOBs as an output parameter.

W-11098541

1.13.3

May 26, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Database Connector no longer needs Oracle’s UDT scheme appended on the type name when you define the scheme on the connector’s global configuration Column types field or in the Parameter types section of the Stored procedure operation. Now, the connector searches the type name correctly.

W-11002486

1.13.2

May 12, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Database Connector did not log enough information when the Connection Factory caught an exception during the connection creation. Now, the connector logs the proper stack trace with the error level.

W-10718271

Database Connector no longer throws a java.lang.OutOfMemoryError: Java heap space error when using the Insert operation to work with large CLOB files.

W-10911002

1.13.1

April 25, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

The output of prepareArray and prepareStruct functions are now properly converted into the actual JDBC objects. Also, when calling store procedures, the correct parameter type is inferred, which avoids breaking the creation of structs and arrays.

W-10673234

1.13.0

April 11, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

To fix concurrency issues that occur when using the createArray and createStruct functions, Mule introduces the prepareStruct and prepareArray functions to use instead. These new functions enable Database Connector to defer JDBC values creation until the correct SQL connection is available. The createArray and createStruct functions continue to work as previously. Replace them manually in your code with the new functions.

W-10673234

1.12.1

February 21, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Database Connector now supports the consumption of LOBs for the IBM’s DB2.

W-10673315

1.12.0

February 4, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Support Oracle features even if the database connection is provided as a Spring bean reference to a DataSource or as a Generic Connection.

DBCON-329

Access Oracle’s proprietary createARRAY() function using a JDBC standard method to increase compatibility with custom connection pool managers.

DBCON-352

Added synchronization while invoking createArray functions to prevent deadlocks that occurred under high concurrency.

DBCLI-15

1.11.3

January 31, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Database Connector now allows brackets in the Stored procedure operation query to support the MSSQL Server.

DBCON-360

Added a warning message when a timeout’s value is rounded up.

DBCON-318

1.11.2

January 07, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Reversed a dependency in Database Connector versions 1.11.0 and 1.11.1 that prevented the deployment of apps.

DBCON-350

1.11.1

January 05, 2022

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Reversed a change in the Database Connector version 1.11.0 API that prevented the deployment of apps.

DBCLI-25

1.11.0

December 22, 2021

What’s New

TLS support feature for Oracle’s connection provider.

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

The Database Connector Select operation closed the connection at the end of the flow when its result contained a LOB stream. Now the consumption of the LOB streams is tracked, and the connection is closed when there are no more LOB streams to consume or at the end of the flow.

DBCON-304

Timeouts are now rounded up to whole seconds. Because timeouts are set in seconds (JDBC API), the connector rounds up values smaller than a second to avoid waiting indefinitely.

DBCON-318

When using JDBC’s REF_CURSOR type as a stored procedure out parameter, the error unsupported network datatype or representation was thrown. Now the type is handled correctly.

DBCON-319

1.10.6

November 10, 2021

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Inserting data into an Oracle database returned an Invalid Column Type error. The variable used as input parameter should be of MIME type text/plain.

DBCON-311

1.10.5

October 27, 2021

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

Large NVarchar payloads failed with jTDS driver (MSSQL).

DBCLI-10

1.10.4

August 20, 2021

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

Issue ID

ResultSets with active LobStreams are forcibly closed at the end of a flow.

DBCLI-12

Changed the record level to WARN when unable to determine if there are more records in the ResultSets.

DBCLI-14

1.10.3

July 28, 2021

Compatibility

Software Version

Mule

4.1.1 and later

Anypoint Studio

7.3 and later

OpenJDK

8 and 11

Fixed Issues

  • Database Connector threw an incorrect QueryExecutionException exception when the SQLException thrown by the driver didn’t have an SQLState nor a message related to the connection. Therefore, the reconnection strategy was not triggered. The correct throw message is DB:CONNECTIVITY. (DBCLI-11)

1.10.2

July 19, 2021

Fixed Issues

  • Database Connector threw an Invalid column type message when using Oracle’s XMLTYPE as input for the Stored Procedure operation. The connector now manages the correct type. (DBCON-278)

  • Database Connector threw an incorrect TransactionException exception when the connection was lost during an XA transaction. Therefore, the reconnection strategy was not triggered. The correct throw message is DB:CONNECTIVITY. (DBCLI-7)

  • The Database Connector Stored Procedure operation incorrectly executed database functions with an IN OUT parameter. Now, the operation performs correctly. (DBCLI-8)

  • Database Connector did not log enough information when the Connection Factory caught an exception during the connection creation. Now, the connector logs the proper information. (DBCLI-9)

1.10.1

July 05, 2021

Fixed Issues

  • Database Connector exported incorrect packages, now the connector exports the correct packages. (DBCON-283, DBCON-286)

1.10.0

June 04, 2021

Features

Added new options for Pooling profile configuration:

  • The Test connection on checkout field enables you to disable connection testing on checkout in order to improve the connector’s performance.

  • The Max statement field enables you to define the total number of PreparedStatements a DataSource will cache.

1.9.4

June 01, 2021

Fixed Issues

  • Database Connector logged an exception at ERROR level causing a large amount of content to be saved in the log registry. Now the connector uses the correct log level, DEBUG. (DBCLI-5)

1.9.3

April 05, 2021

Fixed Issues

  • When using the Insert operation, Database Connector didn’t correctly resolve the NCLOB types, which resulted in a DB:QUERY_EXECUTION error with an Invalid column type message. (DBCON-265)

1.9.2

March 22, 2021

Fixed Issues

  • Database Connector threw an incorrect NoSuchElementException Java exception for a connection reset while iterating a result, and produced a noncatch by the try catch block. The correct throw message is DB:CONNECTIVITY. (DBCON-253)

  • The Stored Procedure operation threw a MULE:UNKONWN error (with a NullPointerException message) when returning an empty array. (DBCON-255)

  • Database Connector closed the connection after reading the entire ResultSet of a Select operation despite having the LOB stream still open. This behavior prevented the LOB values from being read after the connection closure. (DBCON-256)

1.9.1

November 30, 2020

Fixed Issues

  • Fixed an issue in which the On Table Row operation closed connections once rows were dispatched to the next processor, thus preventing the consumption of streams. (DBCON-234)

1.9.0

November 17, 2020

Minimum Mule Version

Mule 4.1.1

Features

  • Introduced the Query single operation that enables you to select a single record from a database and access the result without any additional transformations to the payload. This operation doesn’t use streaming.

1.8.3

September 30, 2020

Fixed Issues

  • Fixed an issue in which stored procedures were not closing connections when no stream was returned, nor any transaction performed. (DBCON-225)

  • When the Bulk insert operation used debug output, it logged a placeholder instead of the record number. (DBCON-228)

1.8.2

August 12, 2020

Fixed Issues

  • Fixed "Struct cannot be cast to [Ljava.lang.Object" issue that prevented the connector to create SQL Arrays or Structs containing BLOBs or CLOBs types. (DBCON-190)

1.8.1

June 1, 2020

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

  • Fixed issue where connections were not closed if a stored procedure returned multiple result sets. (DBCON-182)

  • Fixed issue where dbCreateStruct performance introduced a regression since Mule 3.9.4. (DBCON-178)

1.8.0

April 24, 2020

Minimum Mule Version

Mule 4.1.1

Features

Database Connector now accepts SQL Casting PostgreSQL and Snowflake syntax’s, through the double colon (::) expression. For example, SELECT MAX(modified_date)::DATE FROM sales, where modified_date is of type string. This feature does not change the existing behavior for the connector (MULE-18150).

Fixed Issues

  • MySQL driver now logs to the Mule Log when using MySQL Driver 8.x and higher (MULE-18287).

  • Fixed issue that prevented the usage of the BulkInsert Operation within a ForEach scope (MULE-18260).

  • Fixed issue that prevented the logging of information about a BulkUpdate Operation when an Exception was thrown by it (MULE-18290).

1.7.0

March 13, 2020

Minimum Mule Version

Mule 4.1.1

Features

You can now specify additional pooling profile properties using the additional-properties tab for any Database provider. This feature allows you to specify only additional properties and not to override the main ones (like maxPoolSize) if they were already specified.

Fixed Issues

Fixed issue where oracle DB connector was unable to use specific pooling profile configurations (such as checkoutTimeout or idleConnectionTestPeriod). (MULE-17949) Fixed issue where first stored procedure calls to database took a long time. (MULE-17808) Fixed issue where operation stored-procedure did not offer the parameter to configure repeatable streaming. (MULE-17898)

1.6.2

January 9, 2020

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

The infinite loop when using stored procedure with H2 Database issue is fixed. (MULE-17793)

1.6.1

January 7, 2020

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

  • The issue where connection leaks occurred when using dynamic configurations is fixed. (MULE-17792)

  • The issue where using stored procedures with a CLOB In Out parameter failed to execute on Oracle is fixed. (MULE-17846)

1.6.0

October 11, 2019

Minimum Mule Version

Mule 4.1.1

Features

You can now reference the name of a package of stored procedures on Oracle. (MULE-17418)

Fixed Issues

Pooled DB connections maxIdleTime default 0 causes connections to remain open. (MULE-17601)

1.5.5

September 24, 2019

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

  • Stored procedures took too long to execute with the Oracle Database. (MULE-17394)

  • Unable to retrieve responses with custom data types. (MULE-17470)

  • Unable to execute stored procedures defined within packages on an Oracle Database. (MULE-17418)

1.5.4

June 6, 2019

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

  • On stored procedures where the output return variable is set to null, the output should not be processed further. (MULE-16961)

  • db:select operation fails to throw a connectivity error. (MULE-16950)

1.5.3

May 7, 2019

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

  • Connector doesn’t ensure data is consumable by DataWeave if it has an encoding different from the one used by the runtime. (MULE-16460)

  • Clob in out parameters are not made consumable with Oracle DB. (MULE-16770)

1.5.2

April 16, 2019

Minimum Mule Version

Mule 4.1.1

Features

Add connector icon.

Fixed Issues

  • Errors while transforming to JSON the output of Oracle SP call with custom types. (MULE-16589)

  • Can’t get parameter data types when store procedure name includes schema. (MULE-16685)

  • FlowListener callback retains too much state. (MULE-16366)

  • Errors when using Oracle’s UDT Table type. (MULE-16401)

  • Database connector not sending value of the IN-OUT parameter. (MULE-16484)

  • "Unable to convert between" error when using SP in MsSql. (MULE-16339)

1.5.0

December 28, 2018

Minimum Mule Version

Mule 4.1.1

Features

The connector now supports the usage of Struct and Array types out of the box.

Fixed Issues

DB Connector doesn’t work OOTB with Struct and Array types. (MULE-16074)

1.4.3

December 11, 2018

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

Database connector not releasing connections. (MULE-16072)

1.4.2

October 18, 2018

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

Queries get cached without any TTL or limit, which causes memory to grow. (MULE-15869)

1.4.1

October 16, 2018

Minimum Mule Version

Mule 4.1.1

Features

None

Fixed Issues

  • Can’t get stored procedure name from SQL query when there is whitespace before parentheses. (MULE-15793)

  • MySQL default driver causes a memory leak. (MULE-15748)

  • Database On Table Row should hint available columns for ID and Watermark using Value Providers. (MULE-15644)

1.4.0

August 7, 2018

Minimum Mule Version

Mule 4.1.0

Features

  • Now in Generic Connections, the username and password can be configured outside the JDBC URL for improved security and support for multitenancy.

  • Improved New Row trigger, now hints with the available tables to retrieve rows.

  • Support for PostgreSQL type casting.

Fixed Issues

  • Database On New Row listener should provide a hint to available tables. (MULE-15310)

  • Database Connector uses deprecated DriverClass when using new MySQL Drivers. (MULE-15218)

  • Database Connector doesn’t support PostgreSQL type casting. (MULE-15101)

1.3.4

June 29, 2018

Minimum Mule Version

Mule 4.1.0

Features

  • Fixed issue that prevented inserting and updating CLOB types in Oracle Databases.

  • When using the newest MySQL Driver, the connector uses the new preferred Driver Class instead of the old deprecated one.

  • Fixed issue when consuming CLOB and BLOB types when using Derby databases.

Fixed Issues

  • Database Connector should automatically transform CLOB types on Oracle Databases. (MULE-15240)

  • Database Connector uses deprecated DriverClass when using new MySQL Drivers. (MULE-15218)

1.3.3

May 21, 2018

Minimum Mule Version

Mule 4.1.0

Features

Fixed issue that makes the connector log the JDBC URL.

Fixed Issues

Database connector logs passwords. (MULE-15047)

1.3.2

May 7, 2018

Minimum Mule Version

Mule 4.1.0

Features

Minor internal changes.

Fixed Issues

  • SQL Server Connection provider doesn’t communicate the library RegEx. (MULE-14876)

  • Upgrade c3p0 to Mule fork version. (MULE-14859)

1.3.1

March 16, 2018

Minimum Mule Version

Mule 4.1.0

Features

This release includes the following enhancements, changes, and fixes:

  • Now the Oracle Connection can be configured with a Service Name.

  • When doing a Select now the output metadata communicates correctly if the columns values can be have a null value or not.

  • In some scenarios when an error occurs the connection string with embedded credentials could be logged.

Fixed Issues

  • Connectors doesn’t communicate correctly if their POJOs properties are nullable or not. (MULE-14701)

  • Credentials leak in error messages. (MULE-14740)

  • Add the capability of configuring the Service Name for an Oracle Connection. (MULE-14750)

1.3.0

March 2, 2018

Minimum Mule Version

Mule 4.1.0

Features

This release includes the following enhancements, changes, and fixes:

  • Added a new message source which triggers a flow per each row in a table.

  • When doing a SELECT over a CLOB column the value is retrieved as a InputStream.

Upgrade Requirements

Mule 4.1

Fixed Issues

  • Create Trigger for Database. (MULE-14657)

  • DB Connector returns ClLOB objects instead of InputStreams. (MULE-14615)

1.2.0

January 19, 2018

Minimum Mule Version

Mule 4.0.0

Features

This release includes the following enhancements, changes, and fixes:

  • Added out-of-the-box support for connecting to Microsoft SQL Server Databases.

  • Improved support for Derby sub-protocols.

  • Improved UX.

Fixed Issues

  • ColumnTypes parameter should be placed on Advanced Tab. (MULE-14515)

  • Add Value Providers for SubSubProtocols in Derby Connection Provider. (MULE-13921)

Was this article helpful? Thanks for your feedback!