Menu Close

Release Notes for Eclipse Vert.x 4.1

Red Hat build of Eclipse Vert.x 4.1

For use with Eclipse Vert.x 4.1.8

Red Hat Customer Content Services


This Release Note contains important information related to Eclipse Vert.x 4.1.8


Date of release: 2022-01-17

Providing feedback on Red Hat documentation

We appreciate your feedback on our documentation. To provide feedback, you can highlight the text in a document and add comments.

This section explains how to submit feedback.


  • You are logged in to the Red Hat Customer Portal.
  • In the Red Hat Customer Portal, view the document in Multi-page HTML format.


To provide your feedback, perform the following steps:

  1. Click the Feedback button in the top-right corner of the document to see existing feedback.


    The feedback feature is enabled only in the Multi-page HTML format.

  2. Highlight the section of the document where you want to provide feedback.
  3. Click the Add Feedback pop-up that appears near the highlighted text.

    A text box appears in the feedback section on the right side of the page.

  4. Enter your feedback in the text box and click Submit.

    A documentation issue is created.

  5. To view the issue, click the issue tracker link in the feedback view.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Chapter 1. Required Infrastructure Component Versions

When you work with Red Hat build of Eclipse Vert.x, you can use the following components. However, Red Hat does not provide support for components listed below except Red Hat OpenShift cluster.

Required components
The following components are required to build and develop applications using Eclipse Vert.x.
Component nameVersion


3.6.0 or later


8 or 11

[a] A full JDK installation is required, as JRE does not provide tools for compiling Java applications from source.
Optional components
Red Hat recommends using the following components depending on your development and production environments.
Component nameVersion


2.0 or later

OpenShift Maven Plugin


oc command line tool

3.11 or later[a]

Access to a Red Hat OpenShift cluster[b]

3.11 or later

[a] The version of the oc CLI tool should correspond to the version of OCP that you are using.
[b] OpenShiftCluster is supported by Red Hat

Chapter 2. Supported Eclipse Vert.x Runtime Component Configurations and Integrations

The following resource defines the supported configurations and integrations of Red Hat products with Eclipse Vert.x:

Chapter 3. Features

3.1. New and Changed features

This section describes the new functionalities introduced in this release. It also contains information about changes in the existing functionalities.

3.1.1. OpenJDK11 OpenShift images support multiple architectures

OpenJ9 images for IBM Z and IBM Power Systems have been deprecated. The following OpenJDK11 image has been updated to support multiple architectures:

  • ubi8/openjdk-11

You can use the OpenJDK11 image with the following architectures:

  • x86 (x86_64)
  • s390x (IBM Z)
  • ppc64le (IBM Power Systems)

3.1.2. Support Eclipse Vert.x Runtime on FIPS enabled Red Hat Enterprise Linux (RHEL) system

Red Hat build of Eclipse Vert.x runs on a FIPS enabled RHEL system and uses FIPS certified libraries provided by RHEL.

3.1.3. HTTP client redirect handler propagates headers

From Eclipse Vert.x 4.1.0 onward, if there are headers in an HTTP redirect, then the HTTP client redirect handler propagates the headers to the next request. This change enables the redirect handler to have more control over the entire redirected request.

In earlier releases of Eclipse Vert.x, where there were redirected requests with headers, the HTTP client would handle the headers after the redirect.

The following example shows you how redirects are handled in Eclipse Vert.x 4.1.0:

RequestOptions options = new RequestOptions();

// From 4.1.0 propagate headers

3.1.4. Upgrade to Infinispan 12

In Eclipse Vert.x 4.1.0, the Infinispan cluster manager has been updated and is based on Infinispan 12.

Infinispan 11 had a bug, which did not allow storing of byte arrays in a multimap cache. As a wordaround, the Eclipse Vert.x cluster manager had to use an internal Infinispan class, WrappedBytes, to store eventbus subscription data. This issue has been fixed in Infinispan 12.

3.1.5. JSON configuration takes precedence over connection string options in MongoDB Client

In Eclipse Vert.x 4.1.0, the JSON configuration options are applied even if a connection_string option is available.

The following configuration options are now applied:

        db_name: "mydb"
        connection_string: "mongodb://localhost:27017"
        maxPoolSize: 10
        minPoolSize: 3

In earlier releases of Eclipse Vert.x, the JSON configuration options were ignored when connection string was available. For example, consider the previous example. In earlier releases of Eclipse Vert.x, db_name, maxPoolSize, and minPoolSize options would have been ignored.

3.1.6. Removed the deprecated JWT options methods

From Eclipse Vert.x 4.0 onward, the JWT and OAuth2 handlers are used to handle scopes.

From Eclipse Vert.x 4.1.0 onward, JWTOptions.setScopes(List<String>), JWTOptions.addScope(String) and JWTOptions.withScopeDelimiter(String) methods have been removed. These methods did not comply with the specification.

The following example shows you how to handle scopes in Eclipse Vert.x 4.1.0.

// before 4.1.0
JWTAuthOptions authConfig = new JWTAuthOptions()
  .setJWTOptions(new JWTOptions()
    .withScopeDelimiter(" ")));

JWTAuth authProvider = JWTAuth.create(vertx, authConfig);


// in 4.1.0
JWTAuth authProvider = JWTAuth.create(vertx, new JWTAuthOptions());

    .withScopeDelimiter(" "));

3.1.7. Deprecated the custom formatter method that accepts a function

From Eclipse Vert.x 4.1.0, LoggerHandler.customFormatter(Function) method has been deprecated. The function takes as input an HttpServerRequest and returns a formatted log string. Because the output is a string, it is not possible to access the context.

Use the new method LoggerHandler customFormatter(LoggerFormatter formatter) instead. The method takes as input a custom formatter that gives access to the context.

3.1.8. New exception to handle HTTP failures

From Eclipse Vert.x 4.1.0, a new exception class io.vertx.ext.web.handler.HttpException is available that can be used to handle HTTP failures. You can use the exception to specify custom status codes other than 500. For example, new HttpException(401, “Forbidden”) indicates that the requests that are forbidden should return status code 401.

3.1.9. Support for RxJava 3

From Eclipse Vert.x 4.1.0, RxJava 3 is supported.

  • A new rxified API is available in the io.vertx.rxjava3 package.
  • Integration with Eclipse Vert.x JUnit5 is provided by the vertx-junit5-rx-java3 binding.

3.1.10. Context server interceptor binds all types of data and is more secure

From Eclipse Vert.x 4.0.3, the ContextServerInterceptor.bind() method binds all types of data to the context. The method is more secure now as it does not expose the storage details.

In releases prior to Eclipse Vert.x 4.0.3, the method used to bind only 'String' data type to context. It also exposed the storage details.

To use the updated ContextServerInterceptor.bind() method, you must update your application.

The following example shows the code in releases prior to Eclipse Vert.x 4.0.3.

// Example code from previous releases

class X extends ContextServerInterceptor {
  public void bind(Metadata metadata, ConcurrentMap<String, String> context) {

The following example shows the replacing code fpr Eclipse Vert.x 4.0.3 release.

// Replacing code for Eclipse Vert.x 4.0.3 release

class X extends ContextServerInterceptor {
  public void bind(Metadata metadata) {

3.1.11. Matching of ending slash (/) in route paths that end with wildcard character is no longer required

In releases prior to Eclipse Vert.x 4.0.3, if routes were defined with a path ending in slash and a wildcard /*, the routes would be called only if the matching request also included the ending slash /. This rule caused problems when the wildcard was empty.

From Eclipse Vert.x 4.0.3 onward, this rule is no longer applied. You can create routes whose paths end in a slash (/). However, it is not mandatory to specify the slash in the request URLs.

Also, you can create and use request URLs to call routes that end with wildcards in their path instead of slash (/). For example, routes with wildcard can be defined as /foo/*. Here the route has to match an open wildcard at the end of the path. The request URL can be /foo.

The table shows the behavior in Eclipse Vert.x 4.0.3 and previous releases when you send a request URL /foo/*. You can see that the ending slash is optional in Eclipse Vert.x 4.0.3 and request matches the route.

RouteEclipse Vert.x 4.0.3Releases prior to Eclipse Vert.x 4.0.3



No Match


No Match

No Match







3.1.12. Removed the autoRegistrationOfImporters attribute from service discovery options

The autoRegistrationOfImporters attribute has been removed from service discovery options.

3.1.13. Authenticate method in authentication provider class updated to support token as input credentials

In releases prior to Eclipse Vert.x 4.0.3, the AuthenticationProvider.authenticate() method would incorrectly take jwt: someValue as input credentials.

From Eclipse Vert.x 4.0.3, the AuthenticationProvider.authenticate() method has been updated and takes token: someValue as input credentials. This change ensures that both JSON and typed APIs are consistent and can be used interchangeably.

The following code shows the implementation for the authenticate method in releases prior to Eclipse Vert.x 4.0.3.

new JsonObject().put("jwt", "token...");

The following code shows the implementation for the authenticate method in Eclipse Vert.x 4.0.3 release.

new JsonObject().put("token", "token...");

3.1.14. Get method for PEM keys returns Buffer instead of a String

The PubSecKeyOptions.getBuffer() method returns the PEM or secret key buffer. In releases prior to Eclipse Vert.x 4.0.2, the key buffer was stored and returned as a String. However, it is recommended to save secrets as a Buffer. From Eclipse Vert.x 4.0.2 onward, the method stores and returns the key buffer as a Buffer. This change improves the security and handling of secrets.

The PubSecKeyOptions.setBuffer() method continues to accept a String argument. In the set method, an overload for Buffer has been added to safely handle non ASCII secret materials. This change does not require any change to the existing code.

3.1.15. Kubernetes service importer is no longer registered automatically

From Eclipse Vert.x 4, the KubernetesServiceImporter discovery bridge is no longer registered automatically. Even if you have added the bridge in the classpath of your Maven project, it will not be automatically registered.

You must manually register the bridge after creating the ServiceDiscovery instance.

3.1.16. Use future methods for asynchronous operations

Eclipse Vert.x 4 uses futures for asynchronous operations. Every callback method has a corresponding future method.

Futures can be used to compose asynchronous operations. When you use futures, the error handling is better. Therefore, it is recommended to use a combination of callback and futures in your applications.

3.1.17. No dependency on the Jackson Databind library

In Eclipse Vert.x 4, Jackson Databind is an optional Maven dependency. If you want to use this dependency, you must explicitly add it in the classpath. For example, if you are object mapping JSON, then you must explicitly add the dependency.

3.1.18. Handling deprecations and removals

In Eclipse Vert.x 4, new enhanced features have been provided. The old features and functions have been deprecated or removed in Eclipse Vert.x 4. Before you migrate your applications to Eclipse Vert.x 4, check for deprecations and removals.

The Java compiler generates warnings when deprecated APIs are used. You can use the compiler to check for deprecated methods while migrating applications to Eclipse Vert.x 4.

3.1.19. Support for distributed tracing

Eclipse Vert.x 4 supports distributed tracing. You can use tracing to monitor microservices and identify performance issues.

Eclipse Vert.x 4 integrates with OpenTracing system.

The following Eclipse Vert.x components can log traces:

  • HTTP server and HTTP client
  • Eclipse Vert.x SQL client
  • Eclipse Vert.x Kafka client

Tracing is available as Technology Preview. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend to use them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

See Technology Preview Features Support Scope on the Red Hat Customer Portal for information about the support scope for Technology Preview features.

3.1.20. New publishing location for EventBus JavaScript Client

In Eclipse Vert.x 4, the EventBus JavaScript client, vertx-web-client.js is not published as a Red Hat artifact in the Maven repository.

The client is published in the npm repository. You can access the client from the following location: @vertx/eventbus-bridge-client.js

3.1.21. Deploy Eclipse Vert.x applications using OpenShift Maven plugin

Use the OpenShift Maven plugin to deploy your Eclipse Vert.x applications on OpenShift. The Fabric8 Maven plugin is no longer supported. For more information, see the section migrating from Fabric8 Maven Plugin to Eclipse JKube.

3.1.22. Eclipse Vert.x metering labels for OpenShift

You can add metering labels to your Eclipse Vert.x pods and check Red Hat subscription details with the OpenShift Metering Operator.

  • Do not add metering labels to any pods that an operator or a template deploys and manages.
  • You can apply labels to pods using the Metering Operator on OpenShift Container Platform version 4.8 and earlier. From version 4.9 onward, the Metering Operator is no longer available without a direct replacement.

Eclipse Vert.x should use the following metering labels:

  • Red_Hat
  • rht.prod_name: Red_Hat_Runtimes
  • rht.prod_ver: 2022-Q1
  • rht.comp: Vert.x
  • rht.comp_ver: 4.1.8
  • rht.subcomp: <leave_blank>
  • rht.subcomp_t: application

3.1.23. Support for OpenJDK 8 and OpenJDK 11 RHEL 8 Universal Base Images (UBI8)

Eclipse Vert.x introduces support for building and deploying Eclipse Vert.x applications to OpenShift with OCI-compliant Universal Base Images for Red Hat OpenJDK 8 and Red Hat OpenJDK 11 on RHEL 8.

The RHEL 8 OpenJDK Universal Base Images replace the RHEL 8 OpenJDK builder images. The RHEL 8 OpenJDK base images are no longer supported for use with Eclipse Vert.x.

3.2. Deprecated features

This section lists the functionalities deprecated or removed in this release.

  • HttpServerOptions

    Removed methodsReplacing methods

































  • Eclipse Vert.x Web

    Removed elementsReplacing elements









    StaticHandler.create(String, ClassLoader)






  • Messaging

    Removed methodsReplacing methods





  • EventBus

    Removed methodsReplacing methods

    EventBus.send(…​, Handler<AsyncResult<Message<T>>>)Message.reply(…​, Handler<AsyncResult<Message<T>>>)


  • Handlers

    Removed methodsReplacing methods





  • JSON

    Removed Fields/MethodsNew methods

    Json.mapper() field


    Json.prettyMapper() field


    Json.decodeValue(Buffer, TypeReference<T>)

    JacksonCodec.decodeValue(Buffer, TypeReference)

    Json.decodeValue(String, TypeReference<T>)

    JacksonCodec.decodeValue(String, TypeReference)

  • JUnit5

    Deprecated methodsNew methods





  • Reactive Extensions (Rx)

    Deprecated methodsNew methods



  • Circuit breaker

    Removed methodsReplacing methods





  • MQTT

    Removed methodsReplacing methods













  • AMQP client

    Removed methodsReplacing methods

    AmqpClient.createReceiver(String address, Handler<AmqpMessage> messageHandler, …​)

    AmqpClient createReceiver(String address, Handler<AsyncResult<AmqpReceiver>> completionHandler)

    AmqpConnection createReceiver(…​, Handler<AsyncResult<AmqpReceiver>> completionHandler)

    AmqpConnection createReceiver(String address, Handler<AsyncResult<AmqpReceiver>> completionHandler)

    AmqpConnection createReceiver(.., Handler<AmqpMessage> messageHandler, Handler<AsyncResult<AmqpReceiver>> completionHandler)

    AmqpConnection createReceiver(String address, Handler<AsyncResult<AmqpReceiver>> completionHandler)

  • Authentication and authorization

    Removed elementsReplacing elements


    No replacing method


    No replacing method


    No replacing method


    No replacing method


    KeycloakAuth.create(vertx, JsonObject) ()

    OAuth2Auth.create(Vertx, OAuth2FlowType, OAuth2ClientOptions)()

    OAuth2Auth.create(vertx, new OAuth2ClientOptions().setFlow(YOUR_DESIRED_FLOW))

    OAuth2Auth.create(Vertx, OAuth2FlowType)

    OAuth2Auth.create(vertx, new OAuth2ClientOptions().setFlow(YOUR_DESIRED_FLOW))





    io.vertx.ext.auth.jwt.JWTOptions data object

    io.vertx.ext.jwt.JWTOptions data object

    SecretOptions class

    PubSecKeyOptions class

    Deprecated methodsReplacing methods






    No replacing method




    No replacing method

    Deprecated classReplacing class


    Create user objects using the ` User.create(JsonObject)` method.


    No replacing class


    JDBCAuthenticationOptions for authentication and JDBCAuthorizationOptions for authorization


    No replacing class




    Recommended to use WebClient class


    No replacing class

  • Service discovery

    Removed methodsReplacing methods

    ServiceDiscovery.create(…​, Handler<ServiceDiscovery> completionHandler)


    ServiceDiscovery.create(…​, Handler<ServiceDiscovery> completionHandler)

    ServiceDiscovery.create(Vertx, ServiceDiscoveryOptions)

  • Eclipse Vert.x configuration

    Removed methodsReplacing methods



  • MongoDB client

    Removed methodsReplacing methods

















  • Clients with no shared data sources

    Deprecated MethodsNew Methods









  • Hook methods

    Removed MethodsNew Methods


    No replacing method


    No replacing method

  • Clone methods

    Removed MethodsNew Methods







  • VertxOptions

    Removed MethodsNew Methods


    No replacing method


    No replacing method



  • Pooled buffer

    Removed MethodsNew Methods


    No replacing method


    No replacing method

Chapter 4. Release components

4.1. Supported Artifacts introduced in this release

The following artifacts have been moved from Technology Preview to fully supported in this release:

  • vertx-auth-webauthn
  • vertx-config-vault
  • vertx-sql-client-templates
  • vertx-web-api-contract

4.2. Technology Preview artifacts introduced in this release

The following artifacts are provided as Technology Preview in this release.

  • vertx-mssql-client

    The Eclipse Vert.x reactive MSSQL client is a client for Microsoft SQL server. It is an API that helps in database scalability and has low overhead. Since the API is reactive and non-blocking you can handle multiple database connections with a single thread.

  • vertx-http-proxy

    The Eclipse Vert.x HTTP proxy is a reverse proxy. Using this module you can easily create proxies. The proxy server can also dy­nam­i­cally re­solve the DNS queries from ori­gin server.

  • vertx-web-proxy

    The Eclipse Vert.x web proxy enables you to mount an Eclipse Vert.x HTTP proxy in an Eclipse Vert.x web router.

  • vertx-opentelemetry

    Open Telemetry tracing is supported. You can use Open Telemetry for HTTP and event bus tracing.

  • vertx-web-sstore-infinispan

    This Eclipse Vert.x web ses­sion stor­e enables you to save session data in an Infinispan cache. The module is implemented on the In­fin­is­pan client so you can use it with either stand alone or clus­tered Eclipse Vert.x ap­plications.

  • vertx-auth-webauthn

    The Eclipse Vert.x authentication module io.vertx.ext.auth.AuthProvider interface has been split into two new interfaces:

    • io.vertx.ext.auth.authentication.AuthenticationProvider
    • io.vertx.ext.auth.authorization.AuthorizationProvider

      Authentication is a new feature in Eclipse Vert.x 4. In earlier releases, you could only check if a user was authorized to perform the tasks on the User object. This meant that the provider was responsible for both authentication and authorization of the user.

      In Eclipse Vert.x 4, the User object instances are not associated with a particular authentication provider. So you can authenticate and authorize a user using different providers.

  • vertx-opentracing

    Eclipse Vert.x 4 supports distributed tracing. You can use tracing to monitor microservices and identify performance issues.

    Eclipse Vert.x 4 integrates with OpenTracing system.

    The following Eclipse Vert.x components can log traces:

    • HTTP server and HTTP client
    • Eclipse Vert.x SQL client
    • Eclipse Vert.x Kafka client


      For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

4.3. Artifacts removed in this release

No artifacts are removed in this release.

4.4. Artifacts deprecated in this release

No artifacts are marked as deprecated in this release.

Chapter 5. Fixed issues

This Eclipse Vert.x release incorporates all bugfixes from community release of version 4.1.8. Issues resolved in the community release are listed in the Eclipse Vert.x 4.1.8.

5.1. Google Guava classes included in GraphQL builds

In the Eclipse Vert.x 4.0.0 and 4.0.2 releases, the vertx-web-graphql dependency was not usable. This was because an incomplete build of GraphQL Java with version 16.1.0.redhat-00001 was used. In the incomplete GraphQL build, the Guava classes were missing.

This issue is resolved in the Eclipse Vert.x 4.0.3 release. The release includes the GraphQL Java 16.1.0.redhat-00002 version, which is a complete build with Guava classes. These Guava classes are shaded into the jar.

5.2. vertx-opentracing available in Eclipse Vert.x builds

The vertx-opentracing dependency was introduced as a Technical Preview feature in Eclipse Vert.x 4.0.0. However, the dependency was not available in Eclipse Vert.x 4.0.0 and 4.0.2 releases.

This issue is resolved in Eclipse Vert.x 4.0.3 release. The release includes the vertx-opentracing dependency.

Chapter 6. Known issues

6.1. KubernetesServiceImporter() cannot be directly registered in Eclipse Vert.x Reactive Extensions (Rx)

You cannot directly register KubernetesServiceImporter() with the Reactive Extensions (Rx) for Eclipse Vert.x.
Service importers do not have a generated RxJava 2 implementation.
You must create an instance of KubernetesServiceImporter and encapsulate it with {@link io.vertx.reactivex.servicediscovery.spi.ServiceImporter} as shown in the following example:
{@link examples.RxServiceDiscoveryExamples#register(io.vertx.reactivex.servicediscovery.ServiceDiscovery)}

The following example shows how to register KubernetesServiceImporter() in Eclipse Vert.x Reactive Extensions (Rx).

ServiceDiscovery discovery = ServiceDiscovery.create(vertx);
discovery.getDelegate().registerServiceImporter(new KubernetesServiceImporter(), new JsonObject());

6.2. Red Hat AMQ Streams images are not available for IBM Z and IBM Power Systems

The Red Hat AMQ Streams Operator and Kafka images are not available for IBM Z and IBM Power Systems. Since the images are not available, the vertx-kafka-client module is not certified to work with AMQ Streams on IBM Z and IBM Power Systems.

6.3. Connection between a RHEL 8-based database application and a RHEL 7-based MySQL 5.7 database fails due to TLS protocol version mismatch


Attempting to open a TLS-secured connection using OpenSSL between an application container built on a RHEL 8-based OpenJDK builder image and a database container built on a RHEL 7-based MySQL 5.7 container image results in a connection failure due to a at runtime: For more detail, view the issue in JIRA.

Caused by: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)


The issue occurs due to a difference in the latest supported TLS protocol version between RHEL 7 and RHEL 8. The TLS implementation on RHEL 7 supports TLS protocol versions 1.0 (deprecated), 1.1, and 1.2. The TLS implementation on RHEL 8 also supports TLS protocol version 1.3, which is also the default TLS version used in RHEL 8-based builder images. This discrepancy may cause a TLS protocol version mismatch between application components while negotiating a TLS handshake, which in turn causes the connection between the application and database containers to fail.


To prevent the issue described above, manually specify a TLS protocol version that is supported on both operating system versions in your database connection string. For example:


6.4. False Connection reset by peer error messages when calling application endpoint

Making an HTTP request on an endpoint of an Eclipse Vert.x application using either the curl tool or a Java HTTP client, produces the following error in the logs after each request:
SEVERE: Connection reset by peer

This behavior is caused by the interaction of the Netty application framework and the HAProxy load-balancer used by OpenShift. The error occurs due to existing HTTP connections being re-used by HAProxy without closing. Even though the error message is logged, no error condition occurs. HTTP requests are handled correctly and the application responds as expected.

Legal Notice

Copyright © 2022 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.