Red Hat xPaaS Release Notes

Red Hat xPaaS 0

Information about the release and known issues

Red Hat xPaaS Documentation Team

Legal Notice

Copyright © 2016 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 http://creativecommons.org/licenses/by-sa/3.0/. 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, 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 Software Collections 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.

Abstract

Release Note Information for Red Hat xPaaS images

Chapter 1. Release Notes

Starting in OpenShift Enterprise 3.0, xPaaS images are provided for the following:

  • Red Hat JBoss Enterprise Application Platform
  • Red Hat JBoss Web Server
  • Red Hat JBoss A-MQ

Starting in OpenShift Enterprise 3.1, xPaaS images are also provided for the following:

  • Red Hat JBoss Fuse (Fuse Integration Services)
  • Red Hat JBoss BRMS (Decision Server)
  • Red Hat JBoss Data Grid

Starting in OpenShift Enterprise 3.2, xPaaS images are also provided for the following:

  • Red Hat JBoss SSO image.
  • Red Hat JBoss BPM Suite (Intelligent Process Server)

xPaaS images are now also provided for:

 — Red Hat JBoss Data Virtualization

See enterprise.openshift.com/middleware-services for additional information.

Chapter 2. xPaaS Image for Red Hat JBoss Data Virtualization

Red Hat JBoss Data Virtualization is available as a containerized xPaaS image that is designed for use with OpenShift Enterprise 3.2 and later.

However, there are significant differences in supported configurations and functionality in the Red Hat JBoss JDV xPaaS image compared to the regular release of Red Hat JBoss Data Virtualization. Documentation for other Red Hat JBoss Data Virtualization functionality not specific to the Red Hat JBoss Data Virtualization image can be found in the Red Hat JBoss Data Virtualization documentation on the Red Hat Customer Portal.

Chapter 3. xPaaS Image for Red Hat JBoss BPM Suite (Process Server)

Red Hat JBoss BPM Suite (Process Server) is available as a containerized xPaaS image that is designed for use with OpenShift Enterprise 3.2 and later.

However, there are significant differences in supported configurations and functionality in the Red Hat JBoss BPM Suite xPaaS image compared to the regular release of Red Hat JBoss BPM Suite. Documentation for other Red Hat JBoss BPM Suite functionality not specific to the Red Hat JBoss BPM Suite image can be found in the Red Hat JBoss BPM Suite documentation on the Red Hat Customer Portal.

Chapter 4. xPaaS Image for Red Hat JBoss SSO

Red Hat JBoss SSO is available as a containerized xPaaS image that is designed for use with OpenShift Enterprise 3.2 and later.

However, there are significant differences in supported configurations and functionality in the Red Hat JBoss SSO xPaaS image compared to the regular release of Red Hat SSO. Documentation for other Red Hat SSO functionality not specific to the Red Hat JBoss SSO image can be found in the Red Hat Single Sign-On documentation on the Red Hat Customer Portal.

Chapter 5. xPaaS Image for Red Hat JBoss EAP

Red Hat JBoss EAP is available as a containerized xPaaS image that is designed for use with OpenShift Enterprise 3.0 and later.

However, there are significant differences in supported configurations and functionality in the JBoss EAP xPaaS image compared to the regular release of JBoss EAP. Documentation for other JBoss EAP functionality not specific to the JBoss EAP xPaaS image can be found in the JBoss EAP documentation on the Red Hat Customer Portal.

Chapter 6. xPaaS Image for Red Hat JWS

The Apache Tomcat 7 and Apache Tomcat 8 components of Red Hat JBoss Web Server 3 are available as containerized xPaaS images that are designed for use with OpenShift Enterprise 3.0 and later.

However, there are significant differences in the functionality between the JBoss Web Server xPaaS images and the regular release of JBoss Web Server. Documentation for other JBoss Web Server functionality not specific to the JBoss Web Server xPaaS images can be found in the JBoss Web Server documentation on the Red Hat Customer Portal.

Chapter 7. xPaaS Image for Red Hat JBoss A-MQ

Red Hat JBoss A-MQ is available as a containerized xPaaS image that is designed for use with OpenShift Enterprise 3.0 and later. It allows developers to quickly deploy an A-MQ message broker in a hybrid cloud environment.

However, there are significant differences in supported configurations and functionality in the JBoss A-MQ image compared to the regular release of JBoss A-MQ. Documentation for other JBoss A-MQ functionality not specific to the JBoss A-MQ xPaaS image can be found in the JBoss A-MQ documentation on the Red Hat Customer Portal.

Chapter 8. xPaaS Image for Red Hat JBoss Fuse (Fuse Integration Services)

Red Hat JBoss Fuse is available as a containerized xPaaS image, known as Fuse Integration Services, that is designed for use with OpenShift Enterprise 3.1. It allows developers to quickly deploy applications in a hybrid cloud environment. In Fuse Integration Services, application runtime is dynamic.

However, there are significant differences in supported configurations and functionality in the Fuse Integration Services compared to the regular release of JBoss Fuse. Documentation for other JBoss Fuse functionality not specific to the Fuse Integration Services can be found in the JBoss Fuse documentation on the Red Hat Customer Portal.

Chapter 9. xPaaS Image for Red Hat JBoss BRMS (Decision Server)

Red Hat JBoss BRMS is available as a containerized xPaaS image, known as Decision Server, that is designed for use with OpenShift Enterprise 3.1 as an execution environment for business rules. Developers can quickly build, scale, and test applications deployed across hybrid environments.

However, there are significant differences in supported configurations and functionality in the Decision Server xPaaS image compared to the regular release of JBoss BRMS. Documentation for other JBoss BRMS functionality not specific to the Decision Server xPaaS image can be found in the JBoss BRMS documentation on the Red Hat Customer Portal.

Chapter 10. xPaaS Image for Red Hat JBoss Data Grid

Red Hat JBoss Data Grid is available as a containerized xPaaS image that is designed for use with OpenShift Enterprise 3.1. This image provides an in-memory distributed database so that developers can quickly access large amounts of data in a hybrid environment.

However, there are significant differences in supported configurations and functionality in the JBoss Data Grid xPaaS image compared to the full, non-PaaS release of JBoss Data Grid. Documentation for other JBoss Data Grid functionality not specific to the JBoss Data Grid xPaaS image can be found in the JBoss Data Grid documentation on the Red Hat Customer Portal.

Chapter 11. Known Issues

The following are the current known issues along with any known workarounds:

Decision Server and Intelligent Process Server

  • https://issues.jboss.org/browse/CLOUD-609: KIE.SERVER.REQUEST queue consumer not transacted

    The first request after an A-MQ message broker restart produces no response when using the A-MQ interface to the IPS. The request message is consumed, even though there is an exception.

    There is no known workaround.

  • https://issues.jboss.org/browse/CLOUD-610 KIE server consumes request messages before all KIE containers are deployed

    The kie-server starts handling messages from the KIE.SERVER.REQUEST queue before the KIE containers are in the STARTED state. This issue causes problems with scaling and pod restarts.

    There is no known workaround.

  • https://issues.jboss.org/browse/CLOUD-874 kie-server deployment sometimes fails with A-MQ clients

    The IPS pod sometimes fails to start up with A-MQ clients running, during an IPS pod restart.

    There is no known workaround.

  • https://issues.jboss.org/browse/CLOUD-875 A-MQ responses to clients are PERSISTENT and have unlimited TTL, may clog the response queue

    The kie-server replies to A-MQ clients are persistent and have unlimited TTL. This causes the response queue to grow if the A-MQ client disconnects, which results in the A-MQ message broker to eventually block any more messages pushed to the response queue.

    To get around this issue, purge the response queue manually.

  • https://issues.jboss.org/browse/CLOUD-878 Empty responses from kie-server for JMS clients during startup

    JMS client calls for UserTaskService methods can get lost while restarting a pod. The client does not get an error message or notification of failure.

    There is no known workaround.

SSO

  • https://issues.jboss.org/browse/CLOUD-747: SSO server starts before DB is available.

    Due to the lack of a dependency mechanism in OpenShift, the SSO server starts before the corresponding database is available. The liveness probe in OpenShift eventually re-starts the SSO pod, but this can take up to 3 minutes.
    There is no known workaround.

  • https://issues.jboss.org/browse/CLOUD-712 Keycloak admin client doesn’t use SNI extension

    Since the KeyCloak admin Java client does not use SNI, it is not possible to use this client from outside of OpenShift using the HTTPS protocol.

  • https://issues.jboss.org/browse/CLOUD-637 Router node IP address, instead of the end-user client IP address, are logged on login failures

    On invalid login requests, the SSO image logs the OpenShift router’s node IP address instead of the end-user’s client IP. This information is not helpful in debugging log in failure requests.

  • https://issues.jboss.org/browse/CLOUD-674 Not giving certificates to SAML deployment causes failure

    If the following environment variables are not defined, the SSO deployment will fail even if no SAML application is deployed: SSO_SAML_KEYSTORE, SSO_SAML_CERTIFICATE_NAME, and SSO_SAML_KEYSTORE_PASSWORD.

    As a workaround, you may pass the HTTPS secret using the SSO_SAML_KEYSTORE_SECRET variable.

  • https://issues.jboss.org/browse/CLOUD-799 Support for EAR

    The SSO auto-registration scripts do not work with EAR archives and there is no current workaround for this issue.

  • https://issues.jboss.org/browse/CLOUD-555 SSO logs throws duplication error after reset while backed up with db

    The SSO pod tries to to create admin user with admin password at start up in the master realm. This causes duplication issues, if SSO is backed up with db, although the application starts correctly.

    To workaround this issue, delete the duplicate admin user and restart the pod.

JWS

  • https://issues.jboss.org/browse/CLOUD-57: Tomcat’s access log valve logs to file in container instead of stdout

    Due to this issue, the logging data is not available for the central logging facility. To work around this issue, use the oc exec command to get the contents of the log file.

  • https://issues.jboss.org/browse/CLOUD-153: mvn clean in JWS STI can fail

    Cleaning up after a build in JWS STI is not possible, because the Maven command mvn clean fails. This is due to Maven not being able to build the object model during startup.

    To work around this issue, add Red Hat and JBoss repositories into the pom.xml file of the application if the application uses dependencies from there.

  • https://issues.jboss.org/browse/CLOUD-156: Datasource realm configuration is incorrect for JWS

    It is not possible to do correct JNDI lookup for datasources in the current JWS image if an invalid combination of datasource and realm properties is defined. If a datasource is configured in the context.xml file and a realm in the server.xml file, then the server.xml file’s localDataSource property should be set to true.

EAP

  • https://issues.jboss.org/browse/CLOUD-61: JPA application fails to start when the database is not available

    JPA applications fail to deploy in the EAP OpenShift Enterprise 3.0 image if an underlying database instance that the EAP instance relies on is not available at the start of the deployment. The EAP application tries to contact the database for initialization, but because it is not available, the server starts but the application fails to deploy.

    There are no known workarounds available at this stage for this issue.

  • https://issues.jboss.org/browse/CLOUD-158: Continuous HornetQ errors after scale down "Failed to create netty connection"

    In the EAP image, an application not using messaging complains about messaging errors related to HornetQ when being scaled.

    Since there are no configuration options to disable messaging to work around this issue, simply include the standalone-openshift.xml file within the source of the image and remove or alter the following lines related to messaging:

    Line 18:
    
    <!-- ##MESSAGING_EXTENSION## -->
    
    Line 318:
    
    <!-- ##MESSAGING_SUBSYSTEM## -->
  • https://issues.jboss.org/browse/CLOUD-161: EAP pod serving requests before it joins cluster, some sessions reset after failure

    In a distributed web application deployed on an EAP image, a new container starts serving requests before it joins the cluster.

    There are no known workarounds available at this stage for this issue.

EAP and JWS

  • https://issues.jboss.org/browse/CLOUD-159: Database pool configurations should contain validation SQL setting

    In both the EAP and JWS images, when restarting a crashed database instance, the connection pools contain stale connections.

    To work around this issue, restart all instances in case of a database failure.

Fuse Integration Services

  • https://issues.jboss.org/browse/OSFUSE-112: karaf /deployments/karaf/bin/client CNFE org.apache.sshd.agent.SshAgent

    Attempting to run the karaf client in the container to locally SSH to the karaf console fails.

    Workaround: Adding both shell and ssh features make the client work. It will log the warning errors in the logs.

    $ oc exec karaf-shell-1-bb9zu -- /deployments/karaf/bin/client osgi:list

    These warnings are logged when trying to use the JBoss Fuse bin/client script to connect to the JBoss Fuse micro-container. This is an unusual case, since the container is supposed to contain only bundles and features required for a micro-service, and hence does not need to be managed extensively like a traditional JBoss Fuse install. Any changes made using commands in the remote shell will be temporary and not recorded in the micro-service’s docker image.

  • https://issues.jboss.org/browse/OSFUSE-190: cdi-camel-jetty S2I template incorrect default service name, breaking cdi-camel-http

    The cdi-camel-http quickstart expects the cdi-camel-jetty service to be named qs-cdi-camel-jetty. In the cdi-camel-jetty template however, the service is named s2i-qs-cdi-camel-jetty instead by default. This causes the cdi-camel-http to output this error when both are deployed using the S2I with default values.

    Workaround: Set the cdi-camel-jetty SERVICE_NAME template parameter to qs-cdi-camel-jetty.

  • https://issues.jboss.org/browse/OSFUSE-193: karaf-camel-rest-sql template service name too long

    oc process karaf-camel-rest-sql template fails with the following error: The Service "s2i-qs-karaf-camel-rest-sql" is invalid. SUREFIRE-859: metadata.name: invalid value 's2i-qs-karaf-camel-rest-sql', Details: must be a DNS 952 label (at most 24 characters, matching regex [a-z]([-a-z0-9]*[a-z0-9])?): e.g. "my-name" deploymentconfig "s2i-quickstart-karaf-camel-rest-sql" created

    Workaround: Set SERVICE_NAME template parameter to karaf-camel-rest-sql.

  • https://issues.jboss.org/browse/OSFUSE-195: karaf-camel-amq template should have parameter to configure A-MQ service name

    The application template for A-MQ deployments uses a suffix for every transport type to distinguish. Hence there should be a configurable parameter for setting the service name as environment parameter A_MQ_SERVICE_NAME.

A-MQ

There are no known issues in the A-MQ image.