search

camunda / camunda-bpm-platform

Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.
https://camunda.com/
Apache License 2.0
4.11k stars 1.55k forks source link

Remove supported environments with 7.19 #2780

Closed ThorbenLindhauer closed 1 year ago

ThorbenLindhauer commented 2 years ago

This issue was imported from JIRA:

Field Value
JIRA Link CAM-14891
Reporter @toco-cam
Has restricted visibility comments false

Acceptance Criteria (Required on creation):

Environments to remove:

Hints (optional):

Links:

Breakdown:

yanavasileva commented 1 year ago

Adjusting the description as Amazon Aurora PostgreSQL 11 hasn't been removed yet. (Maybe was meant for postgresql version 10?)

yanavasileva commented 1 year ago

Changes: Cleaned up CI, test containers. CI execution: commit https://github.com/camunda/camunda-bpm-platform/commit/4bfe05b40dca272a74d6e133587b6a9e4ba7c96f, link; postgresql tests run: https://github.com/camunda/camunda-bpm-platform/commit/778854acbfbe98682203018a2749e82f33051d97, link Bumped to jdbc drivers to latest patches - mariadb, mysql, sqlserver, postgresql. Bumped mysql and postgresql versions in docker tests. Updated supported environments in docs. The announcement is already adjusted.

Notes: There's an issue with newer mariadb jdbc drivers related to batch processing. Previously opened ticket CAM-8891 (Investigate why batch processing does not work with MariaDB 10.2 and JDBC driver versions >= 1.7.0 or >= 2.1.0). Stack trace:

Caused by: org.camunda.bpm.engine.ProcessEngineException: ENGINE-03004 Exception while executing Database Operation 'DELETE_BULK deleteExceptionByteArraysByIds {id=7286}' with message '
### Error flushing statements.  Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.HistoricJobLogEntity.deleteExceptionByteArraysByIds_mysql (batch index #1) failed. Cause: java.sql.BatchUpdateException: (conn=5) This command is not supported in the prepared statement protocol yet
### Cause: org.apache.ibatis.executor.BatchExecutorException: org.camunda.bpm.engine.impl.persistence.entity.HistoricJobLogEntity.deleteExceptionByteArraysByIds_mysql (batch index #1) failed. Cause: java.sql.BatchUpdateException: (conn=5) This command is not supported in the prepared statement protocol yet
java.sql.BatchUpdateException: (conn=5) This command is not supported in the prepared statement protocol yet
java.sql.BatchUpdateException: (conn=5) This command is not supported in the prepared statement protocol yet
java.sql.SQLException: (conn=5) This command is not supported in the prepared statement protocol yet

Thus bumped mariadb jdbc driver only to 1.7.6. Including in migration suite, adjusting the test fixtures (7.2-7.4) to use 1.1.8 where specific check for mariadb databasetype is not performed and it causing failures otherwise.

Dependencies updates: Link: https://github.com/camunda/camunda-bpm-platform/pull/3161#issuecomment-1438763181 No license changes.

Removed dependencies:

Added dependencies: None

yanavasileva commented 1 year ago

Reopened due to failure in docker jobs: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:copy (default-cli) on project standalone-pom: Unable to find artifact. Could not find artifact mysql:mysql-connector-java:jar:8.0.32 in central (https://repo.maven.apache.org/maven2)

Stacktrace

``` [2023-02-22T22:27:06.494Z] #11 190.1 [INFO] Configured Artifact: mysql:mysql-connector-java:8.0.32:jar [2023-02-22T22:27:06.494Z] #11 190.2 [INFO] Downloading from central: https://repo.maven.apache.org/maven2/mysql/mysql-connector-java/8.0.32/mysql-connector-java-8.0.32.jar [2023-02-22T22:27:06.494Z] #11 190.3 [INFO] ------------------------------------------------------------------------ [2023-02-22T22:27:06.494Z] #11 190.3 [INFO] BUILD FAILURE [2023-02-22T22:27:06.494Z] #11 190.3 [INFO] ------------------------------------------------------------------------ [2023-02-22T22:27:06.494Z] #11 190.4 [INFO] Total time: 41.766 s [2023-02-22T22:27:06.494Z] #11 190.4 [INFO] Finished at: 2023-02-22T22:27:05Z [2023-02-22T22:27:06.494Z] #11 190.4 [INFO] ------------------------------------------------------------------------ [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:copy (default-cli) on project standalone-pom: Unable to find artifact. Could not find artifact mysql:mysql-connector-java:jar:8.0.32 in central (https://repo.maven.apache.org/maven2) [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] Try downloading the file manually from the project website. [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] Then, install it using the command: [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] mvn install:install-file -DgroupId=mysql -DartifactId=mysql-connector-java -Dversion=8.0.32 -Dpackaging=jar -Dfile=/path/to/file [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] Alternatively, if you host your own repository you can deploy the file there: [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] mvn deploy:deploy-file -DgroupId=mysql -DartifactId=mysql-connector-java -Dversion=8.0.32 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] [2023-02-22T22:27:06.494Z] #11 190.4 [ERROR] mysql:mysql-connector-java:jar:8.0.32 ```

Root cause: The jdbc driver mysql:mysql-connector-java has been relocated and renamed to com.mysql:mysql-connector-j to since 8.0.31 version. I double checked the license, release notes and third party information. All look good.

yanavasileva commented 1 year ago

Pending: resolve docker job failures occurring due to caching issues (?). Track https://camunda.slack.com/archives/C5AHF1D8T/p1677148863900529