Red Hat JBoss Operations Network 3.3 Update 09 (3.3.9) Release Notes
JBoss ON updates are cumulative. You only need to apply the latest update to receive all fixes from the previous updates for the same version.
A server update contains one or more updated server or agent or storage node components which can be applied to a JBoss ON server or agent directory.
Changes and Fixes
This update includes all fixes and changes from Red Hat JBoss Operations Network 3.3 Update 08.
General bug fixes or changes
This update includes the following bug fixes or changes:
| ID | Component | Summary |
|---|---|---|
| This content is not included.BZ-1413088 | Server | Server log warnings from CriteriaQueryRunner: Could not initialize private org.rhq.core.domain.event.EventSource org.rhq.core.domain.event.Event.source [details] |
| This content is not included.BZ-1427571 | Server | Unusable group metric graphs due to fix for BZ-1236021 [details] |
| This content is not included.BZ-1402333 | Server | The "Resource" column is not included while exporting the Alert Definitions in a .csv file. |
| This content is not included.BZ-1429909 | Server | User with Manage Alerts permission unable to delete a Group Alert Definition they created [details] |
| This content is not included.BZ-1447965 | Server | Undertow metrics processing-time, processing-time-per-minute and max-processing time do not scale units in charts |
| This content is not included.BZ-1416097 | Server | Failed to delete the bundles when deleting a bundle with lot of configuration parameters and versions |
| This content is not included.BZ-1401565 | Server | Attempt to navigate to REST interface while server is not still started causes NullPointerException in the server.log file |
| This content is not included.BZ-1444899 | Server | Failure in datasource while processing FETCH request when adding notification to resource group alert definition or to alert definition template [details] |
| This content is not included.BZ-1380471 | Server | UI's live availability check results in repeated "A request timeout has expired after 30000 ms" |
| This content is not included.BZ-1455091 | Server | Error when trying to save agent:SNMP plugin configuration UI [details] |
| This content is not included.BZ-1421186 | Server | globally uncaught exception on storage node details page in administration |
| This content is not included.BZ-1417937 | Server | Details link and paging on content tab throws HTTP Status 404 |
| This content is not included.BZ-1431097 | Server | "java.lang.IllegalArgumentException: NaN" is logged in the server.log file when trying to store BaseLine values in the database [details] |
| This content is not included.BZ-1400692 | Agent | Update Jsch to 1.54 [details] |
| This content is not included.BZ-1419142 | Plug-ins | pg_temp_15.vacuum_l Tables in inventory and marked as down |
| This content is not included.BZ-1419531 | Plug-ins | Many network adapters in inventory although there is only one visible in device mapper |
| This content is not included.BZ-1446072 | Installer/Upgrade | JBoss ON Server fails to start after upgrade from update 05 to 08 due to deprecated system config fields: PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE [details] |
| This content is not included.BZ-1343642 | Installer/Upgrade | JBoss ON server installation does not complete and terminal shows "Still waiting for server to start..." over and over again [details] |
| This content is not included.BZ-1294626 | Other | Path too long error on unzipping the patch using Extract All on Windows Server 2008 R2 |
| This content is not included.BZ-1484900 | Other | Add licensing files to cumulative patch releases. |
| This content is not included.BZ-1420712 | Provisioning/Bundles | updateBackingContent CLI operation is not blocking and following retrieveBackingContent returns older content for some time |
| This content is not included.BZ-1463351 | Provisioning/Bundles | Bundle deployment sometimes fails with message "Unable to store Trigger with name: '<timestamp>' and group: 'org.rhq.enterprise.server.scheduler.jobs.BundleDeploymentStatusCheckJob', because one already exists with this identification." [details] |
| This content is not included.BZ-1324217 | Provisioning/Bundles | Bundle exec task can fail if %temp% is used on Windows when agent is running as System Service [details] |
| This content is not included.BZ-1420717 | Provisioning/Bundles | When calling retrieveBackingContent cli operation immediately after updateBackingContent it sometimes fails with NPE |
Installation
The apply-updates utility included in the update archive will be used to update a JBoss ON server, agent, or storage node installation.
Updating a server and storage node
-
Shutdown the server and any other components controlled by the server's
rhqctlcommand. Other components would include the JBoss ON agent and storage node installed on the same host as the server. To shutdown all components, therhqctl stopcommand could be used. -
Make a backup of your existing server installation and your JBoss ON system's database.
-
Extract the server update archive to the host machine where the JBoss ON component to be updated is installed.
-
As the same user who starts the JBoss ON components being updated, execute the
apply-updatescommand passing in the path to RHQ_SERVER_HOME. For example:./apply-updates.sh /opt/jboss/on/jon-server-3.3.0.GAIf the target server directory includes a storage node installation, it will also be updated.
If the target server has an agent installed in the directory above RHQ_SERVER_HOME, the agent will also be updated. For example, the above command would have also applied an agent update to
/opt/jboss/on/rhq-agentif the agent was installed. -
Start the server and all of its components, such as the JBoss ON agent or storage node, normally.
If more than one server or storage node is running in a high availability (HA) configuration, repeat the above steps for each server and storage node.
NOTE: In some cases, the update may introduce property or configuration script file changes that cannot safely be applied to existing user modified property or configuration script files. In such cases a new base or default file is created, with a
.newfile name extension, alongside the existing or user modified file. For example:[jon-server-3.3.0.GA]$ ls bin/rhq-server.properties* rhq-server.properties rhq-server.properties.newIf the new or changed properties or configuration options are applicable to you, you will need to manually add or define them in their respective property or configuration file.
Updating a server or storage node that has not yet been installed
The update can be applied to a JBoss ON server or storage node prior to executing the rhqctl install or rhqctl upgrade command. This allows installer and upgrade specific fixes to be applied to the JBoss ON components prior to performing the installation.
-
Extract the JBoss ON server archive as instructed in the installation guide.
-
On the same host, extract the server update archive.
-
As the same user who will be starting the JBoss ON components, execute the
apply-updatescommand passing in the path to RHQ_SERVER_HOME. For example:./apply-updates.sh /opt/jboss/on/jon-server-3.3.0.GAIf the target server has an agent installed in the directory above RHQ_SERVER_HOME, the agent will also be updated. For example, the above command would have also applied an agent update to
/opt/jboss/on/rhq-agentif the agent had already been manually installed. -
Perform the server, storage node, or agent installation or upgrade as instructed in the installation guide.
NOTE: In some cases, the update may introduce property or configuration script file changes that cannot safely be applied to existing user modified property or configuration script files. In such cases a new base or default file is created, with a
.newfile name extension, alongside the existing or user modified file. For example:[jon-server-3.3.0.GA]$ ls bin/rhq-server.properties* rhq-server.properties rhq-server.properties.newIf the new or changed properties or configuration options are applicable to you, you will need to manually add or define them in their respective property or configuration file.
Updating an agent
NOTE: JBoss ON agents installed via RPM can not be updated using this process. Instead, update RPM based installations using your system's update manager.
These steps are only necessary if the agent's auto-update feature is disabled or if you want to manually update an existing agent.
Before proceeding, you should first apply the update to all servers in the JBoss ON system.
-
Shutdown the agent.
-
Make a backup of your existing agent installation.
-
Extract the server update archive to the host machine where the JBoss ON agent to be updated is installed.
-
As the same user who starts the JBoss ON agent being updated, execute the
apply-updatescommand passing in the path to RHQ_AGENT_HOME. For example:./apply-updates.sh /opt/jboss/on/rhq-agent -
Start the agent normally.
Repeat the above steps for any agent in the system that must be updated.
NOTE: In some cases, the update may introduce property or configuration script file changes that cannot safely be applied to existing user modified property or configuration script files. In such cases a new base or default file is created, with a
.newfile name extension, alongside the existing or user modified file. For example:[rhq-agent]$ ls bin/rhq-agent-env.* rhq-agent-env.sh rhq-agent-env.sh.newIf the new or changed properties or configuration options are applicable to you, you will need to manually add or define them in their respective property or configuration file.