Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction
Introduction

JBoss plugin release notes

7 minute readExtensibilityDeveloper productivity

4.0.0

  • Upgraded from Perl 5.8 to Perl 5.32. The EC-JBoss plugin is not backward compatible with CloudBees CD/RO 10.3 and earlier.

  • Starting with the 4.0.0 release, a new agent is required to run EC-JBoss plugin procedures.

3.1.0

  • Added JBoss EAP 7.4 support.

  • Fixed issue with accessing non-existent serverconfig properties.

  • Preserve protocol definition in JBoss endpoint.

3.0.0

  • Exception handling has been improved.

2.8.1

  • Added session validation.

2.8.0

  • Plugin configuration has been improved to support external credentials.

2.7.2

  • The documentation has been migrated to the main documentation site.

2.7.1

  • Renamed to "CloudBees CD".

2.7.0

  • The following updates have been made for creating and editing plugin configuration procedures:

    • Added the option to check the connection with JBoss within a provided resource.

    • Added more logging and diagnostic messages.

    • Jobs with a successful run for creating or editing configuration are no longer automatically removed.

2.6.3

  • Renamed to "CloudBees".

2.6.2

  • Fixed the issue with lost output parameters for CloudBees CD/RO 9.0. Previously, when upgrading or performing a clean installation of CloudBees CD/RO 9.0, output parameters were not created for the plugin’s procedures.

2.6.1

  • The plugin icon has been updated.

2.6.0

  • Added support for the CreateOrUpdateDataSource and StartHostController procedures.

  • The following improvements have been made for the StartStandaloneServer procedure:

    • Improved step summary.

    • The Physical location of the standalone script parameter label was updated to Startup Script.

    • The Optional configuration name parameter label was updated to Server Configuration File.

    • Added supported for a new optional Additional options parameter, for changing startup behavior.

    • Added supported for a new optional Log file location parameter that is used to surface server logs.

    • Fixed handling of Server Configuration File in Windows, to override the default standalone.xml file by using a different file that stores server configuration.

    • Verification of server startup is now verified by connecting the JBoss CLI successfully to the server.

    • Startup boot errors are now surfaced.

    • The most recent 100 lines of server logs are shown if a log file location is specified.

  • The following improvements have been made for the CheckServerGroupStatus procedure:

    • Improved documentation for step summary.

    • Added the following new Criteria options: DISABLED and STOPPED or DISABLED.

    • For ElectricFlow 8.3 and later, added an output parameter to capture if the Criteria checked by this procedure returns TRUE or FALSE.

  • The following improvements have been made for the StartServers and StopServers procedures:

    • Improved the step summary for some specific cases.

    • Standardized approach for writing the step summary, and it is now to be included only in the /myCall/summary context.

    • Fixed logging for log levels INFO, WARNING, and ERROR.

    • Improved passing of credentials to the JBoss CLI.

    • Configured the plugin to allow the ElectricFlow UI to create configurations inline of the procedure form.

    • Added classification of procedures in the top section of the help file.

2.5.0

  • Added support for the CreateOrUpdateXADataSource, RemoveXADataSource, StopDomain, and GetEnvInfo procedures.

  • For the StartServers and StopServers procedures, fixed the step summary to show correct information if the controller is not available.

2.4.1

  • Configured the plugin to allow the ElectricFlow UI to render the plugin procedure parameters entirely using the configured form XMLs.

  • Enabled the plugin for managing the plugin configurations inline when defining an application process step or a pipeline stage task.

2.4.0

  • Added support for the DeployApplication, the CreateOrUpdateJMSQueue, the CreateOrUpdateJMSTopic, the RemoveJMSQueue, and the RemoveJMSTopic procedures. The DeployApplication provides a major improvement to the existing DeployApp procedure. It provides a very robust interface and its behavior is idempotent.

  • The following improvements have been made for the DeployApp procedure:

    • Renamed the Path to the application to deploy parameter to Application Content Source Path.

    • Added URL support within the Application content source path parameter for JBoss EAP 7.0 and later.

    • Changed the successful step summaries.

    • Improved the documentation.

  • The following improvements have been made for the StartServers procedure:

    • Renamed the Wait time parameter to Timeout for recurring check of servers (seconds).

    • Changed the behavior for checking servers in order to perform a check at least once.

    • Improved the documentation.

  • The following improvements have been made for the StopServers procedure:

    • Renamed the Wait time parameter to Timeout for recurring check of servers (seconds).

    • Changed the behavior for checking servers in order to perform a check at least once.

    • Changed the warning step summary to include information about previously DISABLED servers, similar to information about STOPPED servers.

    • Improved the documentation.

  • Fixed non-Ascii characters in plugin forms.

2.3.2

  • For the StartStandaloneServer procedure, the handling of the Optional configuration name parameter has been fixed.

  • The following improvements have been made for the StartDomainServer procedure:

    • Renamed the Optional configuration name parameter to Optional domain configuration name.

    • The handling of the Optional domain configuration name parameter has been fixed.

    • Added support for a new Optional host configuration name parameter.

  • For the CheckServerStatus procedure, the check for the "NOT RUNNING" success criteria has been fixed.

  • For the StopServers procedure, the server check has been expanded by handling the DISABLED server status, similar to information about STOPPED servers.

  • For the JBoss configuration, renamed the JBoss AS URL parameter to JBoss controller location.

2.1.5

  • In the DeleteDatasource procedure, the application_name property has been renamed to datasource_name.

  • Added support for the CheckHostControllerStatus and CheckServerGroupStatus procedures.

  • Fixed an issue where the CheckDeploymentStatus procedure was unable to check the status of the deployment in domain mode.

  • The following parameters have been added to the CheckDeployStatus procedure: Hosts, ServerGroups, Servers, Criteria, and Wait time.

  • The Additional Java options and Physical location of the JBoss client script fields have been added to the configuration.

  • The Physical location of the JBoss client script field is now optional.

  • The EnableDeploy and DisableDeploy procedures have been improved to work with both JBoss domain and standalone modes.

  • Fixed a bug where the CreateDatasource procedure failed when enabling a datasource on JBoss 6.0.0.

2.1.4

  • Fixed an issue with configurations being cached for Internet Explorer.

2.1.3

  • Updated the ShutdownStandaloneServer, StartDomainServer, and StartStandaloneServer procedures.

  • Added a link to the Plugin Configuration page within the plugin step panels.

2.1.2

  • Improved the plugin for improved Windows support.

  • Replaced the Username and Password parameters with credentials in the CreateDatasource procedure for backward incompatibility.

2.1.1

  • Cleaned up the code.

  • Fixed the procedure descriptions and updated the documentation.

2.1.0

  • Added support for the RunCustomCommand procedure to run user-specified commands on JBoss instances.

  • Added support for the StartServers procedure to start server groups.

  • Added support for the StopServers procedure to stop server groups.

  • Fixed the CreateDatasource, DeleteDatasource, DeployApp, UndeployApp, EnableDeploy, and DisableDeploy procedures.

  • Fixed plugin errors on Linux ElectricFlow instances.

2.0.7

  • Fixed a POST_PROCESSOR_ERROR in the CheckServerStatus procedure.

  • Fixed an error in the CheckDeployStatus procedure where the Success criteria was set to Page not found.

  • Fixed a bug in the DeployApp procedure where the Runtime name for deployment parameter was specified.

2.0.6

  • Added five new procedures to check the status of deployments, create datasources, delete datasources, stop servers, and restart servers.

  • Fixed minor bugs.

2.0.5

  • Changed the procedure names in the step picker section.

2.0.4

  • Added minor fixes.

2.0.3

  • Made improvements to the documentation.

2.0.2

  • Upgraded the plugin to use the new XML parameter form.

  • Added a direct link to the new documentation.

2.0.1

  • Improved the XML parameter panels.

  • Reformatted the documentation.

Known issues

This section contains known limitations with different JBoss server versions found during system testing.

Table 1. Known issues
JBoss version Issue

JBoss EAP 6, Windows only

The jboss-cli.bat does not exit with the correct return code when calling it from a wrapper script. It always exits with 0, even if the operation fails. For CloudBees CD/RO, the JBoss CLI response may be interpreted incorrectly. For more information, refer to link: Red Hat Bugzilla – Bug 1223877.

Workaround: Make sure that you are using JBoss 6, with all updates installed. For JBoss EAP 6.4, the latest cumulative pack should be installed.

JBoss 6.0 and 6.2

The JBoss CLI fails to show the app status when the runtime name is different from the deployment name. The JBoss CLI may fail with a no metrics available error during the CheckDeployStatus procedure. For more information, refer to the RedHat customer solution, Red Hat Bugzilla – Bug 1007696, and WFLY-2061.

Workaround: Use the latest version of JBoss 6.2. This issue has been fixed in JBoss 6.2.1.

JBoss EAP 6.3

Removing enabled XA data sources can result in removing services that lead to unsatisfied dependencies and return errors. For example, in JBoss standalone:

JBAS014762: Removing services has lead to unsatisfied dependencies: Service jboss.data-source.reference-factory.MysqlXADSC289546 was depended upon by service jboss.naming.context.java.MysqlXADS Service jboss.xa-data-source-config.MysqlXADSC289546 was depended upon by service jboss.data-source.java:/MysqlXADS
▼

For example, in JBoss domain:

JBAS010839: Operation failed or was rolled back on all servers.
▼

JBoss EAP 7.0

When attempting to create XA data sources using the JBoss CLI --command, single quotes are missed if using the --check-valid-connection-sql additional option. For more information, refer to JBEAP-14659. This issue has been fixed in JBoss EAP 7.1.

JBoss EAP 7.1, Windows only

The JBoss CLI may fail with the following error:

Failed to connect to the controller: Unable to authenticate against controller at ... Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication
▼

This is a bug in the jboss-cli.bat script:

Cannot connect to JBoss controller via CLI by passing password in command line if password contains '!' character (for JBoss EAP 7.1.0.GA in Windows)
▼

For more information, refer to JBEAP-14335 and WFCORE-3674

JBoss EAP 7.4

When deploying a remote artifact using the URL path (for example, --url=<artifact url>), the JBoss CLI ignores the custom deployment name (the --name parameter). Due to this new JBoss behavior, the custom deployment name parameters are also ignored in the DeployApp and DeployApplication procedures. Launching the DeployApplication procedure may fail if both the URL in the Physical location of the JBoss client script and Deployment name parameters are specified at the same time.

All systems

When the JBoss CLI is in non-interactive (--command) mode, it still prompts you for input if the certificate is invalid. For example, if it is self-signed. This only affects secure JBoss connections. If a target certificate is not valid, self-signed, exported, or similar, the JBoss CLI incorrectly prompts for connection confirmation, even in non-interactive mode. For more information, refer to WFLY-2950 and WFCORE-869.

This issue has not been fixed in JBoss EAP 7. However, an --error-on-interact option has been added as a workaround. As a result, the plugin procedure may become unresponsive, if a secured connection is being used and the certificate is invalid.

Workarounds:

  • Use a valid certificate.

  • Use --error-on-interact as an additional parameter to prevent the procedure from becoming unresponsive. However, it still fails if the certificate is invalid.

  • In the plugin configuration, use the Additional Java options field to provide a keystore file with certificate accepted. It can be achieved with the following value:
    -Djavax.net.ssl.trustStore=/path/to/your.keystore
Create JBoss plugin procedures