I have discovered that after swapping to using Logging-Profile's, some log lines are still logged not using the correct Logging-Profile.
Examples lines (not ordered or necessarily relevant to each other):
2025-01-23T19:58:55,005 WARN (EJB default - 2) IJ000621: Destroying connection that could not be validated.....
2025-01-23T14:06:00,821 WARN (Thread-2553 (ActiveMQ-client-global-threads)) SQL Error: 1, SQLState: 23000
2025-01-23T14:06:00,821 ERROR (Thread-2553 (ActiveMQ-client-global-threads)) ORA-00001: unique constraint (...) violated...
2025-01-23T14:06:00,772 ERROR (Thread-2571 (ActiveMQ-client-global-threads)) IJ031070: Transaction cannot proceed: STATUS_MARKED_ROLLBACK
These lines, usually some sort of error/warn/stack trace are still logged with the Default/Root logger, instead of my logging profile.
I could see the error about destroying a connection being only tied to Wildfly and not a specific artifact, therefore logging with root configuration, but unique constraint log is very much the cause of an artifact, and I would think it should use the configurated logger profile?
Is this the expected behavior? Anyway around this?