Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Liquibase migration run from java code never ends because of number of living non-daemon threads #103

Open
Jenya95 opened this issue Sep 29, 2021 · 0 comments

Comments

@Jenya95
Copy link

Jenya95 commented Sep 29, 2021

I've created project that reproduces my issue at https://github.com/Jenya95/liquibase-cassandra-issue
I'm using liquibase directly from java to create objects in database. For other types of database it works well, but for cassandra - program never ends because of number of living non-daemon threads. Close connection did not help.
Log like this: (pay attention on threads at the end of log):

[main] INFO com.datastax.oss.driver.internal.core.DefaultMavenCoordinates - DataStax Java driver for Apache Cassandra(R) (com.datastax.oss:java-driver-core) version 4.8.0
[s0-admin-0] INFO com.datastax.oss.driver.internal.core.time.Clock - Using native clock for microsecond precision
[s0-io-2] WARN com.datastax.oss.driver.api.core.auth.PlainTextAuthProviderBase - [] localhost/127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[s0-io-3] WARN com.datastax.oss.driver.api.core.auth.PlainTextAuthProviderBase - [] localhost/127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Sep 29, 2021 10:55:14 AM liquibase.ext
INFO: No DATABASECHANGELOGLOCK available in cassandra.
Sep 29, 2021 10:55:14 AM liquibase.ext
INFO: successfully.acquired.change.log.lock
Sep 29, 2021 10:55:14 AM liquibase.ext
WARNING: expecting exactly 1 table with name DATABASECHANGELOG, got 0
Sep 29, 2021 10:55:14 AM liquibase.ext
INFO: Creating database history table with name: sample.DATABASECHANGELOG
Sep 29, 2021 10:55:14 AM liquibase.ext
INFO: Reading from sample.DATABASECHANGELOG
Sep 29, 2021 10:55:15 AM liquibase.changelog
INFO: SQL in file scripts/sample_table.cql executed
Sep 29, 2021 10:55:15 AM liquibase.changelog
INFO: ChangeSet cassandra-scheme/changesets/sample-table-init-1.0.xml::create_sample_table::me ran successfully in 65ms
Sep 29, 2021 10:55:15 AM liquibase.ext
INFO: Successfully released change log lock
[Thread-35] INFO com.sample.LiquibaseApp - ----------------------------
[Thread-35] INFO com.sample.LiquibaseApp - Threads prevent to stop jvm:
[Thread-35] INFO com.sample.LiquibaseApp - 80:cluster3-connection-reaper-0
[Thread-35] INFO com.sample.LiquibaseApp - 127:cluster5-nio-worker-0
[Thread-35] INFO com.sample.LiquibaseApp - 120:cluster4-nio-worker-0
[Thread-35] INFO com.sample.LiquibaseApp - 123:cluster4-worker-0
[Thread-35] INFO com.sample.LiquibaseApp - 146:cluster7-worker-0
[Thread-35] INFO com.sample.LiquibaseApp - 184:DestroyJavaVM
...

┆Issue is synchronized with this Jira Bug by Unito

@Jenya95 Jenya95 changed the title Liquibase migration run from java code never ends because of number of living non-deamon threads Liquibase migration run from java code never ends because of number of living non-daemon threads Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant