Jelastic 4.3/4.4

This document is preliminary and subject to change.

In this document, you will find all of the new enhancements and visible changes included in the Jelastic PaaS & IaaS 4.3 and 4.4 releases:

For detailed information on using any of Jelastic’s features, please refer to the users’ documentation.

External IPs Swap via CLI

In the current Platform update, the functionality of Jelastic CLI was complemented with a new method, that allows to swap external IP addresses among two nodes or, in case one of them does not have its own Public IP bounded, to transfer an address to another instance. Herewith, this operation can be handled for any nodes within the confines of a single account, i.e. even for the ones, that belong to different environments or run different services. So, in order to accomplish this, just a single line of code should be run:

~/jelastic/environment/control/swapextips --envName {env_name} --srcnodeid {src_node_id} --dstnodeid {dst_node_id}

This command requires the following values to be specified within the highlighted parameters:

  • {env_name} - name of the environment, which comprises the server with Public IP you’d like to swap/move
  • {src_node_id} - the exact ID of the node (from the stated environment) the required Public IP is attached to
  • {dst_node_id} - ID of the target node (can belong to any environment at your account)

It will take a few minutes for all the necessary operations to be completed.

Note: This process may cause a short-term unavailability of the corresponding Public IP address(es), for approximately ~8-10 seconds.

After that, you’ll be shown the details on current IPs of the stated nodes within the method output.

Note that while swapping, nodes of the following types will be automatically restarted for the necessary changes to be applied: GlassFishApache-PHPApache-RubyNGINX-PHPNGINX-Ruby. This is required for forcing the corresponding services to start listening on new IPs.

Herewith, if operating with VPS or Docker containers, you have to define the necessity of the appropriate instance restart on your own and perform it manually if needed (as it depends on a particular service, running inside). In such a way, you can be sure that the operation of IPs swap won’t cause the unrequired downtime of your app.

More info

Back to the list of Improvements

PHP 7 Support (4.3/4.4)

A new major version of PHP server-side scripting language, that takes almost two years for being developed and polished, have been finally released under the PHP 7 name. Being based on the refactored Zend Engine called PHPNG (PHP Next Generation), it shows a significant capacity boost compared to the legacy versions. This allows to increase your PHP applications’ performance in up to 2 times just through upgrading the server’s engine version it is running on.

Also, the great emphasis was made on the language syntax enhancements - namely, removal of the previous versions’ deprecated functionality and simultaneous improvement of language consistency. The detailed information on new features and backward incompatibility issues can be examined at the official Migrating from PHP 5.6.x to PHP 7.0.x document.

As for the specifics of PHP 7 integration at Jelastic PaaS, this resulted in the following changes of the supported modules’ list for the nodes, running on this engine version:
  • removed - mysql (deprecated, use mysqli instead)
  • added - gearman, mongodb (to be used instead of mongo one)
  • currently unavailable for PHP 7 (will be added upon being developed) - event, intl, mysqlnd_ms, mysqlnd_qc, ncurses, solr, solr2, xcache

At the Jelastic dashboard, the newest version of PHP engine can be found alongside the preceding ones (namely - PHP 5.3, 5.4, 5.5 and 5.6) for being selected during the environment creation or while changing its topology.

The Jelastic 4.4 release is delivered with the latest PHP 7.0.2 engine, which includes a number of security and bug fixes, whilst Jelastic 4.3 provides the 7.0.0 PHP version. In addition, the next changes in the in-built PHP modules’ list were implemented:
  • provided support of the previously unavailable for PHP 7 extensions: gearman, intl, solr, solr2, oauth, gmp (for legacy PHP containers on the top of CentOS 5 distribution)
  • with an aim to simplify the migration of the already existing applications to the newest engine version, the rebuilt and adjusted mysql module (excluded within the preceding 4.3 version) was appended
  • several new extensions were added for all of the provided PHP versions, namely: pdo_dblib, pdo_oci, pdo_odbc, readline, recode, sysvmsg, enchant, odbc. See the details below.

More info

Back to the list of Improvements

MongoDB Driver for PHP Update

In order to work with the MongoDB database, PHP requires a special low-level driver, that was recently updated. Thus, in the present 4.3 Jelastic Release, the new module was added to the pool of extensions, provided for PHP app servers by default. Herewith, the deprecated driver ( still remains available to ensure support of the already launched applications, built on its basis; however, we recommend to consider the latest driver version for your new projects, whilst taking into the consideration that both these modules implement different API, so the existing libraries, that use the legacy driver, should be rebuilt for working with the new one.

Just as before, in order to establish the connection between your PHP application server and MongoDB node, the appropriate module should be enabled beforehand. This can be performed directly within the dashboard by entering the app server Configs, uncommenting the required extension within the etc > php.ini file and restarting the node in order to apply new settings.

More info

Back to the list of Improvements

PHP Modules List Refactoring (4.3/4.4)

The Jelastic PaaS provides the most popular and frequently used PHP modules out-of-box, i.e. they are included to the default PHP application servers’ builds. Such embedded basis allows to launch most of the applications on fly, without any code changes required.

However, as the number of extensions is constantly growing, it was decided to shorten the list of active modules to the several most commonly used ones, while the rest of them became disabled by default (i.e. became “dynamic”). In such a way, the amount of consumed memory at a bare server reduces, being revealed from the unrequired services running, while any of the necessary modules still can be enabled manually in a few easy steps. As a result, all the newly created PHP app server containers will be launched cleaned up, with a lower level of default resource consumption and more flexible extensions’ configurability.

  • The list of modules, that were removed from the active ones and became dynamic, can be seen here.
  • Note that in case of switching engine version to the newly added PHP 7 one for legacy PHP containers (i.e. that were created before 4.3 Platform upgrade and, thus, include old version of the configuration file), you may require to manually re-define the necessary modules from the list above within the php.ini file. For that, use the line of the following type:

    extension = {extension_name}.so

    The complete list of modules (both in-built and dynamic ones) is specified at the dedicated documentation page and within the introductory comments of the etc > php.ini configuration file. Further, at the same file, each dynamic extension has its own section, where it can be enabled (through simple uncommenting of the corresponding string) and configured if needed.

    Physically, all modules are located at the dedicated modules server folder, where you can also upload your custom extensions and consequently activate them via the same php.ini file.

    Within the 4.4 Platform release, a bunch of new modules were implemented for all of the provided PHP engines, namely:,,,,,, and

    Also, the extension support was added for PHP 5, both of the provided 5.5 and 5.6 versions (previously, it was available for the 5.3/5.4 PHP engine only).

    More info

    Back to the list of Improvements

    OpenSSL Update

    OpenSSL is an open source toolkit, that implements Secure Sockets Layer (SSL) and Transport Layer Security (TLS) network protocols. The openssl command-line tool is pre-installed at all Jelastic containers and can be used for handling various security-related operations, like public/private keys management, SSL/TLS client-server testing, etc.

    Recently, the substantial security update has been implemented for all of the currently supported OpenSSL versions, intended to fix a number of revealed vulnerabilities. Due to this fact, the current Jelastic Platform release provides the throughout update of OpenSSL packages at all containers (including the already existing ones) to their latest versions, provided for CentOS (as it is used as a basic OS template for all Jelastic containers):
    • for centos 6 (i.e. for containers, created before 4.0 platform upgrade) - openssl-1.0.1e-42.el6.x86_64.rpm, openssl-devel-1.0.1e-42.el6.x86_64.rpm
    • for centos 7 - openssl-1.0.1e-42.el7.9.x86_64.rpm, openssl-devel-1.0.1e-42.el7.9.x86_64.rpm, openssl-libs-1.0.1e-42.el7.9.x86_64.rpm

    Back to the list of Improvements

    Node.js Engine Update

    Node.js is a popular open source cross-platform lightweight runtime, implemented on the top of the Chrome's V8 JavaScript engine. At Jelastic, Node.js hosting is provided based on the cartridge packaging model and offers an easy way to build the highly performant, scalable network applications.

    Commonly, the Node.js packages are dependent on OpenSSL (as it is linked to binaries during build process), which receives some security fixes recently. Thus, with an aim to prevent the possible malfunctions and vulnerabilities use, another Node.js patch-level update was released, which also includes some other security defects elimination (like threats of service denials and out-of-bounds access)

    Striving to ensure the highest level of security for our users, the abovementioned patch was applied to all of the provided Node.js engine versions (namely: 0.10.41, 0.12.9, 4.2.3) within the Platform upgrade to 4.3.

    More info

    Back to the list of Improvements

    Software Stack Versions

    The component templates versions have been updated to their latest versions since the previous release:

    StackJelastic 4.3Jelastic 4.4
    Tomcat 66.0.446.0.44
    Tomcat 77.0.627.0.62
    Java 61.6.0_451.6.0_45
    Java 71.7.0_791.7.0_79
    Java 81.8.0_451.8.0_45
    MariaDB5.5.42 / / 10.0.17
    MySQL5.6.24 / / 5.7.7
    NGINX Ruby1.
    Node.js0.10.41 / / 0.12.9

    Back to the list of Improvements

    Bug Fixes

    In the table below, you can see the list of bug fixes in Jelastic PaaS 4.3:

    Jelastic 4.3
    JE-24113The list of available tags is retrieved not via daemon while a custom Docker image addition
    JE-24123Unability to add custom Docker image in case a maintainer name includes the “_” symbol
    JE-24165The CentOS 7-based Docker images do not work properly if including the packages, that depend on systemd-container daemon