Use New Relic to monitor your Java applications running on the Oracle’s WebLogic Java Application Server. New Relic provides deep visibility into the performance and health of Java applications running on WebLogic all the way down to the line of code or SQL statement. New Relic provides rich JVM analysis, transaction tracing, and a lightweight production thread profiler to troubleshoot the most complex application performance problems.
See the details for each of your WebLogic data sources, including active and available connections in your connection pools; the number of successful, failed, and waiting connection requests; the number of connections created; the total number of connections leaked; and the size of the data source’s statement cache.
Java Transaction API (JTA)
On the JTA tab you can see the number of committed, rolled back, and abandoned transactions as well as the overall percentage of committed transactions for the entire time period.
On the EJB Transactions (Enterprise Java Beans) tab you can see how many committed and rolled back transactions are occurring for each of the applications deployed in your WebLogic instances. In this example there are two applications presented: “medrec” with 100% committed transactions and “mejb” with 80% committed transactions.
Key Features for Java Applications on WebLogic
- Monitor distributed and SOA applications with Cross Application Tracing
- Track business critical transactions with Key Transactions
- Get call tree analysis with New Relic’s production Thread Profiler
Get deep insight into the health of your WebLogic JVMs:
JVM Memory Graphs for WebLogic
- Heap memory usage graph
- Non-heap memory pool usage graph
- Garbage collection graph
- Loaded and unloaded class count graph
Thread Analysis for WebLogic
- Active thread count graph
- Thread pool graphs for active and idle threads