查看 Glassbox，Java 应用程序的故障排除代理，可自动诊断常见问题。 Glassbox 作为 war 文件部署到您的应用程序服务器，然后使用 AspectJ 加载时间编织来监视应用程序组件和其他工件，以便识别诸如过多或失败的远程调用、缓慢的查询、过多的数据库查询、线程争用，甚至什么请求等问题参数导致故障。
Glassbox 通过使用方面来跟踪组件交互，以非侵入方式监控应用程序。我们还监控内置 JMX 数据，特别是在 Java 5 VM 上我们采样线程数据（默认情况下每 100 毫秒一次）。在处理请求时，我们会总结值得注意的事件，例如在哪里花费了时间以及涉及哪些参数导致事情变慢或失败。我们还检测用于报告的更高级别的操作（例如 Struts 操作或 Spring 控制器）。然后，我们的 AJAX Web 客户端会根据受监控机器上的操作提供状态摘要，并根据请求生成更详细的分析。 Glassbox 允许监控服务器集群：Web 应用程序使用 JMX Remote 或直接 RMI 来访问远程服务器的数据。我们还提供对较低级别汇总统计信息的 JMX 远程访问。
Check out Glassbox, a troubleshooting agent for Java applications that automatically diagnoses common problems. Glassbox deploys as a war file to your appserver and then uses AspectJ load time weaving to monitor application components and other artifacts, in order to identify problems like excess or failed remote calls, slow queries, too many database queries, thread contention, even what request parameters caused failures.
Glassbox monitors applications non-invasively by using aspects to track component interactions. We also monitor built-in JMX data, notably on a Java 5 VM we sample thread data (every 100 ms by default). As a request is processed, we summarize noteworthy events such as where time was spent and what parameters were involved in making things slow or fail. We also detect higher-level operations (such as Struts actions or Spring controllers) that we use to report on. Our AJAX Web client then provides summaries of status by operation on the machines being monitored and we generate a more detailed analysis on request. Glassbox allows monitoring clusters of servers: the Web app uses JMX Remote or direct RMI to access data from remote servers. We also provide JMX remote access to the lower-level summary statistics.
I've found Yourkit to be a pretty amazing profiler for java. It does wonderful hotspot analysis and memory profiling. I've used it to find many a memory leak as well as lots of optimizations.
It also has a nice Eclipse integration plugin (if that's your bag)
发布评论
评论（4）
Cobertura 和 Emma 将执行代码覆盖率分析。
就多线程正确性而言，FindBugs 会做其中的一些工作。然而它执行静态分析。即在程序运行时不。
Cobertura and Emma will perform code coverage analysis.
In terms of multi-threaded correctness, FindBugs will do some of this. However it performs static analysis. i.e. not whilst the program is running.
查看 Glassbox，Java 应用程序的故障排除代理，可自动诊断常见问题。 Glassbox 作为 war 文件部署到您的应用程序服务器，然后使用 AspectJ 加载时间编织来监视应用程序组件和其他工件，以便识别诸如过多或失败的远程调用、缓慢的查询、过多的数据库查询、线程争用，甚至什么请求等问题参数导致故障。
Check out Glassbox, a troubleshooting agent for Java applications that automatically diagnoses common problems. Glassbox deploys as a war file to your appserver and then uses AspectJ load time weaving to monitor application components and other artifacts, in order to identify problems like excess or failed remote calls, slow queries, too many database queries, thread contention, even what request parameters caused failures.
我发现 Yourkit 是一个非常棒的 Java 分析器。它具有出色的热点分析和内存分析功能。我用它发现了许多内存泄漏以及许多优化。
它还有一个很好的 Eclipse 集成插件（如果这是你的包）
I've found Yourkit to be a pretty amazing profiler for java. It does wonderful hotspot analysis and memory profiling. I've used it to find many a memory leak as well as lots of optimizations.
It also has a nice Eclipse integration plugin (if that's your bag)
我之前使用过一个名为 JRat 的性能分析器。
作为 Java 代理运行并报告统计信息，例如在某个方法中花费的时间。
One I've used before is a performance profiler named JRat.
Runs as a Java agent and reports statistics like time spent within a certain method.