You can disable javamelody with a parameter in the server, for example
with a system property "-Djavamelody.disabled=true":
See
http://code.google.com/p/javamelody/wiki/UserGuide#6._Optional_parameters
Like this, you can more easily enable the monitoring in dev and QA and
disable it in the sensible environment.
Or you could use a separated collect server in order to manage the
storage and the reports.
See
http://code.google.com/p/javamelody/wiki/UserGuideAdvanced#Optional_centralization_server_setup
If you do not include the jrobin jar file in the monitored webapp, the
monitored webapp will not try to store the data on the filesystem and it
will wait the collect server to give the data to it.
Otherwise, you can't have the monitoring if you do not store the data in
a filesystem.
bye,
Emeric
Le 17/02/2012 10:55, mineral...@gmx.de a �crit :
I do not think that storing the data in memory only would be possible in
the future.
Because it would need too much change with many risks of massive heap usage.
Sorry,
Emeric
Le 20/02/2012 10:10, mineral...@gmx.de a �crit :