5608057 / javamelody

Automatically exported from code.google.com/p/javamelody
0 stars 0 forks source link

reporting server data location #312

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. setup javamelody reporting server
2. restart reporting server
3. configuration/data is lost since it was in TOMCAT_HOME under /tmp

What is the expected output? What do you see instead?
Is there a way to configure the reporting server so that the 
applications.properties and other data javamelody writes to TOMCAT_HOME can be 
redirected to another location - without changing TOMCAT_HOME of course.

I know for the javamelody war that is embedded in a webapp there is a property 
for this but didnt find any instructions to do the same with the reporting 
server - can you describe what the changes in the collect server web.xml would 
like if that is what needs to be changed? 

What version of the product are you using? On what application server, JDK,
operating system?
javamelody latest release; Tomcat 6; Ubuntu 10.04 LTS

Please provide any additional information below.

Original issue reported on code.google.com by mmarti...@oreillyauto.com on 21 May 2013 at 6:35

GoogleCodeExporter commented 8 years ago
It's the same property in the centralized reporting server.

For example, you can start the reporting server with a system property:
-Djavamelody.storage-directory=/path/to/directory

https://code.google.com/p/javamelody/wiki/UserGuideAdvanced#Optional_centralizat
ion_server_setup

Note: the use of a centralized server is optional

Is it ok for you?

Original comment by evernat@free.fr on 23 May 2013 at 3:13

GoogleCodeExporter commented 8 years ago
Yes thank you for the clarification

Original comment by mmarti...@oreillyauto.com on 24 May 2013 at 6:59

GoogleCodeExporter commented 8 years ago

Original comment by evernat@free.fr on 24 May 2013 at 8:06