このコンテンツは選択した言語では利用できません。
4. Known Issues in JBoss Operations Network 3.1.1
This section contains a subset of the known issues at the time that JBoss Operations Network 3.1.1 was released. When possible, workarounds are provided.
4.1. Upgrade and Installation
When upgrading the server and installed JBoss plug-ins, there may be an error in the logs that one of the plug-in JAR files was corrupted:
2012-08-28 10:31:36,473 ERROR [org.rhq.enterprise.server.core.plugin.PluginDeploymentScanner] Scan failed. Cause: java.lang.Exception:File [/home/jon/jon-server-3.1.0.GA/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins/hornetq-jopr-plugin-2.0.0.Final.jar] is not a valid jarfile - it is either corrupted or file has not been fully written yet.
This appears to happen if there is an EAP instance in the inventory and several different JBoss plug-ins are installed, though it may occur in other situations.
That error prevents the other updated plug-ins deployed in the JBoss ON server's
plugins/ directory from being picked up.
If that error occurs, simply restart the JBoss ON server again. All of the plug-ins will be successfully deployed after restarting another time.
If the installer is not bound to 0.0.0.0 when setting up a server, then it does not set all of the required connection properties. Specifically, the installer does not set the
java.rmi.server.hostname parameter to the real value, and it uses the default of 0.0.0.0. This parameter must be set to the real IP address of the server by manually editing the rhq-server.properties file.
Automatic upgrades of agents on Windows appear to fail. Two conditions must be true for automatic upgrade of agents to work on Windows:
- The agent must be installed and running as a Windows service.
- No Windows Explorer window can be open to any agent subdirectory. Windows sets a lock on directories when they are open, which blocks the upgrade process.
When starting a server while agents are running, the server may log servlet errors in the logs. This is because the remoting (communications) classes are loaded early in the startup sequence, before the server is completely started. This causes some communications interruptions until the server is completely started. These errors can be ignored.
If a JBoss ON server was added to the resource inventory, the old JBoss ON server resource must be deleted from the inventory after upgrade. The old resource entry is unusable after upgrade.
Null pointer exceptions for the
org.apache.catalina.connector.CoyoteAdapter service are returned when the JBoss ON 3.1.1 server is first installed. These errors are harmless and can be ignored. Installation will complete successfully, and both the server and the GUI will start and run properly.
The installer shows non-replaced {} properties.
4.2. JBoss EAP 6 Resources
The tracking bug for all resolved and open issues related to the EAP 6 plug-in for JBoss ON 3.1.1 is Bugzilla 707223.
- The first time that a reload is run on an EAP 6 resource after the resource is imported into the inventory, an exception is thrown in the UI.The reload operation completes successfully and subsequent reload operations do not throw an exception.
- When an EAP 6 server is running in domain mode with the full-ha profile, unsetting the proxy URL to save a null value fails with the error We got a 500 with the following response body back. Setting the proxy URL to a different value (not null) is successful.
- Bundle provisioning is only available for EAP 6 standalone servers. Standalone servers use a filesystem-based deployment directory, which is used by the bundle system. Domain resources use a different, distributed style of deployment. The domain style of content distribution is not supported for bundles.
- When running a group of operations in a specific order on a server group, attempting to open the operations schedule returns a null pointer exception.
- When editing a network interface for a JBoss EAP 6 server, the network configuration requires either a specific IP address or a setting to use any IP address for IPv4, for IPv6, or any address. However, the UI does not enforce that an IP address selection is made, which can cause the interface to be unreachable.
- Attempting to deploy a child resource such as a WAR application fails with a malformed URL exception if the EAP 6 server is listening on IPv6.
- Some path elements defined in the configuration of a domain controller or standalone server are computed by the server itself. These computed paths are all prefixed with
java.*,jboss.*, anduser.*.While the configuration values are viewable, they are not editable. However, the Configuration tab for the server shows both edit and delete options for the path elements. If a user attempts to change or delete the path, the path simply reverts to its previous state. - When a child JVM definition is created for a managed resource, the name of the JVM definition must be the same as the host JVM definition which it is based on. However, the JBoss ON UI creation wizard does not detect or enforce a pre-computed name, so it allows a user to enter any name.
- The UI will not let users enter a driver name when manually adding a datasource, so it is not possible to deploy a module-loaded driver.
- The agent properly detects an EAP 6 server running over an IPv6 address, but it incorrectly reports it as offline.
- It can take several minutes to be able to detect a child resource on a JBoss EAP 6 server.
- If both an EAP 6 server and a JDG server are running on the same system, the EAP 6 child resources are detected and added as (unavailable) child resources of the JDG instance.
4.3. Server Configuration
The password mechanism in the server installer doesn't properly hash Unicode characters. The Unicode characters are translated into the HTML entities, and then the HTML characters are hashed and stored as the password.
For example, the string
你好 is treated as the string 你好 in the installer, and the second string is the one that is hashed and stored in the rhq-server.properties file.
After configuring the server, but before logging in, manually update the password in the
rhq-server.properties file:
- Manually generate a hashed password based on the Unicode password:
serverRoot/jon-server-3.1.1.GA/bin/generate-db-password.sh 你好 Encoded password: 68f725778bb36d3b
- Replace the database password value with the new hashed password.
rhq.server.database.password=68f725778bb36d3b
4.4. Agents
Attempting to use the
config import command in the agent command prompt fails with an InvalidPreferencesFormatException exception.
java.util.prefs.InvalidPreferencesFormatException: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 41; Document root element "preferences", must match DOCTYPE root "null". ...
The JVM can sometimes cause the agent to crash when Augeas is running.
A fatal error has been detected by the Java Runtime Environment ...
4.5. Databases
The agent assumes that PostgreSQL uses a default password. If a different password is used, the PostgreSQL resource is shown as unavailable in the UI even if it is running.
4.6. Groups
A dynagroup definition with a short recalculation interval (less than two minutes) can cause duplicate groups to be created.
Changing the recursive setting on a group disassociates the group from any roles it was (previously) associated with.
4.7. Provisioning
Hot deployment fails if the file changes during provisioning.
If a bundle is being deployed in a hot deployment and one of the underlying bundle files, like a WAR or JAR, is changed while the bundle is being uploaded, then provisioning will fail.
The
<rhq:system-service> Ant tag only works on Red Hat Enterprise Linux systems. Using the tag and then deploying the bundle to other operating systems causes the Ant task to fail to operate and can cause the deployment to fail.
4.8. Content and Repositories
A repository can only be used for one resource, the one it was initially defined for.
Attempting to delete a repository with a space in the name throws an exception and the deletion fails.
Deploying WARs from a content repository is not supported. WARs and EARs should be deployed using bundles.
Deploying an exploded archive on JBoss EAP 4 results in deploying a zipped archive, which makes the deployed application unavailable.
4.9. Remote API and the CLI
ResourceFactoryManager does not throw any exceptions when attempting to create duplicate or invalid resources in the CLI.
The JBoss ON remote API cannot be used to connect to the JBoss ON server when the client is running inside an application server. For example, the remote API cannot be run from a client inside an EAP instance; it fails with errors like the following:
Caused by: java.lang.IllegalArgumentException: interface org.rhq.enterprise.server.auth.SubjectManagerRemote is not visible from class loader at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581) at org.rhq.enterprise.client.RemoteClientProxy.getProcessor(RemoteClientProxy.java:69)
4.10. UI
Problems with Sessions and Multiple Tabs
If there are multiple tabs open to the JBoss ON UI and one of those sessions times out, then the other tabs will register errors. This can also occur if multiple people are logged into JBoss ON as the same user.
Searching for a resource with a backslash (\) in the name returned no results, even if the resource exists.
Bugzilla 736732: Bookmarked UI Pages May Display the Old UI
The page names used for different pages in the JBoss ON UI for version 3.0 are different than the ones used in JBoss ON 2.4. However, because JBoss ON 3.0 retains some of the elements used in the older JSF-based UI, these pages still exist. This means that bookmarks will go to the old style pages.
For example, the Dashboard page in the old JSF UI had the URL http://localhost:7080/Dashboard.do/. In the new UI, the location is http://localhost:7080/coregui/#Dashboards.
All of the new pages have the
coregui/ element in them. Remove any old bookmarks and replace them with the new GWT-based pages in the coregui/ area.
When the results for a dynamic search are long, the list is truncated but no scrollbar is presented, so it is not possible to scroll to the end of the list.
4.11. Operations
Attempting to run an operation on a resource without parameters immediately after running an operation with parameters can fail with an error that the second operation did not have the required parameters set, even though there are no required parameters.
4.12. Measurements and Monitoring
A user-defined baseline value for a metric is ignored and overwritten by the server-calculated baseline.
4.13. Alerts
Attempting to upload a CLI script directly to a repository to use for alerting fails because it says the SHA-256 checksum for the script is not an OSGi string. Uploading a CLI script through the alert configuration UI works successfully.
In Oracle, the alert notification table is created with the NOLOGGING option. This means that users are required to review the alert notification configuration manually for every alert to verify that the configuration is correct.
Alerts with compound AND conditions can incorrectly fire when one of the conditions goes from true to false within 30 seconds of the other condition going from false to true.
Alert conditions and alert notifications in an alert definition cannot be edited. The condition or notification must be deleted and a new item added.
Recovery alerts are not triggered by an availability condition.
4.14. Drift
Drift definitions can be created for resources which do not support drift, using the remote API to create a script.
Drift monitoring is not supported for embedded web applications, only for standalone applications.
4.15. Platform Resources
The inventory for a Linux platform may discover non-existent network adapters, which are added and then shown as unavailable in the inventory.
4.16. Tomcat Resources
If a WAR file is configured to be deployed to a non-standard location on a Tomcat application server, an invalid deployment name is added to the inventory. The
unpackWARs option extracts the web app to a second, invalid directory. For example, if it should be extracted to /myapps/helloworld, the web app is extracted both there and to /myapps#helloworld.
The agent cannot discover a Tomcat instance if its Java process is running as a user other than the system user that the agent is running as.
4.17. Apache Resources
Editing any option in the directory inside an Apache virtual host fails with this error:
2012-08-07 15:32:10,835 ERROR [ResourceContainer.invoker.nonDaemon-4] (org.rhq.plugins.apache.ApacheDirectoryComponent)- Augeas failed to save configuration
When trying to add a second entry for the Allow Override directive in an Apache directory resource, deselecting the Unset checkbox for the Param field returns a globally uncaught exception.
Apache directives are case-insensitive, but the Apache plug-in treats them as if they were case-sensitive. This makes the plug-in disregard directives with non-default case.
If the
/tmp directory is configured a noexec in the fstab file, the agent throws exceptions because it cannot properly initialize the Augeas lens. In that case, the Configuration tab is unavailable for the Apache resource.
To work around this, make sure that the
/tmp directory does not have noexec set as an option.
# # /etc/fstab # tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0
noexec is one security method available to that directory to prevent unauthorized or malicious scripts from running. Disabling noexec for the directory is not ideal, but it is also not a security issue by itself because other filesystem security settings can be used.
4.18. BRMS Resources
BRMS 5.1 applications are discovered fine, but BRMS 5.2 and 5.3 applications are not discovered automatically by the BRMS plug-in. The applications must be added manually as child resources.
4.19. JBoss and JVM Resources
If two EAP 5 resources are shut down more or less at the same time on the same platform (agent), then the max wait time of the second, later operation overrides the max wait time of the first shutdown operation. This can cause problems if the wait time on the second resource is significantly shorter or longer than the other resource.
Initiating a shut down operation a stopped EAP instance through JMX results in a (proper) failure message, while attempting to shut down a stopped EAP instance using the
shutdown.sh script shows an incorrect success message.
If EAR, WAR, or script resources are deleted outside of JBoss ON, the agent throws an exception during discovery, and the server is not informed that the resource was deleted.
Discovering a JBoss AS instance fails if the configuration directory is a URL.
The discovery process fails to determine the JNP URL if the data directory is not located at ${jboss.server.home.dir}/data.
Shutting down a JBoss AS 5 resource can fail with java.rmi.NoSuchObjectException: no such object in table.
The JBoss AS plug-in is unable to load resource configuration for JMS queues that are deployed using a SAR file.
The discovery process attempts to discover an embedded JVM process through its JMX remoting rather than using the EMSConnection of its parent Tomcat or JBoss resource.
4.20. Performance
Attempting to update the members in a compatible group with thousands of members times out and fails with 'Failed to fetch Resource Group.'
Viewing configuration, alerts, or other data for groups with more than 1000 members can fail with the SQL exception maximum number of expressions in a list is 1000.
4.21. Plug-in Writing
If an embedded plug-in extension is defined and the parent resource type has subcategories, those subcategories cannot be changed or it causes a database deadline.
