Download: JDBInsight 3.0 EA6 - Distributed CORBA Request JVM Tracing/Profiling with Integrated Transaction Analysis
http://www.jinspired.com/products/jdbinsight/downloads/index.html The next two major releases of JDBInsight scheduled for Dec 2004 and Jan/Feb 2005 will focus on providing a comprehensive J2EE/JDBC/SQL intelligent tuning solution that goes beyond merely associating advice with a particular component type (interface or method). The first release of version 3.0 "Beautiful Evidence" will contain enhancements to the console and agent/server such as improved data collection, increased profiling coverage as well as new innovative runtime visualizations. The second release of JDBInsight 3.0 "Intelligent Advice" will offer advice that is based on observed transaction executional patterns within the context of the profile. 3.0.EA.6 Release Notes Console - Added menu command to shutdown the JVM of a server or a cluster of servers - Added new view, Leaf Traces Table, to Traces perspective within Profile showing the leaf nodes of ancestor tree nodes - Added icons and enhanced callstack classifications for JMS Server - Added VisiBroker Trace Interceptor adaptor that supports distributed profiling and tracing of calls across multiple CORBA client and servers including Borland AppServer 4.5 and Borland Enterprise Server 5 and 6. To install perform the following steps for all Java CORBA (IIOP/ RMI-IIOP) clients and servers to be traced. 1. Include the jdbidriver.jar on the classpath of the Java process. 2. Specify the following JVM parameter (see install guide for additional library command options) -Xrunjdbinsight 3. Specify the following JVM system property -Dvbroker.orb.dynamicLibs=com.jinspired.jdbinsight.trace.ext.visibroker.ServiceLoader Traces started on the client process will be transfered to the server process and appended to the trace root before server dispatching. Creating a cluster of servers and clients and taking a snapshot will allow for distributed profiling and tracing within the console. - Updated filters config to exclude org.omg.CORBA.portable.ObjectImpl - Changed default value of trace root system property to -Djdbinsight.server.tracer.root=${host},${process} 3.0.EA.5 - Added new dialog for speeding up reseting, snapping and exporting of profile data captured during a use case / scenario test for clusters and servers. The recording dialog stays active across operations and use case tests. The dialog can be activated via the Recording.. context menu on Clusters and Servers. The snapshot exported is derived from the current active mode. - Fixed a performance problem in the switching to the transaction perspective within the console's profile mode. - Additional misc. fixes and menu changes. - Extended the evaluation license period to 30 days. 3.0.EA.4 Console - Added TracePoints Table view to the Trace perspective within the Profile mode. - Added additional calculation columns to Traces table view showing inherent and sub traces statistical totals. - Added additional menu commands to the console toolbar to short cut repetitive menu work - Minor table view fixes (tooltips) - Cluster wizard now allows the addition of servers within the dialog (see below) - Minor console tree fixes - Added Configuration perspective to console within profile mode. This shoudl the configuration resources loaded via the recorded classloaders. Server - Added system property -Djdbinsight.server.tracer.root=[comma separated list]. The strings are added as distinct trace nodes to explicit traces trees. The possible list values include ${host}, ${process}, ${threadgroup}, and ${thread}. The following setting -Djdbinsight.server.tracer.root=${host},${thread} will result in the grouping of traces by host and then thread. It is also possible to include arbitrary strings such as -Djdbinsight.server.tracer.root=${host},test1 which will result in the prefixing of all traces with the host name and the string value 'test1'. - Added new profile object, TracePoint, which tracks statistics (clock, cpu, memory, blocking, waiting, gc) at the calling callstack and tracestack level. - Server models now include configuration resources such as standard J2EE XML files (META-INF/ejb-jar.xml,META-INF/application.xml) as well as jar manifests (META-INF/MANIFEST.MF) - Server now records the thread context classloader for traced invocations, interceptions and user traces. - Enclosed additional calls to standard Java classes throwing SecurityExceptions within a PrivilegedAction run method block 3.0.EA.3 - Added Traces perspectives to console within profile mode. - Transactions perspective updated to include the ability to navigate paths by trace identifiers - UI comestic changes to menus - Enclosed server side calls to standard Java classes throwing unchecked SecurityExceptions within PrivilegedActions - Interceptions are now keyed with trace identifier allowing for transaction paths to be distinguished by trace identifiers. - Added Tracing (com.jinspired.jdbinsight.trace.Tracer) API to allow users to profile individual Java code blocks in terms of JVMPI events and JDBC transactions. import com.jinspired.jdbinsight.trace.Tracer; try { Tracer.start("mytraceid"); // code block executing JDBC work directly or indirectly } finally { Tracer.stop(); } Tracer.start() calls can be nested (thread specific) with the tracer identifier providing a hierarchical tracing capability similiar to call stack trees within typical Java code profilers. The difference being that tracing within JDBInsight can consist of smaller blocks of code or span method stacks. JDBInsight can be configured to capture all object allocation costs during an active trace as well as blocking, waiting, and GC costs. Our JDBInsight console can actually trace itself helping us improve the performance of the console and enhancing the trace views!! =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
