The following is a list of issues addressed and enhancements implemented in this release.
|
Defect ID |
Resolved Issue |
| FAPM-1217 | After switching an instrumented Tomcat JVM from Oracle JVM to IBM JVM, the Code Cache, Compressed Class Space, Metaspace, PS Old Gen, PS Eden Space, and PS Survivor Space metrics show on the UI, but without data. |
| FAPM-1216 | The nodes cannot be transformed or explicitly ignored by the transform specification during the startup of Tomcat server, when running Tomcat on IBM JVM 1.7 and IBM JVM 1.8. |
| FAPM-1206 | Preinstrumentation throws a VersionedConfigNotFound Exceoption when Tomcat is running on IBM JDK 1.8. |
| FAPM-1174 | Invoke the getServerNumber() method to return the Tomcat Server version, if the getServerInfo() method does not take effects. |
| FAPM-1164 | The maximum active connections of datasource cannot be collected on Tomcat 8.0.36 and Tomcat 8.0.37. |
| FAPM-1138 | The Recording Settings entries cannot be deleted from either the .Net Administration dashboard or the Nexus Administration dashboard. |
| FAPM-1007 | The Cache metric, namely cacheAccessCount of web applications, cannot be collected on Tomcat 8.0.22, Tomcat 8.0.36, and Tomcat 8.0.37. |
| FAPM-884 | There are lots of duplicated Work Managers in the Work Managers dashboard. |
| FAPM-848 | The NullPointerException is thrown by WebLogic10EjbInfoInstrumentor while starting WebLogic. |
| FAPM-602 | The metric "allMessageCount" of JBossJMSTopic is not collected starting with JBoss 6. |
| FAPM-327 | The status of Systems, Servers, and Applications are not getting synced in the child server. |
| STRACE-2024 FAPM-266 |
When a new application is deployed to a running instrumented WebSphere app server, the Components metrics and EJB metrics can't be collected until the instrumented server is restarted. |
| FAPM-100 STRACE-2058 |
When downloading the agent log file through the Agent Status dashboard, an error occurs if the agent name contains spaces. |
| FAPM-58 | JNDI name of the stateful session beans cannot be collected and displayed on the Stateful Session Bean Instances dialog. |
| FAPM-46 | Message in Queue Time is missing. |
| FAPM-45 | UI mappings "Max Waiters" and "Max Size" in System Thread Pools are incorrect. |
| FAPM-26 | The EJBs of the JBoss Application cannot show up in the Application table in the Application Servers Monitor dashboard. |
| FAPM-13 | "Message Recceived" on EJB MDB for JBoss 7.x is missing. |
| FAPM-12 | System Thread Pools Metrics for JBoss EAP 6.x are missing. |
| FAPM-9 | EJB Stateful Session Bean metrics for JBoss are missing. |
| FAPM-6 | EJB entity bean for JBoss 7.x cannot be collected. |
| FAPM-4 | Metrics of the JCA Resources for JBoss EAP 6 are missing. |
The following is a list of issues known to exist at the time of this release.
|
Defect ID |
Known Issue |
|
FAPM-1272 |
After excluding a server in the ModelFilters configuration, the Weblogic securityRealm metrics still pass through. |
| FAPM-1248 | The Active Version ID and Version ID metrics are missing in the Resource Adapter Instances table. |
| FAPM-1204 | After a Tomcat server is updated to run in the standalone mode, the data of this Tomcat server is still being shown in the cluster in which the Tomcat server is instrumented previously. |
| 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-1199 | There are duplicate objects being collected after adding an instrumented Tomcat server 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-1126 | There is no recording.config data displayed on the Nexus Administration dashboard. |
| FAPM-1121 | The Execution Time, Dispatch Time, and Response Time metrics are missing in the WebLogic Web Service Operations table. |
| FAPM-1061 | The WebLogic Discovery Collector still collects some amount of information about managed servers even though the remote collection of managed server runtime metrics has been disabled. That is, topology of managed servers still be created even though managed servers are not instrumented. |
| 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-890 | The WebSphere server fails to start if the server JVM version is different from the JVM version of its profile. |
| 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-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. |
|
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.9.
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.9. 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.9:
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.59, 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.
