Resource bundle keys unresolved: ejb.timer_service_started #506
Comments
|
I will do all fixes under #502 because all those bugs somehow depends on each other. The core of the problems is searching of LogStrings.properties file in class LogDomains, using different classloaders, placed in different jar files ... sometimes shared, sometimes they are "zombies" after refactoring ... |
MeroRai
pushed a commit
to MeroRai/Payara
that referenced
this issue
Oct 10, 2018
Increment version numbers
aubi
pushed a commit
to aubi/Payara
that referenced
this issue
Jan 3, 2022
….34.0 Increment version numbers 5.34.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The reason is that PersistentEJBTimerService in ejb-full-container has it's own LogStrings.properties, but the key is in LogStrings.properties in ejb-container
The cause of this is probably some incomplete refactoring.
Unresolved bundle keys make bug hunting impossible (this one is maybe not that case, but in general ...)
I don't know if it can be automatically tested somehow ... any idea?
See also issue #502 ...
The text was updated successfully, but these errors were encountered: