You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way SessionFactoryImpl.GetCacheConcurrencyStrategy() is currently written, if a warning is logged, "read-only cache configured for mutable: {0}", the value provided to the log message is the readonly variable "name" which is always set to the value of the SessionFactoryName setting. This value is not very useful when trying to track down the source of the problem.
Instead something like the model.ClassName or model.Type.Name should be included in the logging message, depending on the caller. Alternatively, the log.warn should be moved outside GetCacheConcurrencyStrategy() and logged by the callers.
The text was updated successfully, but these errors were encountered:
fredericDelaporte
changed the title
SessionFactoryImpl.GetCacheConcurrencyStrategy() uses wrong name value when warning message is logged
Wrong name value for L2 read-only cache warning on mutable
Mar 25, 2023
The way SessionFactoryImpl.GetCacheConcurrencyStrategy() is currently written, if a warning is logged, "read-only cache configured for mutable: {0}", the value provided to the log message is the readonly variable "name" which is always set to the value of the SessionFactoryName setting. This value is not very useful when trying to track down the source of the problem.
Instead something like the model.ClassName or model.Type.Name should be included in the logging message, depending on the caller. Alternatively, the log.warn should be moved outside GetCacheConcurrencyStrategy() and logged by the callers.
The text was updated successfully, but these errors were encountered: