I found the problem and the fix was tested by the product engineer who
reported it. The problem was that AbstractHierarchicalConfiguration was
calling setDetailEvents while unlocked. Multiple threads would get in and so
the ConfigurationListener was never notified of the event. I just had that
relo
Ralph Goers schrieb:
It seems my latest changes are insufficient. It appears that under heavy
load reloading the default config file in a combined configuration can
still result in a corrupt state.
:-(
Do you think there is a feasible solution at all for the 1.x series?
FYI, I am still work
It seems my latest changes are insufficient. It appears that under
heavy load reloading the default config file in a combined
configuration can still result in a corrupt state.
-
To unsubscribe, e-mail: dev-unsubscr...@common
