Knowledge Base

• Known Issues
• Limitations

Known Issues

1. While authenticating a WebLogic Server version 7.0.x, if you specify a wrong version, data collection will not happen and no error message will be shown. Also, "Assertion Failed" exception will thrown in the WebLogic Server console. Restart the Applications Manager server and authenticate again.
2. When a query, as part of a transaction, is executed as a batch on the WebLogic Server, its corresponding individual SQL statements cannot be determined and shown in the GUI.
3. For Alarms that are not configured to be analyzed for root causes by default, you can view the list of probable causes only for a period of ten minutes from the time the Alarm was generated.
4. Dashboard Components of multiple Applications cannot be added to a single Dashboard. In other words, a custom dashboard can contain components pertaining to the same application. For example, dashboard components of WebLogic and Oracle Servers cannot be added to a single dashboard.
5. After creating a custom dashboard for an Oracle application, a NullPointerException will be thrown in the client logs. This is a harmless exception and is thrown because the tree node selection for the newly added dashboard does not happen. However, the dashboard can be viewed by clicking on the dashboard name node from the tree panel.
6. Data collection of all the configured JOLT connection pools will happen even if the target for the connection pool is not set.
7. WebLogic Servers has to be restarted every time you deploy a performance-enabled EJB through the J2EE Performance Tool. In case of distributed environment, all the WebLogic Servers of that domain have to be restarted.
8. In distributed environment, the config.xml of the admin server should have the relative path of the applications that are deployed in the managed servers.
9. Servlet node for the Web Applications deployed during runtime will not be added. However, the details of the servlets of that Web Application can be viewed from the WebLogic Systems view of that resource.
10. Using Console Builder, when the count of MBeans fetched is high, CPU will shoot to 100% occasionally.
11. "Assertion Failed" error with ClassNotFoundException will be thrown during redeployment of EJB archives from the J2EE Performance Tool in WebLogic Server 6.1+ any SP. Stop the WebLogic Server, edit the config.xml, and set the deployed attribute to "true" for the respective EJB Application tag and restart the WebLogic Server.

Limitations

1. Oracle monitoring will not be performed if an oci driver is used to establish connection.
2. While starting WebLogic Server 7.0, a system variable should be specified as an argument as -Dweblogic.disableMBeanAuthorization=true. Also, the user name and password specified while authenticating WebLogic Servers 7.0 for data collection do not have any impact on data collection but they are required for EJB Performance Configuration. Hence, specify correct user name and password.
3. The Statement profile count shown in the JDBC details are for that domain and not specific to that connection pool
4. Redeployment of JMX Agents from J2EE Performance Tool for WebLogic Servers in distributed environment is not supported.
5. While generating Graphs for custom applications, in a single Graph Wizard, only two components can be selected.
6. In Console Builder, generating screens for multiple agents from the same project is not supported.
7. Deployment of screens and graphs with the same project name from two different hosts to the same Applications Manager is not supported.
8. While deploying Screens, if the JMX Agent connected is not the same as the one for which the Screens were generated, there will be no check or stop. The Screens will be deployed but might not return the desired values.
9. Screens cannot be generated for the WebLogic MBeans, as some of the classes required for the MBeans will not be available in the classpath. To fetch the WebLogic MBeans, either update the weblogicclient*.jars with the necessary classes or replace the appropriate weblogic.jar with weblogicclient6_1.jar or weblogicclient7_0.jar present in the <AppManager Home>/ jars directory.
10. Viewing logs of WebLogic Server 7.0 is not supported.
11. Web Transaction view is shown only for transactions that start from a servlet through EJB to a database via JDBC.
12. In distributed environment, if you deploy agents in more than one WebLogic Server, the EJB performance will be available only for the latest deployment.