Unexpected logging behavior and warning message

[OleKsimov]

Describe the bug

Hi guys!

I don't know if it's a bug or not.

1. When I set the following properties in a new project:

quarkus.log.min-level=TRACE
quarkus.log.level=TRACE

I receive warning in logs:

WARN: Root log level TRACE set below minimum logging level DEBUG, promoting it to DEBUG

Some trace logs are displayed anyway.

2. In the test, I'm injecting UserTransaction class and then calling:

userTransaction.begin();

And I would expect TRACE logs to be shown, but when BaseTransaction.begin checks logging level:

if (jtaLogger.logger.isTraceEnabled()) { ... }

only INFO level is enabled.
Could you please help me see TRACE logs from the Narayana library in this case?

The reproducer is attached.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

jboss-logging-check.zip

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.7.5.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[famod]

I'll send a PR soon that'll remove that warning

WARN: Root log level TRACE set below minimum logging level DEBUG, promoting it to DEBUG

but turns out that this is not the root cause:
The same code in a Maven project will print BaseTransaction messages just fine (and also that warning).

So it seems to be a gradle specific problem? cc @glefloch

[gsmet]

Well, that warning shouldn't be entirely removed. But if it appears when min-level is properly set up, there's probably something fishy.

[famod]

Well, that warning shouldn't be entirely removed.

Right, that's not what I'm going to do. The warning is a false negative here and that's what I'm going to fix.

[geoand]

Is this still an issue?

[geoand]

Closing for lack of feedback