| Server: Comprehensive performance management solution for HP OpenView ServiceDesk 4.5 and 5.0 client and server applications. |
JXInsight 4.1 delivers unprecedented trace integration with HP OpenView's ObjectServer - the application server platform used to deliver HP OpenView's next generation ITSM products such as ServiceDesk 5.0, Service Level Manager 5.0, CMDB Manager and NetComplete 5. Via extension points within the ObjectServer's AOP Trace framework JXInsight provides deep insight into the runtime behavior of the server workflow including transaction and component execution trace and profile analysis. The distributed trace extension
provides the ability to trace back all database transactions to the actual HP OpenView Java Swing client console - down to the line of Java code. Combining this with JXInsight 4.1 Swing/AWT trace extension enables the HP OpenView Performance Test engineering team to track all requests and transactions to the actual UI component that the user interacted with.
With growing adoption of JXnsight amongst HP OpenView customers JInspired has back ported the trace integration to older versions of the HP OpenView application server technology providing the first application performance management solution for HP OpenView ServiceDesk 4.5 and 5.0 customers.
ITP (proprietary protocol used between client and server) request metrics are also delivered with the trace integration to provide early warning detection for performance problems resulting in failures in meeting internal service level agreements. The metrics
|
| Server: Service times for fast detection of concurrency |
With this release JInspired delivers a new innovative profile measurement, Service Time, which provides a clock time that reflects the level of concurrency for a particular resource (JVM, Database) during a measurement interval (Trace, Interception). Having service time statistics in a Profile model helps determine whether a resource contention within the JVM could have potentially impacted the response clock time. The feature can be used to measure the level of concurrency for any arbitrary resource including a JVM, a database url, an application tier, a technology component, a Java class, or a Java target object. Learn More
|
| Server: On-demand remote thread stack dumps |
Operations staff using the JXInsight application management console can easily initiate a thread stack dump within a remote managed JVM. This can also be scripted via the JXInsight Terminal providing a simple and effective routine investigation method for thread deadlocks and excessive CPU consumption.
|
| JVMInsight: Inspection of JNDI |
JVMInsight is an extensible and configurable repository inspection solution that enables the JXInsight management and monitoring console to display additional state information acquired from a server's (local and remote) repositories. Having the ability to access such detailed runtime configuration and state information from a production JVM is crucial in resolving service performance and outage problems. For developers this information provides a level of detail normally provided by a Java debugger but without the overhead. For testers the information can be stored for ongoing change & configuration management activities. With the ability to configure the automatic export of information from multiple repositories in the event of a runtime event (request failure, performance slowdown, JVM shutdown) operations and support staff have a powerful tool for post analysis of related incidents and service calls. Consolidating the performance profile, metric and tracing information with the runtime state and configuration enables remote support staff to work on resolving issues without the need to have actual physical access to the production systems.
JXInsight 4.1 can inspect a remote server's JNDI service and display this to developer or operations staff within the management console by executing a discovery and data collection of the servers JNDI tree from within the server's JVM. An unique feature of the data collection is the ability to capture and record runtime class information (see tool tip) Learn More
|
| JVMInsight: Inspection of JNDI Deployed Data Sources |
JXInsight 4.1 can search the JNDI service from within a remote server JVM for deployed JDBC Data Sources. Upon discovery of valid data sources the inspection will collect database information such as Catalogs, Schemas, Tables and Columns, via the JDBC MetaData API. System properties are available to configure each individual server process so as to control the level of information extracted from the database repository.
|
| JVMInsight: Inspection of BEA JRockit JVM Runtime Management (JMAPI) |
JInspired is the first application performance management vendor to use the BEA JRockit management specific API's to deliver a powerful inspection of the runtime state of a remote server JVM. Using the JRockit Management API (JMAPI), which predates the Java 5 management and monitoring API, developers, testers and operations staff can access a wealth information related to the JVM runtime state and configuration such as code generation strategies, garbage collection strategies, threads, call stacks, monitors, processor affinity, classloaders and classes from within the award winning JXInsight management console. Learn More
|
| JVMInsight: Inspection of HP OpenView ObjectServer Repository |
JXInsight's JVMInsight can collect information from meta data repositories such as HP's OpenView ObjectServer. Repository information related to installed Modules, EntityTypes, Attributes, Templates as well as customized settings can be embedded within JXInsight's trace and profile snapshots enabling the effective delivery of support initiatives - "HP OpenView Self Healing Services".
|
| JVMInsight: Inspection of Java LogManager |
With JXInsight's JVMInsight feature it is also possible to inspect the configuration of loggers, handlers, and formatters within a remote JVM. Learn More
|
| JVMInsight: Inspection of DriverManager |
JXInsight 4.1 can inspect JDBC Drivers currently registered with the JVM java.sql.Driver Manager singleton within a remote server JVM. Code source and classloader information is recording within the snapshot to help assist staff troubleshooting JDBC connection problems caused by deployment plan mis-configuration. Learn More
|
| JVMInsight: Inspection of Java 5 Management API (MXBeans) |
The JXInsight management and monitoring console can display runtime state and metric information related to memory managers, memory pools, threads, call stacks, monitors, and garbage collectors accessed from within a server JVM via the standard Java SE Management and Monitoring API.
|
| JVMInsight: Inspection of RMI Registry |
JXInsight's JVMInsight technology enables the inspection of a connected RMI Registry from within a remote server JVM.
|
| JVMInsight: Inspection of CORBA CosNaming context tree |
The JXInsight 4.1 management console can inspect the CosNaming service from within a remote server JVM collecting information related to bindings.
|
| JVMInsight: Inspection of Swing/AWT Container/Component tree |
The UI component hierarchy structure of Java Swing/AWT applications can be inspected from within the JXInsight management console. This enables the collection and recording of structural information within a profile snapshot in the event of an application error helping support staff resolve incidents and problems offline.
|
| JVMInsight: Inspection of current executing JDBC/SQL calls - ActiveWatch |
JXInsight can inspect the internal state of its own probes and proxies. The JXInsight JDBC/SQL ActiveWatch plug-in allows operations staff to see the currently executing JDBC API calls in real-time. Call stacks, traces stacks and SQL strings are collected and recorded within the repository snapshot. The ability to inspect active SQL statements is extremely useful when operations staff are alerted by users reporting hung applications or significant performance slowdowns in user transactions.
|
| Console: Trace Concurrency Level Graph |
The timeline visualization now displays the concurrency level for profiled traces in a bar chart embedded within the top of the timeline threads graphic. The concurrency level of traces emitted by the many JXInsight trace extensions can be determined across a cluster of machines and processes by simply merging snapshots within the management console. The height of the bar chart equates to the number of concurrent threads processing traced invocations.
|
| Console: Selected SQL Concurrency Level Graph |
The timeline visualization now displays the concurrency level for the currently selected SQL invocation in the timeline graphic. This is useful in determining the level of concurrency for a particular SQL string through the interval time of the snapshot. It is also helpful in finding other executions of the same SQL string in the timeline irrespective of concurrency level. The two timeline screen shots below show 3 concurrency bar charts for transactions, traces and SQL statements. Note the bottom bar chart changes based on the selected SQL invocation in the timeline threads graphic.
|
| Trace: Swing/AWT Trace Extension |
JInspired delivers with JXInsight 4.1 the industry's first trace and profile solution for Java Swing with the ability to tag AWT queued events across post & dispatch calls. JXInsight 4.1 solves one of the biggest testing pains for Swing developers - the disconnect between the call stack of the thread placing posting an event to the AWT EventQueue and the call stack of the thread dispatching the event. Learn More
|
| Trace: Upgrading of Hibernate and JDO Trace Extensions. |
The JDO, EJB3 and Hibernate trace extensions have been updated to reflect the latest versions of the technology and specifications.
|
| Trace: Distributed Trace Extension for BEA WebLogic 8.x RMI |
JXInsight 4.1 introduces the ability to trace WebLogic RMI calls from a Java application to a WebLogic server via BEA WebLogic's built-in trace context propagation mechanism. The following screen shot of the traces table view in the JXInsight application management console shows the traces recorded in both client and server JVM's added to a JXInsight management cluster. The trace stack of the client call (PingSession.ping) is transferred across to the server and inserted into the trace stack of the request processing thread.
With JXInsight's WebLogic RMI distributed tracing extension comparing the processing times for the client and server has never been so easy. The selected client trace in the bottom middle section of the timeline graphic is visually connected to the server trace in the top middle section of the timeline graphic. This visualization makes it extremely simple to determine where the processing bottleneck is for a client initiated transaction.
|
| Trace: TestNG Trace Extension |
TestNG is a testing framework inspired by JUnit and NUnit but introducing some new functionality that make it more powerful and easier to use. JXInsight 4.1 provides a trace extension for TestNG via the class, com.jinspired.jxinsight.trace.ext.testng.TraceTestListener, which implements the interface org.testng.ITestListener and extends the adapter class org.testng.TestListenerAdapter. Combining this trace extension with the other distributed trace extensions for JBoss, CORBA or WebLogic RMI enables testing teams to derive transaction and trace metrics for tests that execute such remote processing.
|
| Metrics: Configurable Trace Metric Groups |
It is now possible to add additional trace metrics to a monitored server process grouping statistics (clock time, cpu time, blocking time, waiting time, service time, gc time, and object allocation byte sizes) based on trace types and identifiers. This flexibility allows for standard and custom defined trace extensions to have summary measurement groupings suitable for quick break downs of performance costs across tiers, systems and components.
Learn More
|
| Metrics: Java 5 JVM Management Attributes Metrics |
The JXInsight metric collector will automatically detect a Java 5 runtime and start collecting and recording important metrics from the Java 5 Management JMXBeans such as thread counts, memory sizes (heap and non-heap), classes loaded and unloaded, gc collection cycles.
|
| Console: Traces Call Stack Graph |
JXInsight is the only Java application performance management (APM) solution on the market that collects detailed call stacks for all profiled traces. Other APM solutions provide an incomplete call stack derived solely from instrumented methods which means the application centric calls between instrumented methods is not accessible. JXInsight provides both the call stack and the trace stack with statistics for CPU, Clock Time, GC, Thread Blocking, Thread Waiting, Object Allocation aggregated across threads, processes and clusters of application server instances. The powerful visualizations in the JXInsight application management console can seamlessly switch between cluster and server scopes.
|
| Console: Fast Distributed Call Stack Navigation |
The new traces call stacks graph and table views provide faster navigation from server-side call stacks to client-side call stacks. Switching the bottom view site to Client Trace Points Table view makes it extremely easy to pinpoint the actual client side call stack for server side request even when the request was generated indirectly by another thread within a Java Swing application. Learn More
|
| Console: Custom Trace Icons |
JXInsight customers and partners can now extend the console by including custom icons for user defined trace extensions. This is the first step in creating a customized version of JXInsight suitable for embedding in commercial products that require built-in performance management capabilities for operations and product support staff. Learn More
|
| Trace: Servlet TraceFilter Enhancements |
Enhancements to Servlet trace extension to support dynamic trace injection and enablement/disablement.
|
| Miscellaneous Enhancements and Bug Fixes. |
