Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 34.0.0.Beta1, 34.0.0.Final
Affects Version/s: 34.0.0.Beta1
Component/s: Logging, Security Manager, Test Suite
Labels:
None

Forum Reference:
https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/topic/WFLY-19709.20Nightly.20SM.20Tests.20Failing
[QE] How to address?:
---
[QE] Why QE missed?:
---

Many tests started failing with Java Security Manager on Java 17+ after updating WF Core to 26.0.0.Beta3: https://ci.wildfly.org/buildConfiguration/WF_MainSecurityManagerJdk17?buildTypeTab=overview

I think the cause is the update of jboss-logging to version 3.6.0 where a fix for ~~JBLOGGING-184~~ removes doPrivilidged around doGetMessageLogger.

is caused by

JBLOGGING-184 Logger interface implementations inaccessible in module mode

Resolved

WFCORE-6883 Upgrade to jboss-logging 3.6.0 / jboss-logging-tools 3.0.0

Resolved

WFLY-19684 Upgrade WildFly Core to 26.0.0.Beta3

Resolved

is incorporated by

WFLY-19733 Upgrade WildFly Core to 26.0.0.Beta4

Resolved

is related to

JBLOGGING-190 Deprecated getBundle and getMessageLogger methods with throw a SecurityException if the security manager is enabled

Resolved

is triggering

WFCORE-6983 Upgrade JBoss Logging to 3.6.1.Final

Resolved

(1 is triggering)

Assignee:: James Perkins

Reporter:: Ondrej Kotek

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024/09/06 12:12 PM

Updated:: 2024/10/17 4:54 PM

Resolved:: 2024/09/17 2:13 PM