Quest® Foglight Cartridge for Java EE Technologies 5.8.1
Developed for Foglight Management Server 5.6.2
Welcome to Foglight Cartridge for Java EE Technologies
New in this Release
Resolved Issues and Enhancements
Third Party Known Issues
Upgrade and Compatibility
For More Information
The Foglight Cartridge for Java EE Technologies gives you the tools you need to monitor the availability and performance of your Java Enterprise Edition (Java EE) applications and application servers.
These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.8.1 release of the Cartridge for Java EE Technologies. Review all sections before starting the installation.
This release is a maintenance release that does not contain any new features. It includes bug fixes and performance enhancements.
The following new features were contained in the 5.8.0 release:
(Location > Report Name)
WebLogic Server Summary
WebLogic Server Availability and Performance
|WebLogic Reports > WebLogic Server Summary and Performance Report|
WebSphere Server Summary
WebSphere Server Availability and Performance
|WebSphere Reports > WebSphere Server Summary And Performance Report|
OracleAS Process Summary
OracleAS Process Availability and Performance
|OracleAS Reports > OC4J Process Summary And Performance Report|
JBoss Server Summary
JBoss Server Availability and Performance
|JBoss Reports > JBoss Server Summary and Performance Report|
The following is a list of issues addressed and enhancements implemented in this release.
|JEE-7735||Application state metrics for applications deployed to cluster targets were not collected at the same interval as applications deployed directly to server targets.|
|JEE-7725||In rare instances, the Java Monitor dashboard on the Federation Master may time out.|
|JEE-7713||During an upgrade to version 5.8.x, the JavaEEDeploymentManager may fail to upgrade an already integrated Tomcat Service.|
|JEE-7695||In single traces, EJB names for some nodes appear as "Unknown EJB".|
|JEE-7678||The JavaEEDeploymentManager may fail to re-integrate WebLogic Services that use JRockit.|
|JEE-7675||The JavaEEDeploymentManager fails to recognize integrations that use the deprecated com.sitraka.pas.agent.bootstrap.AgentBootstrap package.|
|JEE-6748||The Management Server CDT sometimes rejects data aggregated by the Java EE Agent.|
|JEE-7639||The build IDs for the Java EE Agent and the Java EE Cartridge are different.|
|JEE-7583||Tag and Follow® from client to server for WebLogic RMI traces on EJBs with over 100 methods was not working.|
|JEE-7577||The JavaEEDeploymentManager agent sometimes failed to remain active after an upgrade.|
|JEE-7529||Some rules in the Cartridge for Java EE Technologies have the "undefined" severity set active.|
|JEE-7521||Some WebSphere rules generate an error message: Expected script return value is Boolean, received: null.|
|JEE-7520||The org.apache.coyote.ajp.AjpProcessor.process on JBoss 4.2.3 was not instrumented by the CoyoteConnectorInstrumentor.|
|JEE-7512||When collecting single traces using Start/Stop NewRequestInMethods, the parent request is split.|
|JEE-7487||There is no way to specify additional JVM parameters using the JavaEEDeploymentManager agent.|
|JEE-7444||The explicit class lists for the JdbcDriverInstrumentor are not configurable through the jdbc-driver-instrumentor.config file.|
|JEE-7437||In some instances, the Apache Axis instrumentation was causing a NullPointerException.|
|JEE-7419||The background threads that start and stop metrics collectors can sometimes block WebLogic execute threads and cause the WebLogic server to hang.|
|JEE-7417||The current application state for OracleAS applications that do not have EJB, Web, or Resource modules is not collected.|
|JEE-7403||When upgrading the cartridge from version 5.6.x (or earlier) to any version of 5.7.x or later, the shouldCheckState dynamic property should be removed from the WebSphere topology.|
|JEE-7394||If Tomcat is started with an IBM JVM, the Tomcat agent shuts down with a FATAL classdefnotfound error shortly after startup.|
|Topology churn may occur on the absoluteSourcePath property for WebLogicAppDeployment.|
|Tracking objects per request type does not work for classes with no packages.|
|For WebSphere, on the JMS Queues tab of the Service Integration Bus (SIB) Messaging Engines view, the SIB "Engine" and "Queue" names are always blank.|
|Service Integration Bus (SIB) queue point metrics are displayed as period average instead of period SUM.|
|For WebSphere, on the JMS Queues tab of the Service Integration Bus (SIB) Messaging Engines view, the "Avg Time Spent in Queue" and the "Max Time Spent in Queue" columns are both labeled "Time Spent in Queue".|
|JEE-7369||The Servers tile view on the JavaEE Monitor dashboard performs poorly when the JVM Average Usage and Current Usage columns are displayed.|
|JEE-7340||When enabling Debug level 2 on a JBoss agent, the File and Serialized File message writer threads may encounter a deadlock.|
|JEE-7322||High CPU usage may occur on an instrumented application server when a JRockit JVM is used.|
|JEE-7318||The ObjectTracker instrumentation does not handle implicit .class fields properly, resulting in a verify error when .class fields are added to the ObjectTracker classes section of the instrumentation.config file.|
|JEE-7310||The JavaEE Agent was not capturing metrics on resources at all scoped levels.|
|JEE-7309||The JavaEE Agent now captures the names of web services, instead of just the outgoing URL.|
|JEE-7254||Under certain conditions, when using Apache JServ, a VerifyError can occur during instrumentation.|
|JEE-7248||When more than one OC4JProcess with the same name exists in a system, it can be difficult to distinguish between them due to lack of unique identifiers on some dashboards.|
|JEE-7246||The Tomcat Host Summary and Performance Report does not allow multiple hosts to be selected as input.|
|JEE-7244||Some OracleAS JDBC datasources were not being collected.|
|JEE-7242||The JavaEEDeploymentManager failed to properly update Tomcat Services on Windows Server 2008.|
|JEE-7230||On WebSphere, the Average and Max Time Spent in Queue were sometimes not collected.|
|JEE-7228||Added a configuration option to allow Web client (that is, outgoing HTTP) nodes to appear as root nodes of requests.|
|JEE-7227||Added instrumentation support for Apache Axis so that outgoing HTTP URL nodes for web services requests are created.|
|JEE-7223||The cartridge upgrade fails with a lifecycle script error: Copy_Compatible_Configs.|
|JEE-7207||The JavaEE Agent aggregates some periodic metric data incorrectly, causing an IllegalStateException error in the CDT.|
|JEE-7199||Errors that are occur during the JavaEEDeploymentManager activation are not logged at the ERROR level.|
|JEE-7195||The JavaEEDeploymentManager performs a Registry export of Tomcat services even when the TomcatServices ASP is empty.|
|JEE-7177||The scroll bars are missing from the Web Applications table for WebSphere.|
|JEE-7168||The JavaEE Agent fails to parse the deployment descriptor XML when the file is too large.|
|JEE-7165||In certain instances, the CDT generates an IllegalStateException error for the ActiveCount metric for the WebSphere ThreadPool module.|
|JEE-7148||The JavaEE Agent fails with a NullPointerException when the tags in the server.xml file for Tomcat are in an unexpected order.|
|JEE-7145||The Tomcat thread pool usage rule references an incorrect variable.|
|For WebSphere 6 or 7, when excluding certain servers from model filtering, the excluded servers still appear in the WebSphereRuntime and/or the WebSphere6MBeanCollector data trees in the dmgr agent log, which causes excluded applications to appear in the dashboards.|
|JEE-7132||QueryCacheRuntime/../CacheHitCount is neither transformed nor explicitly ignored by the transform specification.|
|JEE-7129||The thread pool size for WebSphere workmanagers may have been reported incorrectly.|
|JEE-7126||The Nexus throws a FATAL NullPointerException when the agentID is null.|
|JEE-7013||There is no list of metrics available within the Cartridge for Java EE Technologies.|
|JEE-6923||TomcatHost object group names (unclustered or clustered) cannot be customized.|
The Java system property quest.agent.appserverinfo can now be used to customize the names of TomcatHost and TomcatHostGroup topology objects. This property consists of four optional parts, separated by either colon or semicolon characters. The format, as a command-line parameter, is:
Each part is optional and may be left blank, but the separators must still be used. Trailing separators may be omitted. To specify nothing but a custom groupname, use three colons (or semicolons) followed by your desired groupname. For example, to specify a groupname of "TomcatQAServers", use the following command-line option: -Dquest.agent.appserverinfo=:::TomcatQAServers
To specify a name for your TomcatHost other than the one configured in your server.xml file (for example, "Test1Host"), use the following command-line option: -Dquest.agent.appserverinfo=Test1Host
The second positional parameter tells the agent what kind of application server is being used. For Tomcat, the value must be "Tomcat". When omitted, the agent performs tests to determine the application server type. It is recommended that you omit this option in most cases. Unlike other supported application server types, the names specified here are used only to customize the names of topology objects on your Foglight Management Server. They are not used to identify the TomcatServer, TomcatEngine, or TomcatHost objects, and therefore can be changed without resulting in new topology objects being created on your Management Server.
For users who, prior to this release, had specified the quest.agent.appserverinfo system property with a value for the <tomcat-hostsname> option, that option value was used to identify the Tomcat system. The value is no longer used for that purpose, and a generated value is used instead. This will result in the creation of new TomcatServer, TomcatEngine, and TomcatHost topology objects on your Foglight system.
|JEE-6129||After instrumenting a WebSphere server, the WebSphere SystemOut logs may contain some Java EE log messages.|
|JEE-5912||The exported files for some grids do not include the sub-nodes.|
The following is a list of issues known to exist at the time of this release.
The Java EE Agent does not support CLASS_CACHE=true
on JRockit JVM.
Workaround: Either set CLASS_CACHE=false, or use Oracle Hotspot JVM instead.
|JEE-7351||In rare circumstances, the response time for requests may be shown as thousands of seconds, but should not be exceeding the IncompleteRequestTimeout of 120 seconds.|
In some cases, the Java EE Agent does not perform instrumentation when
restarted, due to permission problems accessing the Java EE agent
directory. This may occur after upgrading the Cartridge for Java EE
Technologies, or when restarting the Foglight Agent Manager at any time,
or when manually re-activating the JavaEEDeploymentManager after making
Workaround: The appropriate read/write permissions for the Java EE Agent directory must be set for the application server user before restarting the application server(s). If the permissions are not set appropriately, the application server will not be instrumented at startup. The default location of the Java EE Agent directory is: <FglAM_Home>\agents\JavaEE.
|JEE-7152||If you instrument JBoss or Tomcat servers and also connect the JMX Agent in an attempt to collect metrics through their MBean Server, an error may occur in the JVM itself causing the application server to shut down. It is recommended that you either use the Java EE Agent for request and periodic metric collection or the JMX Agent for periodic metric collection, but not both. This may happen for other application servers as well.|
|JEE-6942||When an MBean attribute has been collected as a "single value" and is then converted to be collected as a metric, an error message is logged by Foglight to the effect that it could not convert the value persisted. This does not affect collection of the attribute as a metric. It indicates that the previous value that was stored as a property is not incorporated into the metric.|
|JEE-6855||When the FMS is experiencing a critical performance slowdown, the Nexus may shut down with a FATAL NullPointerException.|
In a federated environment, changes made to the
"Track Per Request Type" setting on Object Tracking tab of the JVM view
on the Federation Master are displayed incorrectly on Federated
Workaround: In a federated environment, it is recommended that you only enable and disable object tracking and the related "Track Per Request Type" settings on the Federation Master.
When an application server is shut down while
object tracking is enabled, the Live Object count at the time of
shutdown remains the same until the application server is restarted.
Note: Once the application server is restarted, the metrics are reset appropriately.
|JEE-6732||The FxV action:Search Hits (request type, parameter) does not find the correct hits in FxV when searching on an HTTP Header collected by Tomcat or JBoss. This is because Tomcat and JBoss automatically convert all HTTP Header names to lowercase, and FxV does a case-sensitive comparison. Once FXV-144 is resolved, this should work as expected.|
|JEE-6133||During CDT recording feedback, request data may not be displayed.|
|JEE-6070||When the WebSphere node agent attempts to start a managed server using the Monitoring Policy, a role-based authentication exception may be generated.|
After an upgrade, you may see the following error:
2010-03-16 16:23:16.234 ERROR [http-0.0.0.0-8080-7] com.quest.wcf.portal.components.AbstractComponent - Error rendering part: default
java.lang.IllegalStateException: Can't overwrite cause
Workaround: To clear the problem, restart the Foglight Management Server.
The Java EE Agent cannot monitor
Queues and Topics that are defined using JBoss 4 syntax in JBoss 5.
Workaround: Edit Queue and Topic definitions to use the updated syntax for JBoss 5.
If a Cartridge for Java EE Technologies that is operating in a
federated environment is disconnected, the hosting Foglight Management
Server shuts down. The reason for this shutdown does not involve the
Cartridge for Java EE Technologies. When a connection between cartridges
is broken, both of the cartridges should log a message similar to the
following: INFO Disconnected from Federated
Additionally, after a Foglight Client upgrade, several warning messages can appear in the Foglight Client command window, which does not close after the upgrade. For example:
2008-11-18 15:24:00.467 INFO [FILE Message Writer] com.quest.common.log.AsynchronousLogTarget - Interesting log message encountered
2008-11-18 15:23:47.787 WARN [Thread-63] launcher/jfogbank/src/windows/kill - Could not open handle for pid 5436: The parameter is incorrect.
Workaround: In order to re-establish the connection, stop all cartridge instances, and then restart them one at a time.
|JEE-4297||Enhancement: Create a configuration file to test syntax validation for all of the Java EE configuration files.|
|JEE-4243||Old alarms are not cleared for topology objects for which data has not been collected for a period of time.|
|JEE-4210||The Cartridge for Java EE Technologies does not alert on the synchronization status if the WebSphere Application Server is out of synchronization.|
|JEE-4100||Unable to restart the Cartridge for Java EE Technologies after an invalid configuration change occurred.|
|JEE-4068||Log files may include the warning message: WARN Node has used a remote protocol too many times: The ability to find out which request made these calls is being investigated.|
|JEE-2417||The Java EE Agent does not provide full information about topology changes to the Management Server (for example, when a topology is removed or undeployed).|
The following is a list of third party issues known to exist at the time of this release.
|JEE-6785||JBoss 5 does not provide configuration or metric data for EJB3 Entity Beans.|
An IOException error occurs when instrumenting WLS 8.1.6 on Solaris 10
x86-64: Error IOException caught during
This issue is caused by a bug in some versions of the Oracle 1.4.2 JVM or Oracle Java 5 JVM. For details, see: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825
Workaround: To avoid the problem, use one of the following workarounds:
FATAL Assertion error in WebLogic 10 agent logs. This problem is
caused by an MBean object name caching bug in WebLogic 10.0. The problem
has been fixed in WebLogic 10.3.
To resolve the issue, upgrade to WebLogic 10.3.
The latest version of the Cartridge for Java EE Technologies is version 5.8.1. Upgrades from version 5.7.x and 5.8.0 are supported.
You must upgrade the Foglight Management Server to version 5.6.2 or later before you upgrade the Cartridge for Java EE Technologies to version 5.8.1. The minimum supported version of the Foglight Agent Manager is 18.104.22.168.
The Cartridge for Java EE Technologies
version 5.8.1 accepts connections from the Java EE Agent
versions 5.8.x and 5.7.x. Connections from version 5.6.1
and earlier of the Java EE Agent are not supported.
For detailed information about how to upgrade the Cartridge for Java EE Technologies, see the Foglight Upgrade Guide.
The Foglight Cartridge for Java EE Technologies must be deployed on a running Foglight Management Server version 5.6.2 or later, and to a Foglight Agent Manager version 22.214.171.124 or later. For information about system requirements for this release, refer to the "Hardware Requirements and Guidelines" section in the Foglight System Requirements and Platform Support Guide.
Before installing Cartridge for Java EE Technologies, ensure your system meets the following minimum hardware and software requirements:
|Platform||For a list of supported platforms, refer to the Supported Platforms section in the Managing Java EE Systems, Supported Platforms and Servers Guide.|
|Memory||Varies, depending on the environment.
Suggested value: Minimum 1GB.
|Hard Disk Space||Approximately 600 MB of additional hard drive disk space is required to install the cartridge file.|
|Operating System||To ensure the stable performance of the Cartridge for Java EE
Technologies and its agent, your operating system must have the minimum
maintenance patches required to run Java applications. Patch
requirements are available at the following URLs:
AIX 5L 5.3 requires patches to run JDK 1.4.2, 1.5, and 1.6 VMs; see the URL listed above for the latest patch requirements.
Linux: Check for known problems in the release notes and check that the packages they mention are up to date.
Oracle Solaris: http://java.sun.com/j2se/1.4.2/install-solaris.html#notes
|Additional Software||For a list of supported application servers and JDKs, see the Managing Java EE Systems: Supported Platforms and Servers Guide, which can be found in the same location as these release notes.|
The 5.8.0 release is the last major version of the Cartridge for Java EE Technologies that supports Nexus Federation. Support for this feature will be discontinued in the next major release. Quest Software recommends that you do not use the Nexus Federation feature.
Note: Nexus Federation is a separate feature from Foglight Management Server Federation. Support for Foglight Federation will continue. For more information, see the Foglight Federation Field Guide.
Support for the following application servers will be discontinued as of the next full Cartridge for Java EE Technologies release:
These application servers are supported in this release, as documented in the Managing Java EE Technologies Systems: Supported Platforms and Servers Guide. We hope that this notice of planned support changes helps customers plan their upgrades.
This section contains information about installing and operating this product
in non-English configurations, such as those needed by customers outside of
North America. This section does not replace the materials about supported
platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe, and Latin America.
This release has the following known capabilities or limitations: The Cartridge for Java EE Technologies agent property names are not currently localizable. Developer level DEBUG log messages are not localizable.
The Cartridge for Java EE Technologies release package contains the following:
Note: Only the release notes have been updated for this release. The guides remains as they were for version 5.8.0.
For detailed information about installing the Cartridge for Java EE Technologies, see the Managing Java EE Systems: Installation and Configuration Guide.
Get the latest product information, find helpful resources, test the product betas, and join a discussion with the Foglight Quest team and other community members. Join the Foglight Community at http://communities.quest.com/community/foglight.
|Quest Software, Inc.
5 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at www.quest.com/support.
From our Support Portal, you can do the following:
View the Global Support Guide for a detailed explanation of support
programs, online services, contact information, policies, and procedures.
The guide is available at www.quest.com/support.
© 2012 Quest Software, Inc. ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
Refer to our Web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software's trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.
Foglight contains some third party components. For a complete list, see the License Credits page in Foglight online help.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.