The following is a list of issues addressed and enhancements implemented in this release.
|
Defect ID |
Resolved Issue |
| FAPM-1554 |
Fixed the issue where the system._javaee_applications.scripts.getserverrequestsexceptionalexitcount function threw a NullReferenceException. |
| FAPM-1543 |
Fixed the issue where the unit of Current Active Connections (%) in Quick View was incorrect. |
| FAPM-1510 | Fixed the issue where the value of ActiveConnectionUsedPercent was always zero. |
| FAPM-1497 | Fixed the issue where the value of Current Active Connections (5) in Datasource Quick View was unavailable. |
| FAPM-1474 | Support adding Java agent package to Felix OSGi bootdelegation for runtime permission. |
| FAPM-1466 | Changed the UpdatePage property to false for ProgressTracker, to prevent the AppServer Admin dashboard from refreshing repeatedly. |
| FAPM-1465 | Java X-Agent could not collect application requests for Glassfish 4. |
| FAPM-1422 | There was no agent message indicating the server reload is required when statistics are enabled on Wildfly 8 domain mode. |
| FAPM-1412 | Removed the scroll bar in the Server panel of JBoss. |
| FAPM-1356 | The number of Request Types in the Request Perspective tab is incorrect. |
| FAPM-1352 | Tomcat servers are not clustered in the deployment list of applications. |
| FAPM-1336 | Failed to collect the State metric of JMS Servers when the server version is Weblogic 8. |
| FAPM-1334 | Failed to collect the Datasource metric when the server version is Weblogic 8. |
| FAPM-1332 | Failed to collect the Responses metric when the server version is Weblogic 8. |
| FAPM-1329 | Failed to collect the Connector, Deployed, and EIS ID metrics of Resource Adapter Instances when the server version is Weblogic 8. |
| FAPM-1272 | After excluding a server in the ModelFilters configuration, the Weblogic securityRealm metrics still pass through. |
| FAPM-1204 | Tomcat server still shows in the TomcatCluster group even if this server is not included in the cluster any longer. |
| FAPM-1199 | There are duplicate objects being collected after adding an instrumented Tomcat server into a cluster. |
| FAPM-1148 | An error message reports when the pre-instrumentation of IBM JDK 1.8 is complete. |
| FAPM-890 | The WebSphere server fails to start if the server JVM version is different from the JVM version of its profile. |
| FAPM-267 JEE-9156 STRACE-1964 |
The state of non-instrumented managed server is always unknown after adding -Dquest.agent.weblogic.admin.collect.managed.servers=true to PERFORMASURE_OPTIONS in the startup script of the admin server. |
The following is a list of issues known to exist at the time of this release.
|
Defect ID |
Known Issue |
|
FAPM-1604 |
Error related to Weblogic.rjvm occurs when integrating with Weblogic server 12.2.1.2 on Windows and Linux platforms. |
|
FAPM-1557 |
The unit of Datasource - Current Active Connections in Quick View is not updated after upgrading to the 5.9.10 release of Foglight for Java EE Technologies. |
|
FAPM-1555 |
Fails to add SeparationRules in the rocording.config file, if the value of Separation Parameters is empty. |
|
FAPM-1551 |
The java.io.IOException error message appears in the agent log when monitoring Glassfish v4.* with Generic-Agent. |
|
FAPM-1548 |
After moving a clustered Tomcat server out from the cluster, there is no Methods metric shown in the Tomcat server table. |
|
FAPM-1509 |
X-Agent of Glassfish cannot trace the requests of Glassfish 4 and web console. |
|
FAPM-1503 |
WebSphere application server fails to collect the JPA metrics. |
|
FAPM-1496 |
The xml-file implemented JPA methods cannot be treated as EJB methods. |
|
FAPM-1495 |
The Admin server startup console includes some noise messages when instrumenting Oracle Weblogic 12.2.1.1. |
|
FAPM-1491 |
Fail to monitor JBoss datasources that are defined in the WAR file. |
|
FAPM-1490 |
Fail to collect HTTP post parameters for JBoss EAP 7. |
|
FAPM-1477 |
WebSphere Application Server fails to collect the web services. |
|
FAPM-1471 |
Fail to collect JMS requests with EJB annotations on IBM JDK 1.8. |
|
FAPM-1454 |
The Datasource name metric cannot be collected when the Hibernate version is later than 4.2. |
|
FAPM-1407 |
If ServletResponse.reset() is called, the response loses its Foglight UUID header. |
| FAPM-1200 | The methods of a Tomcat server can be collected and shown on the user interface when this server is running in the standalone mode. However the methods of this server cannot be shown after this server is being added into a cluster. |
| FAPM-1197 | If Tomcat server accesses the application through HTTP/2 connection, an error message saying "An unexpected error occurred which may cause undesired behavior. You may want to contact customer support if you see this error again" can be found in the agent log. |
| FAPM-1193 | The Replication Mode metric of the Tomcat clusters cannot be collected starting from Tomcat version 6.x. |
| FAPM-1188 | The Time, End Time, and Length metrics of Aggregated Traces for a Tomcat server cannot be collected. |
| FAPM-1009 FAPM-87 |
The "UndeclaredThrowableException" error occurs when deactivating/activating Nexus if the debug level is set to 2, or when a new Nexus cartridge gets installed over a Nexus running on the debug level 1. |
| FAPM-876 | The integration result is inconsistent after integrating Server A that does not have standalone applications with Server B that has one standalone application. |
| FAPM-780 | WebSphere Application Server fails to collect SIB information. |
|
JEE-9233 |
The Application State alarm still fires when |
|
STRACE-2077 FAPM-264 |
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-2039 FAPM-357 |
JavaIntegrator Agent records suffer delivery delays or go missing altogether. |
|
STRACE-1785 |
Some performance loss may occur when using a combination of |
|
STRACE-1651 FAPM-579 |
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.10.
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.10. 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.10:
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 hotfixes required to run Java applications. Hotfix requirements are available at the following URLs: AIX: http://www-106.ibm.com/developerworks/java/jdk/aix/service.html AIX 5L 5.3 requires hotfixes to run JDK 1.5, and 1.6 VMs; see the URL listed above for the latest hotfix 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. Note: As IBM® WebSphere® Application Server supports IBM JDK 1.8 since version 8.5.5.9, Foglight for Java EE Technologies is now adding the support for IBM WebSphere Application Server 8.5.5.9 and later on IBM JDK 1.8. |
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.
