The following is a list of issues addressed and enhancements implemented in this release.
|
Defect ID |
Resolved Issue |
| FAPM-2311 |
Exception java.lang.NoClassDefFoundError throws when using "OSGI" framework for WebSphere server(8/9) Java agent. |
| FAPM-2292 |
Fixed an issue where WebLogic with IBM JDK 1.8.0_151 fails to start after instrumentation. |
| FAPM-2278 |
Fixed an issue where JBoss with IBM JDK 1.8.0_151 throws ClassFormatError after instrumentation. |
| FAPM-2277 | Fixed an issue where Tomcat with IBM JDK 1.8.0_151 fails to start after instrumentation. |
| FAPM-2274 | Fixed an issue where WAS liberty throws ClassFormatError after instrumentation With IBM JDK 1.8.0_151. |
| FAPM-2236 | Fixed an issue where Version field in appserverinfo flag cannot distinguish "AS" vs "EAP versions of JBoss". |
| FAPM-2195 | JBoss agent supports config file with EXPRESSIONS of numeric values. |
| FAPM-2186 | Fixed an issue where the metric Acquisition Time did not show in Resource Adapters view of JBoss. |
| FAPM-2180 | Fixed an issue where data of specific MBean could not be collected. |
| FAPM-2173 | weblogic.rjvm.BasicOut boundRequest error occurs when integrating WebLogic 12.2.1.3.0 with Foglight for Java 5.9.13. |
| FAPM-2154 | WebSphere fails to start up due to WebSphereEjbInfoInstrumentor.undeployCallback method not found. |
| FAPM-2151 | WebSphere Windows Service could not start after integration. |
| FAPM-2149 | WebSphere Webservice warning messages show in the agent log file. |
| FAPM-2135 | Fixed an issue where the build ID in the Nexus Advanced Configuration dashboard was not up-to-date. |
| FAPM-2082 | Fixed an issue where WebLogic LVT error happened in environments installed WebLogical 10.3.6.0.170418 and Java 1.7.0_141 (64 bit). |
| FAPM-2037 | Improved constraint validations for JBoss7JdbcInfoInstrumentor. |
| FAPM-2018 | WebSphere 8.0: The "Instrumentation constraint violated" error shows in the log, after upgrading the Foglight for Java EE Technologies version from 5.9.7 to 5.9.12. |
| FAPM-1985 | Fixed an issue where JBoss7JdbcInfoInstrumentor failed on JBoss EAP 6.4.15. |
The following is a list of issues known to exist at the time of this release.
|
Defect ID |
Known Issue |
|
FAPM-2297 |
WebLogic: When deploying an application on a cluster server in which selects "All servers in the cluster", this cluster server status will display "Prepared" or "New". This issue would not happen if the cluster server is set to "Part of the cluster". |
|
FAPM-2296 |
Exception java.lang.NoClassDefFoundError throws when using "OSGI" framework for JavaEE agent (excluding X-Agent and WebSphere). |
|
FAPM-1923 |
The Manage Config dashboard shows no data, if the value of configName is not set for an agent. |
| FAPM-1802 | Bootstrap jar needs to be regenerated manually, if Java version changes or new agent version upgrades. |
| FAPM-1800 | WebSphere Internal applications still appears on the user interface, after upgrading from release 5.9.10 to 5.9.11. |
| FAPM-1799 | The "Original Subject has already been retrieved - despite this error, data collection will continue normally" error shows in the WebSphere error logs. |
| FAPM-1777 | The Java target cannot be deleted after performing the action of "Delete and undo the integration". |
| FAPM-1765 | Some Java Nexus connections cannot be deleted as expected. |
| FAPM-1740 | More memory is needed after enabling CustomComponentInstrumentor with debug level 2. |
|
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 recording.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-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-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.13.
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.13. 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.13:
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 these versions 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 these versions 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. |
The following JDKs and application servers are not supported:
These application servers 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.
The following operating system (OS) platforms are not supported since this 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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center
