Hello everyone! We just released a new version of the lightweight Java profiler, XRebel with a few important improvements. With XRebel 2.1 you will be able to trace asynchronous invocations for applications that spawn threads via Thread or ExecutorService API. You will also be able to better understand the results since we have added rendering of the aggregated database queries into the application profiling view.
Have you observed how your web application can slow down due to extra HTTP requests? The HTTP client may execute multiple requests instead of just one request and you might not even notice! HTTP redirects are the cause of the extra requests. Also, it is not easy to spot those extra requests if you’re not specifically looking for them to appear. XRebel, the lightweight Java profiler can give you the insight needed to find extra requests, if any.
Data that you don’t care about? We’ve got a fix for that!
The theme of this series of blog posts post has been showcasing how XRebel is giving users useful information, while keeping it simple. Here are the first two posts, in case you missed it:
- XRebel UI Awesomeness for Java Enterprise apps
- Improved XRebel UI for tracking HTTP invocations, SQL and NoSQL queries
UI design is all about simplicity. What does it mean to be simple?
Hello and welcome, XRebel 1.2!
The new version of XRebel comes with support for Hibernate/JPA, Redis, Java RMI, WildFly 8.2, improvements for MongoDB support and adds some eye candy too!
MongoDB is the most popular NoSQL data store available today. MongoDB organizes JSON-like documents into collections. One collection may contain multiple documents with different structures. It is then up to the user to organize these documents by logically grouping ‘em into collections.