New Relic Enhances Support for Oracle’s WebLogic

Oracle’s WebLogic Java application server provides many capabilities that enhance the experience of operating enterprise applications at scale. New Relic Java agent version 3.8 automatically retrieves a critical set of JMX (Java Management Extensions) metrics from WebLogic instances and presents the data on the Java virtual machine’s tab. This data can be invaluable for diagnosing issues with your WebLogic instances and for tuning container resources to deliver maximum performance with your applications.

Data Sources

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.

weblogic 1

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.

weblogic 2

EJB Transactions

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.

weblogic 3

Conclusion

We’re excited to provide this level of visibility into WebLogic instances and the applications running on them. Check out our documentation for more details about the instrumentation. If you have questions, concerns, or suggestions we’d love to hear from you in our community forum!

Greg Unrein is VP of Product Management for New Relic. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!