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

JPA View: make sure JPA view logs warnings correctly. #955

Closed
zambrovski opened this issue Mar 4, 2024 · 0 comments · Fixed by #956
Closed

JPA View: make sure JPA view logs warnings correctly. #955

zambrovski opened this issue Mar 4, 2024 · 0 comments · Fixed by #956
Assignees
Labels
Prio: Must This feature must be implemented in current milestone. Status: In progress Assignee is working on this issue. Type: bug Something isn't working
Milestone

Comments

@zambrovski
Copy link
Member

Steps to reproduce

  • camunda-bpm-taskpool version: 4.1.3
  • Camunda BPM version: any
  • JDK version: any
  • Operating system: any
  • Steps: The log statements in JPA view have wrong severity / are not logged at all.

Expected behaviour

All unexpected violations are logged on WARN severity.

Actual behaviour

Some are missing, some are not logged at all.

@zambrovski zambrovski added Type: bug Something isn't working Prio: Must This feature must be implemented in current milestone. labels Mar 4, 2024
@zambrovski zambrovski added this to the 4.1.4 milestone Mar 4, 2024
@zambrovski zambrovski self-assigned this Mar 4, 2024
@zambrovski zambrovski added the Status: In progress Assignee is working on this issue. label Mar 4, 2024
zambrovski added a commit that referenced this issue Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio: Must This feature must be implemented in current milestone. Status: In progress Assignee is working on this issue. Type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant