The following is a list of issues addressed and enhancements implemented in this release.
|
Defect ID |
Resolved Issue |
|
CAC-760 |
Enhance the |
|
CAC-759 |
Enhance the |
|
CAC-755 |
On the Single Traces view (from the Application Servers Monitor dashboard), the Fast Find feature does not work on Foglight Management Server version 5.7.1. |
|
JEE-9207 |
On the Application Server Monitor dashboard, users can now select individual application servers and applications, in addition to domains, when they create a service. The service can now also be reused locally or globally. |
|
JEE-9136 |
When integrating an application server that has a Windows service, the service fails to start if there are certain characters in the registry. |
|
JEE-8913 |
Supported integrations with renamed or removed parameters fail to load after an upgrade. |
|
JEE-8216 |
Improved the performance of the Application Servers Monitor dashboard. |
|
STRACE-2038 |
Enhance the availability metric calculation for WebLogic Servers. |
|
STRACE-1998 |
Tomcat 8 running on Java 8 produces the following exception: |
|
STRACE-1932 |
Support for JBoss EAP 6.4.4. |
|
STRACE-1927 |
Support for Oracle® WebLogic 12.2.1 (12c). |
|
STRACE-1912 |
A JBoss AS 7 agent fails to start when |
|
STRACE-1906 |
A JBoss server in domain mode with agent instrumentation persists a 'restart warning' in the JBoss admin console and server console. |
|
STRACE-1848 |
Support for Oracle WebLogic Server 12.1.3. |
|
STRACE-1841 |
Support for JBoss EAP 6.4.0 |
The following is a list of issues resolved in hotfixes issued for the previous release. These issues are also fixed in this release.
|
Defect ID |
Resolved Issue |
|
STRACE-2019 |
Servlet and application metrics are not collected for applications that specified an Application Edition with the Application Name during deployment on WebSphere Application Server versions 8.5.0.0 and later. |
|
Defect ID |
Resolved Issue |
|
FGL-17923 |
Data for newly monitored objects (application servers or request type) may fail to display in the dashboards. This issue occurs on Foglight Management Server 5.7.1 and might be noticed after upgrading Foglight for Java EE. This issue was fixed in Foglight Management Server 5.7.5. |
|
STRACE-1960 |
During a Foglight for Java EE installation or upgrade, agents that belong to other cartridges and are versions 5.1.x or 5.2.x might be accidentally deleted. |
|
STRACE-1939 |
Agent fails to start if JBoss® EAP 6.0.x to 6.4.x has one-off patch installed. |
|
Defect ID |
Resolved Issue |
|
JEE-9155 |
Changed data processing to prevent false alarms for WebLogic Servers. |
|
JEE-9030 |
Prevent the agent for the WebLogic Admin Server from duplicating metrics collection for managed servers. |
The following is a list of issues resolved in a previous release for a component that is common to Foglight for Java EE and Foglight for Microsoft .NET. These issues are fixed in this release.
|
Defect ID |
Resolved Issues |
|
CAC-756 |
The CDT throws a NullPointerExpression while it is processing an ExternalSystem node. |
|
CAC-753 |
An IllegalArgumentException causes data to be dropped when the Foglight Agent Manager (FglAM) is restarted. |
The following is a list of issues known to exist at the time of this release.
|
Defect ID |
Known Issue |
|
JEE-9233 |
The Application State alarm still fires when |
|
STRACE-2077 |
If the instrumentation configuration for JBoss server agent in domain mode is changed a fatal error occurs. Workaround: Restart the JBoss EAP application server after making instrumentation configuration changes. |
|
STRACE-2058 |
When downloading the agent log file through the Agent Status dashboard, an error occurs if the agent name contains spaces. |
|
STRACE-2056 |
After deploying the Java agent from the Foglight APM appliance, data collection fails. |
|
STRACE-2048 |
After excluding a server in the |
|
STRACE-2040 |
During startup, the agent cannot detect the Tomcat version number and fails. Workaround: Use the |
|
STRACE-2039 |
JavaIntegrator Agent records suffer delivery delays or go missing altogether. |
|
STRACE-2024 |
When a new app is deployed to a running instrumented WebSphere application server, the Components metrics and EJB metrics cannot be collected until the instrumented server is restarted. |
|
STRACE-1802 |
JBoss EAP 6.3.0 throws a |
|
STRACE-1791 |
When the WebLogic server ClassCache is enabled, a |
|
STRACE-1785 |
Some performance loss may occur when using a combination of |
|
STRACE-1651 |
Support for JBoss server in domain mode can be enhanced to consider domain-specific options. |
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.8.
Important: There is a known issue with Foglight Management Server 5.7.1 that might occur after upgrading Foglight for Java EE. Newly monitored objects may fail to display in the dashboards. If this issue occurs, a workaround is available in Knowledge Base article 152648 available at https://support.quest.com/foglight/kb/152648.
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.8. 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.8:
The following Foglight product versions and platforms are compatible with this release.
|
Product Name |
Product Version |
Platform |
| Foglight Management Server | 5.6.7 and later | All Platforms supported by this version of the Foglight Management Server |
| Foglight Agent Manager Note: The monitoring agents available in this version of Foglight for Java EE do not support the Agent Manager HA failover mode. For more information about this mode, see the Agent Manager Guide. |
5.6.7.2 Version 5.6.7.3 and later is recommended |
All Platforms supported by this version of the Foglight Agent Manager |
Foglight for Java EE Technologies must be deployed on a Foglight Management Server version 5.6.7 or later, and to a Foglight Agent Manager version 5.6.7.2 or later. For information about system requirements for this release, see the Foglight for Java EE Technologies Supported Platforms and Servers Guide.
Before installing Foglight 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 Foglight for Java EE Technologies 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 Foglight 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: http://www-106.ibm.com/developerworks/java/jdk/aix/service.html AIX 5L 5.3 requires patches to run JDK 1.5, and 1.6 VMs; see the URL listed above for the latest patch requirements. HP-UX: http://ftp.hp.com/pub/softlib/hpuxjava-patchinfo/index.html Linux: Check for known problems in the release notes and check that the packages they mention are up to date. Oracle Solaris: http://www.oracle.com/technetwork/systems/patches/solaris/index.html |
| Additional Software | For a list of supported application servers and JDKs, see the Foglight for Java EE Technologies Supported Platforms and Servers Guide, which can be found in the same location as these release notes. |
Support for the following application servers and OS platforms will be discontinued in the next major version release:
These operating systems are supported in this release, as documented in the Foglight for Java EE Technologies Supported Platforms and Servers Guide. We hope that this notice of planned support changes helps customers plan their upgrades.
