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
It is a great feature that archaius supports management over JMX. Though the list of operations which are possible over JMX is a little limited.
Would it be possible to extend the list of supported operations to be able to control the whole properties store and not only single property.
flush the store (clear all entries)
refresh the store (pull all entries)
get size of the store (without pulling all entries and calling size() on them)
get usage metrics
A use case which needs such functionality:
Using DynamicConfiguration with JDBCConfigurationSource and FixedDelayPollingScheduler. Since the properties don't change very often, have the delay of 24 hours. This is quite ok.
But when there is a network issue data reload fails. Next attempt to load the data will be again in 24 hours. So when the network issue has been fixed we still have to wait in worst case another 24 hours to get data reloaded.
If we had the flush/refresh functionality over JMX, then one could just simply trigger the store reload when the network issue is fixed.
A use case of metrics:
Using JMX for monitoring the services. Would pull the store metrics over JMX put the data into Graphite and directly see nice charts about how the store behaves. Especially useful for the case where the store size is limited and want to see how many entries are in the store.
The text was updated successfully, but these errors were encountered:
It is a great feature that archaius supports management over JMX. Though the list of operations which are possible over JMX is a little limited.
Would it be possible to extend the list of supported operations to be able to control the whole properties store and not only single property.
A use case which needs such functionality:
Using
DynamicConfiguration
withJDBCConfigurationSource
andFixedDelayPollingScheduler
. Since the properties don't change very often, have the delay of 24 hours. This is quite ok.But when there is a network issue data reload fails. Next attempt to load the data will be again in 24 hours. So when the network issue has been fixed we still have to wait in worst case another 24 hours to get data reloaded.
If we had the flush/refresh functionality over JMX, then one could just simply trigger the store reload when the network issue is fixed.
A use case of metrics:
Using JMX for monitoring the services. Would pull the store metrics over JMX put the data into Graphite and directly see nice charts about how the store behaves. Especially useful for the case where the store size is limited and want to see how many entries are in the store.
The text was updated successfully, but these errors were encountered: