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

EnversService#initialize should be called only once #204

Open
4 tasks done
xavs opened this issue Oct 1, 2021 · 2 comments
Open
4 tasks done

EnversService#initialize should be called only once #204

xavs opened this issue Oct 1, 2021 · 2 comments

Comments

@xavs
Copy link

xavs commented Oct 1, 2021

Task List

  • Steps to reproduce provided
  • Stacktrace (if present) provided
  • Example that reproduces the problem uploaded to Github
  • Full description of the issue provided (see below)

Steps to Reproduce

  1. Grails 4.X.X project
  2. Hibernate Envers used. Annotate some domain with @Audited
  3. Any command via grails grails prod dbm-gorm-diff or ./gradlew :runCommand -Pargs="dbm-generate-gorm-changelog " --info --stacktrace

Expected Behaviour

plugin task is performed

Actual Behaviour

Grails application running at http://localhost:0 in environment: development
Command execution error: EnversService#initialize should be called only once

> Task :runCommand FAILED
:runCommand (Thread[Execution worker for ':',5,main]) completed. Took 14.215 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':runCommand'.
> Process 'command '~/.sdkman/candidates/java/8.0.265-open/bin/java'' finished with non-zero exit value 1
Command execution error: EnversService#initialize should be called only once`

Environment Information

  • Operating System: ubuntu 20.04
  • Grails Version: 4.0.11
  • Plugin Version: 'org.grails.plugins:database-migration:3.1.1.BUILD-SNAPSHOT' / 'org.liquibase:liquibase-core:3.10.1' Tried earlier versions as well
  • Database: mariadb
  • JDK Version: tried 11.0.8 and 8.0.265

Example Application

@davebrown1975
Copy link

Any comment on this issue? This is STILL present in Grails 5

@verglor
Copy link
Contributor

verglor commented Apr 28, 2023

As a workaround it's possible to disable hibernate-envers with configuration hibernate.integration.envers.enabled = false.

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

3 participants