fengshao0907 / javamelody

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

Java Melody does not work on Google App Engine #288

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Deploy a simple webapp with Java Melody onto Google App Engine
2. Java Melody doesn't seem to be accessible? unable to reach URL at 
http://your-google-app-id.appspot.com/monitoring
3.

What is the expected output? What do you see instead?
Expected: this URL works: http://your-google-app-id.appspot.com/monitoring
Actual: URL does not work

What version of the product are you using? On what application server, JDK,
operating system?
Java Melody v1.43.0 on Google App Engine v1.7.5

Please provide any additional information below.
Could you please provide some additional logging in Java Melody (Google App 
Engine only officially supports java.util.logging)
Notes:
a) Google App Engine does not allow writing to JVM's temp directory 
(java.io.tmpdir)
b) viewing the log output on the App Engine dashboard does not show any Java 
Melody log messages with all log levels enabled
c) can Java Melody log to memory instead of disk (as an option)? and/or create 
a plugin to store Java Melody stats to App Engine data store (instead of local 
disk)?

Original issue reported on code.google.com by a...@triggerfox.com on 21 Feb 2013 at 8:27

GoogleCodeExporter commented 9 years ago

Original comment by evernat@free.fr on 22 Feb 2013 at 8:36

GoogleCodeExporter commented 9 years ago
It seems to me that Google App Engine does not allow writing files using 
java.io.File or Java NIO, and that it does not allow to use java.lang.Thread or 
java.util.Timer. There may be other issues with GAE.

In this situation, I do not think that javamelody can be made to work at all in 
GAE.
And this issue is won't fix. Sorry.

By the way, even if it was possible, storing monitoring data in memory is not 
the goal of javamelody, because data and trends would be lost after some short 
time and because of some memory overhead.

Note that javamelody is known to work with other cloud providers, such as the 
one of the javamelody demo:
https://code.google.com/p/javamelody/wiki/Demo

Original comment by evernat@free.fr on 23 Feb 2013 at 12:28