Commit 126fd47
committed
Fix potential timing issue involving CustomLogManagerTest
Avoid accessing the CustomLogManager type in the LogManagerSetter test application
because this will load jul.LogManager, which triggers our class-loading hooks, and
ends up activating various Tracer services like JMX that initialize JUL.
If this happens before we've set the custom logger system property, ie:
System.setProperty("java.util.logging.manager", CustomLogManager.class.getName());
then there's a very small window where JUL could be initialized before the updated
system property has taken effect (since the class-loading hook and follow-on services
run on a different thread.)1 parent ec1aabd commit 126fd47
1 file changed
Lines changed: 7 additions & 3 deletions
Lines changed: 7 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
7 | 11 | | |
8 | 12 | | |
9 | 13 | | |
10 | 14 | | |
11 | 15 | | |
12 | | - | |
| 16 | + | |
13 | 17 | | |
14 | 18 | | |
15 | 19 | | |
| |||
49 | 53 | | |
50 | 54 | | |
51 | 55 | | |
52 | | - | |
| 56 | + | |
53 | 57 | | |
54 | 58 | | |
55 | 59 | | |
| |||
93 | 97 | | |
94 | 98 | | |
95 | 99 | | |
96 | | - | |
| 100 | + | |
97 | 101 | | |
98 | 102 | | |
99 | 103 | | |
| |||
0 commit comments