The following is a list of issues addressed and enhancements implemented in this release.
|
Defect ID |
Resolved Issue |
| CAC-750 | No requests seen on the Foglight Management Server dashboard when Named Methods are configured. Several CDT errors flood the Management Server logs. |
| JEE-9038 | Added support for JBoss EAP 6.3.3. |
| JEE-9031 | Added support for WebLogic 12.1.3 |
| JEE-9029 | The pre-instrumentor fails on JDK 1.4.x with the Foglight for Java EE Technologies 5.9.7.3 patch. |
| JEE-9026 | JMS queue data collection fails with the Foglight for Java EE Technologies 5.9.7.2 patch. |
| JEE-8964 | A LinkageError occurs when any JBoss application using a transactional datasource whose JDBC drivers are loaded through a global module. |
| JEE-8958 | Added support for Tomcat 8. |
The following is a list of issues resolved in patches issued for the previous release. These issues are also fixed in this release.
|
Defect ID |
Resolved Issue |
| CAC-741 | High CPU usage occurs on the Agent Manager where the Nexus agent is running. |
| CAC-738 | During the Agent Manager startup cycle, errors appear indicating that the Nexus agent cannot be started. The Nexus agent does eventually start. |
| CAC-737 | A NullPointerException appears in the Nexus logs, sometimes causing the Nexus agent to stop data collection. |
|
Defect ID |
Resolved Issue |
|
JEE-8957 |
Added support for JDK 1.8. |
Version 5.9.7.1 was a re-release of version 5.9.7 solely for the purpose of matching version numbers with the Foglight for Microsoft .NET 5.9.7.1 release. Installing this version avoided version mismatch warnings when installing both Foglight for Java EE Technologies and Foglight for Microsoft .NET.
|
Defect ID |
Resolved Issue |
| CAC-713 | Removed a rule that could cause topology churn and poor performance when deployed on Foglight Management Server Federation Master Servers. |
| CAC-701 | Improved the performance of the Application Server Administration dashboards. |
| CAC-699 | If the Nexus runs out of memory, the Agent Manager (FglAM) restarts automatically to correct the issue. |
| CAC-698 | When a Nexus had many agents connected to it, the app server startup time was slower than usual. |
| CAC-685 | Added a UUID transform in the URL transform rules to reduce the number of request types created by UUIDs in the URL. |
| CAC-374 | StackOverflowErrors in the Nexus when processing requests with deep call trees can be resolved by adding the "-Xss" option to the Nexus Foglight Agent Manager's (FglAM) JVM options to increase the stack size. The Win64 default of 128K is sufficient in our tests for call trees of 300 nodes. The defaults for various platforms can be found here: http://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionX.html#wp1024112 |
| CAC-257 | Read the topic "Before You Begin the Installation Process" in the Managing Java EE Systems: Installation and Configuration Guide before you install the cartridge for important information about embedded Foglight Agent Manager settings. |
| JEE-8853 | Fixed an issue that was causing the Tomcat application state to display incorrectly. |
| JEE-8850 | Fixed an issue that was causing the server state icon to switch between Available and Unknown. |
| JEE-8837 | The log file name for WebLogic agents was not unique when there were multiple WebLogic domains on the same host. |
| JEE-8836 | Fixed an issue that was causing the agent display name for WebLogic to not contain the WebLogic domain name. |
| JEE-8831 | Fixed an issue that was causing the time range to fail to update on all tabs of the JVM views. |
| JEE-8811 | Improved agent performance. |
| JEE-8807 | After upgrading from a version earlier than 5.9 to version 5.9.x, a non-identity property was causing churn in environments where there were similar request URLs on different web apps. |
| JEE-8759 | Fixed an issue that was causing the "delete only" integration option to return a success without performing the deletion. |
| JEE-8755 | Enabled collection of JDBCOracleDataSourceRuntime MBeans for WebLogic. |
| JEE-8720 | The Generic Installation failed if no JAVA_HOME setting was specified. |
| JEE-8602 | The version information for JBoss EAP 6.2 was sometimes displayed as "n/a" in the Application Servers dashboard. |
| JEE-8473 | Implemented a native collector for JBoss EAP 6.1/AS 7.x in order to collect data for stateful session MBeans. |
The following is a list of issues known to exist at the time of this release.
|
Defect ID |
Known Issue |
| CAC-275 | The first time you open the Integrations tab after creating the first integration, the tab may appear empty. Workaround: Toggle the "Show targets only" option to correct the display issue. |
| CAC-259 | When switching the configuration on the Java Administration dashboard, the number of agents affected is not indicated. |
| CAC-93 | After upgrading to version 5.9.x from version 5.8.x, the Java EE agents registered in the JavaEE namespace on the Agent Status dashboard are obsolete and can be deleted. Once the actual agents reconnect to the Nexus, they will be reregistered in the ApplicationServers namespace. |
| JEE-9000 |
In some situations, the configuration file agenttype.config is not updated when Foglight for Java EE Technologies is upgraded. Workaround: The correct agenttype.config file can be installed manually on the Management Server by running the following Groovy script from the Script Console.
|
| JEE-8521 | When running WebSphere 8.5.5.1 with a Domain Manager, an error may be logged with the message "Original Subject has already been retrieved - despite this error, data collection will continue normally". These errors can be safely ignored. |
| JEE-8453 | When the Java Integration Agent attempts to write to the server.policy file, it fails. |
| JEE-8457, JEE-8387 |
When two versions of the same application are deployed on WebLogic, the agent is unable to collect data for servlets/JSPs for them. |
| JEE-8318 | Automatic integration with WebLogic 8.1.x is not supported. To integrate with WLS 8.1.x, create a generic agent installation and then perform a manual integration with the application server as outlined in the Foglight for Java EE Technologies Installation and Configuration Guide or help. |
| JEE-8281 | Setting the cluster name using the appserverinfo flag provides only a method of grouping unclustered Tomcat Hosts under a group name other than "UnclusteredTomcatHosts". It does not turn a standalone Tomcat Host into a cluster, and the deployed applications remain inherently unclustered. In particular, the application names within requests do not carry the information needed to identify the applications cluster, because it does not exist. |
| JEE-8073 | In a monitored WebSphere environment, the number of modulesStarted may be greater than the number of modulesTargeted, which can generate false alarms. |
| JEE-7982 | In some cases, verifier errors occur during instrumentation of classes compiled using a 1.7 JDK. |
| JEE-7960 | Under certain conditions, the state of an application may not be reported reliably. |
| JEE-7941 | The Java EE Agent does not connect to the primary Nexus when the failover Nexus is unavailable. |
| JEE-7881, JEE-7880 |
Foglight for Java EE Technologies does not yet support the Java EE 6 specification, which includes the EJB 3.1 and Servlet 3.0 specifications. Application components developed to these specifications may not be correctly identified as EJBs or Servlets. |
| JEE-7781 | Applications deployed on the WebSphere DM appear, but no metrics are collected for those applications. |
| JEE-7636 | When drilling down from the Domains dashboard, only the corresponding application server type systems should be shown. |
| JEE-7617 | Update the display of object names in various locations (such as, Data-Tree view, Data-Management dashboard, data browser, blackouts page) to provide more meaningful/distinguishable names for major topology objects. |
| JEE-7474 | 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-7370 | Provide monitoring capabilities for WebSphere Dmgr. |
| 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. |
| JEE-7324 | Populate and add a localized description column for the list of available metrics. |
| JEE-7311 | Improve the delta rate calculation. |
| JEE-7146 | The Fast-Find for Exceptions currently gets the first node with exception > 0, instead of the node that actually caused the exception. |
| JEE-7117 | Extend the request transformation feature to non-HTTP requests. |
| JEE-6942, JMX-68 |
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 Foglight Management Server experiences a critical performance slowdown, the Nexus may shut down with a FATAL NullPointerException. |
| JEE-6809 | 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 Children.
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. |
| JEE-6789 | 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-6133 | During CDT recording playback, request data may not be displayed. |
| JEE-4962, JEE-3459 |
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 peer "{0}" 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-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.
|
Defect ID |
Known Issue |
| CAC-318 | Some earlier versions of the JDK 1.7 JRE do not correctly detect Windows 8 or Windows Server 2012. This is a known issue with the JRE reporting "Windows NT (unknown)" in the os.name system property. Updating your JRE to the most recent build should correct the problem. For more information, see: http://bugs.java.com/view_bug.do?bug_id=7170169 |
| JEE-8490 | If you monitor WebSphere Application Server with either an IBM 1.6 or 1.7 JVM, operating system metrics for Committed Virtual Memory or Used Swap Space may not be collected. This is due to the fact that the JVMs do not provide the necessary metrics through the management interfaces. |
| JEE-7930 | When undeploying a web application from JBoss 7.1.0, you may see a NullPointerException logged by JBoss referencing the web application that is being undeployed, with Quest classes in the stack trace. This is caused by our periodic metric collector encountering a bug in JBoss when querying for web application metrics. |
| JEE-7925 | Due to an issue in JBoss 7.1.1, servlet metrics (execution time and invocation count) are not available. See JBoss issue AS7-4404 for details. |
| JEE-7919 | Due to JBoss AS 7 issue AS7-5472, statistics are not available for JBoss 7 datasources. |
| JEE-6785 | JBoss 5 does not provide configuration or metric data for EJB3 Entity Beans. |
| JEE-4991 | 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. |
| JEE-4884 | An IOException error occurs when instrumenting WLS 8.1.6 on Solaris 10 x86-64: Error IOException caught during select. 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.java.com/bugdatabase/view_bug.do?bug_id=6322825 Workaround: To avoid the problem, use one of the following workarounds:
|
| JEE-4102 | 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. Solution: Upgrade to WebLogic 10.3. |
| JEE-3808 | In WebLogic 9.0 and 9.1, the Java agent's attempts to query the state of managed servers causes the error 'Could not execute command "getState" for server "<ServerName>" using the node manager' to be logged for each server that is configured with a machine in the domain config but whose corresponding node manager is not running. Despite the error message, WebLogic still returns the correct state to the agent. Workaround: Ensure that the node manager is running. Upgrading to WebLogic 9.2 also resolves the issue. |
You must upgrade the Foglight Management Server to version 5.6.7 or later before you upgrade Foglight for Java EE Technologies to version 5.9.7.5.
The Nexus requires Foglight Agent Manager is 5.6.7.2. Version 5.6.7.3 or later is recommended.
The Java Integration Agent requires Agent Manager version 5.6.2.2 or later.
The latest version of Foglight for Java EE Technologies is version 5.9.7.5. Upgrades from version 5.8.x and 5.9.x are supported.
Connections from the Java EE Agent versions 5.9.x and 5.8.x are supported. Connections from version 5.7.x, or 5.6.1, or earlier Java EE Agents are not supported.
Compatibility with other Application Server Monitoring products:
To upgrade to version 5.9.7.5:
