Bug fixes

  • Fixed the parsing of a configured SNMP notification target to allow the - character in the middle of the hostname. (#423328)


Bug fixes

  • Fixed incorrect handling of a partial send failure, for the last message to send from the transmit queue, in Savanna scatter-cast. (#219477)

  • Fixed MemDB retained size accounting when the key for a deleted but not yet GC’d entry is reused. (#337944)

  • Removed preconfigured SNMPv3 keys from the default configuration to reduce opportunities for unauthorised access. For new installs these keys must be set via the setsnmpuserdetails rhino-console command before enabling the SNMPv3 engine. By default only the v1 and v2c engines are enabled, this behaviour is unchanged.


Bug fixes

  • Removed the -XX:CMSTriggerInterval option from the Rhino default CMS garbage collection options as it causes heap fragmentation over time. (RHI-6830)

  • Fixed a NullPointerException when importing a declarative configuration bundle that referenced a service with an install level of INSTALLED. (RHI-6802)

  • Fixed error handling when timeout parameter to entered incorrectly. (RHI-6757)


Bug fixes

  • Fixed an issue where replicated SLEE timers did not have globally unique timer identifiers, meaning a replicated timer failed over to another node could be confused in an SBB with a timer locally created on that node. (RHI-6761)


Log4j 2 CVE-2021-44228

Updated Log4j 2 dependency to v2.17.0 in response to recent CVEs.

For background, please refer to:

Rhino and Rhino Element Manager (REM) versions 2.6.0.x, 2.6.1.x, 2.6.2.x, 2.7.0.x, and 3.0.0.x all depend on Log4j 2.

These releases all ship with default log patterns which include the use of %m{nolookups}. While originally included in the defaults for performance reasons, the inclusion of %m{nolookups} is also described as a "temporary mitigation" in some relevant security commentary, for example

As far as Rhino is concerned, internal testing has determined that even when the default logging configuration is modified to remove the %m{nolookups} pattern, no external lookups are possible via JNDI remote classloading.

Rhino uses JNDI to implement JSLEE specification requirements, and as such provides its own custom implementation of InitialContextFactory by specifying the java.naming.factory.initial setting in an embedded file. The JNDI contexts provided by this factory do not provide an LDAP lookup facility.

As a consequence of the custom JNDI contexts provided, Rhino is not thought to be vulnerable to any exploits of this nature.

Unlike Rhino, REM does not use a custom InitialContextFactory and will therefore be vulnerable if {nolookups} is removed from the default logging pattern.

Note that in addition to CVE-2021-44228, there are other CVEs fixed by updating to Log4j v2.17.0.

Accordingly, all releases of Rhino and REM that include Log4j 2 are being released with this updated Log4j dependency.

All releases prior to 2.6.0.x do not use Log4j 2, and therefore do not contain this vulnerability.


Bug fixes

  • Improved error handling when an invalid BulkStreamHandle is received. (RHI-6602)

  • Fixed a memory leak in the key/value store that occurred if a non-transactionally started activity was removed in its first generational update (for example, if no SBB processed any events fired on an activity during its lifetime) or if an activity remove transaction completed committing before a previous update transaction to the same activity completed committing. Also added a garbage collector into the key/value store that will clean up this kind of leaked state if it happens in other unknown circumstances. New configuration options for this garbage collector have been added in rhino-config.xml. (RHI-6724)


  • Add support for --timeout option to This option specifies a maximum period to wait for a graceful shutdown to complete before terminating the node. (RHI-6722)

  • Added Microsoft to the list of officially supported JDK vendors. (RHI-6623)

  • Added Eclipse Foundation to list of unofficially supported JDK vendors. (RHI-6705)


Bug fixes

  • Fixed race condition which could cause SessionOwnershipActivity to rarely return an incorrect value from queryInProgress().


Bug fixes

  • Fixed a NullPointerException that could happen during convergence if a service that had been detected as needing a convergence check was uninstalled before the check actually occurred. (RHI-6330)

  • The deployment work directory for the Activity Context Naming Facility support classes will now be cleaned up before use on node restart if it already exists. This fixes a problem where Rhino may use a jar from a previous deployment rather than the current one, if the management database had been reinitialised without deleting the work directories. (RHI-6612)

  • Fixed incorrect MBean operation permissions on ResourceManagementMBean resource adaptor entity desired state mutator methods that allowed any user with read permission to change the desired state of a resource adaptor entity, more so without that activity being recorded in the management audit log. (RHI-6637)

  • Fixed a bug where system property placeholders in SNMP fields would not be substituted. (RHI-6644)

  • Fixed a bug in actual state convergence after a declarative config state import that could cause activation of a service to happen too early and thus fail. This would happen when the service depended on a resource adaptor entity link name binding bound to a resource adaptor entity that needed to be created as a result of the import. The service activation could have potentially failed on any node other than the one with the lowest node ID. (RHI-6647)

  • Fixed a bug in declarative config import while verifying resource adaptor entity config properties whereby a resource adaptor was not able to access its usage parameter sets during the relevant callbacks. (RHI-6655)

  • Fixed an AccessControlException related to use of the Netty library where the /etc/os-release is not present. (RHI-6669)


Bug fixes

  • Fixed a bug in convergence stats querying where getting the age of the oldest convergence task would throw an NPE if the task was completed concurrently. (RHI-6454)

  • Startup flags for such as -p and -s are now preserved for restart cycles (ie. when using the -k option) if the node was requested to activate the primary component but this failed for unexpected reasons causing the node to die. This means that the node will reattempt to activate the primary component on its next restart rather than forget it was asked to do so. (RHI-6468)

  • Fixed a bug in convergence scheduling which would add another convergence execution task for every recheck while not converged. (RHI-6596)

  • Added a system property ldap.casesensitive in LDAP login module to allow case-insensitive search. This property defaults to true to match prior behaviour. (RHI-6606)

  • Fixed a defect in the LDAP login module when groups without members caused authentication attempts to fall-back to a file based authentication (RHI-6607)


  • Added platform cluster topology stats which reports on the number of each type of node in the cluster (booting, event router, or quorum node) along with the quantity of event router nodes in each possible SLEE state (stopped, running, etc). (RHI-6609)

  • Added statistics monitoring support for service links underneath the Services root parameter set. (Service links were previously only supported underneath the SLEE-Usage root parameter set.) (RHI-6573)


Bug fixes

  • Fixed another issue where connections to the LDAP server are left open indefinitely, in this case only after an authentication failure while using search mode. (RHI-6585)


  • Updated to exit with the return code of the Rhino process. (RHI-6597)


Bug fixes

  • Fixed a pessimistic lock ordering issue that could cause deadlock lock timeouts when profile queries using unindexed profile attributes were run concurrently. (RHI-6434)

  • Fixed exception in the listActiveAlarms command when an alarm is cleared while the command is executing. (RHI-6563)


  • Added a Life Time sample statistic to the Activities parameter set type. (RHI-6556)

  • Added statistics for garbage collection duration, interval and period, and for memory pool collection count and collected bytes. (RHI-6569)


Bug fixes

  • Fixed a stack recursion bug that occurred if an SBB used an SbbLocalObject to invoke a method on itself from within sbbLoad(). (RHI-6379)

  • Ensure shutdown does not block if a shutdown is attempted while Rhino is starting up or already shutting down. (RHI-6439)

  • Fixed rhino-export functionality when handling unicode. (RHI-6463)

  • Fixed an issue where connections opened by Rhino to the authentication LDAP server are left open indefinitely. (RHI-6464)


Bug fixes

  • Fixed a race condition in Session Ownership Activity end that could cause an UnrecognizedActivityHandleException if the activity became unreferenced while outstanding requests were still in progress. (RHI-6355)

  • Fixed a concurrency issue in profile table queries operating on non-indexed profile attributes that could lead to SBB transaction failure due to a javax.slee.NoSuchObjectLocalException being thrown mid-query if a profile had been concurrently removed by another transaction. (RHI-6429)


  • Added "Red Hat, Inc." to the list of supported JVM vendors. Red Hat and CentOS JDK builds after 11.0.8 have this as the vendor string. Added a link to the Rhino compatibility guide from the warning message and alarm message about unsupported Java versions. (RHI-6389)

  • Include list of profile CMP field names in error messages for declarative imports that contain invalid field names. Declarative imports use CMP field names which are not otherwise visible to the user, so this helps troubleshoot problems with such imports. (RHI-6366)


Bug fixes

  • Fixed an issue that could cause resource adaptor entity callbacks to be made out of FSM sequence. For example, an raInactive() callback could be made without the resource adaptor entity having previously received raActive() and raStopping() callbacks. (RHI-6302)

  • Added more validation logic to assess the supplied resource adaptor entity config properties when creating a resource adaptor entity or updating its config properties using ResourceManagementMBean. (RHI-6309)

  • Fixed NPEs that could occur when a resource adaptor entity or namespace was removed when the SLEE in the namespace was concurrently transitioning from the STOPPING to the STOPPED state. (RHI-6319)

  • Fixed a concurrency issue in internal resource adaptor entity state management that could cause an SBB to receive a javax.slee.UnrecognizedActivityException when trying to obtain an activity context for a legitimate activity. (RHI-6321)

  • Fixed encoding/decoding of declarative configuration so that both import and export paths use UTF-8 consistently. (RHI-6346)


  • Added new management operations to ConfigManagementMBean to report on convergence completion status and to generate a full convergence report. Added a new management operation to NodeHousekeepingMBean to return a report of the default and per-node desired states of all stateful entities in the current namespace. Added corresponding rhino-console commands: isconverged, reportconvergencestatus, and listdesiredstates. (RHI-6180)

  • Replicated MemDB instances can no longer be configured with stripe counts greater than one due to the potential for corrupted state after node failures. (RHI-6318)

  • A default-sbb-tracer-levels element is now valid for service declarations in a declarative import config fragment. It allows tracer configs to be specified which will be automatically applied to all SBBs in the service during import, except where any of those SBBs define their own configuration for the same tracer(s). (RHI-6320)

  • XML exports from Rhino now include a task invocation to wait for convergence after every existing task that sets service or resource adaptor entity desired state. This ensures that each desired state change is fully applied before the next Ant task runs and prevents the import process from potentially failing due to lock timeouts caused by conflicts between further desired state updates and concurrent convergence-driven operations within Rhino. (RHI-6328)

  • Updated bundled Oracle JDBC driver to version 19.7. (RHI-6289)

  • Added new config import option to control resource adaptor entity deactivation and reactivation when configuration properties changes require a resource adaptor entity to be deactivated. Defaults to storing the new configuration but not deactivating the resource adaptor entity. (RHI-6290)


Rhino 3.0.0 introduces two major new features: support for Java 11 and declarative configuration.

Java 11

Rhino 3.0.0 depends on and requires Java 11, with both Open JDK and Oracle JDK variants of Java tested and supported.

Due to the significant changes between the previously supported Java 8, and the more modern Java 11, this is expected to be disruptive for customers with custom developed applications deployed into Rhino. To assist with the version upshift, we have compiled notes based on our own experiences in updating applications. These can be found in the Rhino JDK11 Deployable Unit Migration Guide.

Rhino Declarative Configuration

Rhino 3.0 introduces a fundamental change to the way Rhino SLEE component configuration is handled. A new declarative configuration system decouples the configuration of components and their actual activation state from their declared desired state. This applies to Services, Resource Adaptor Entities, and the activation state of the SLEE. This allows the platform to be given an intended configuration, with Rhino asynchronously making the required component state transitions to achieve the new configuration. The goal of these changes is to both make component state easier to manage and to facilitate more flexible and reliable integration with cloud-based solutions and modern configuration management approaches.

With these changes comes the deprecation of the symmetric activation state mode. This is replaced by a combined model where the SLEE, Services, and Resource Adaptor Entities may each concurrently have both 'default' and 'per-node' desired state. Per-node state is optional and can be created (and removed) as required as a node-specific override to the cluster-wide default state.

Complementing the new configuration system, a new declarative import/export format has been introduced (see importdeclarativeconfig/exportdeclarativeconfig in rhino-console) which can be used to atomically make changes to the desired configuration of Services, Resource Adaptor Entities, SLEE activation state, and Profiles, with changes not being applied in the event that any of the changes would fail, for example due to profile validation errors.

New Ant tasks have been added for the management of desired state (SetServiceDesiredStateTask, SetRAEntityDesiredStateTask, WaitTilConvergedTask) and these have been integrated into the imperative-style configuration exports produced by the exportall rhino-console command. Older exports should continue to work assuming the included deployable units are also still compatible with Java 11.

It should be noted that the new declarative configuration functionality covers the management of Service configuration and activation state, Resource Adaptor Entity configuration and activation state, SLEE activation state, and Profile Tables and Profiles. The remainder of the platform state, in the form of deployable units, service bindings, core platform configuration and the like is not covered by these changes. REM has not been updated with explicit handling of the new declarative functionality. Management applications built against pre-3.0 versions of Rhino should continue to function as the superseded imperative state management APIs have been updated to ensure backwards compatibility where possible.

Please see the Declarative Configuration section of the Rhino Administration Guide for more complete information regarding the concepts, terminology, and management examples using the new declarative configuration functionality. A quick listing of the new declarative configuration commands can be found in rhino-console under help declarative.

Bug fixes

  • Rhino now raises an alarm upon node restart if no valid platform license is installed. (RHI-5647)

  • Fixed a memdb state referencing issue that in rare circumstances could have led to invalid state being accessed. (RHI-5858)

  • Fixed JMX API compliance bug in LoggingManagementMBean. The getLoggingProperties method now returns Map<String,String>. (RHI-5891)

  • Fixed an issue where the SAS facility would throw a NullPointerException if getting the trail for an activity failed because the activity was not known to Rhino. (RHI-5893)

  • Fixed a database concurrency exception that occurred when committing a user transaction if that transaction had at some point attempted to create a profile already created by a concurrent user transaction. (RHI-6011)

  • A component that is shadowing other components can no longer be uninstalled from the SLEE until the shadows are removed. (RHI-6026)

  • rhino-console commands which manipulate profile attributes can now include commas in array entries by double-escaping the comma character. e.g. "[Entry1, Entry2\\, with comma, Entry3]". Ant tasks for manipulating profile attributes can also now include commas in array entries, but require a single escape slash instead of double. e.g. "[Entry1, Entry2\, with comma, Entry3]". (RHI-6095)

  • Fixed a lack of namespacing bug with lock manager stats parameter sets for replicating resource adaptor entity activity handlers. This resulted in replicating resource adaptor entities with the same name in different namespaces to share the same lock manager stats parameter set, which generally was fine until one of the resource adaptor entities was removed. This caused the shared stats parameter set to be removed, which meant that the resource adaptor entities in other namespaces could no longer be removed without error, and that led to classloader leaks. (RHI-6167)

  • Fixed an issue with scattercast management operations that would cause a java.lang.AssertionError: Scattercast Management command initiated while another is executing after processing multiple scattercast management requests on different nodes. (RHI-6178)

  • Fixed non-unique referencing of deployable units across namespaces during node start component redeployment which could have caused dependent components to be redeployed earlier than they should have been when deployable units with the same URL were deployed into multiple namespaces. (RHI-6187)

  • Fixed an event router race condition that could cause an event scheduled for processing to be erroneously delivered if its associated activity was suspended for delivery concurrently with the processing of that event. (RHI-6188)

  • Fix two bugs when creating a SessionOwnershipActivity. The invoking SAS trail was not propagating to the newly created SessionOwnershipActivity. A race could occur between the create, attach, and querying the Session Ownership Store and a Session Ownership event being delivered. This could result in the first Session Ownership event being delivered without invoking the attached SBB entity. (RHI-6211)

  • Fixed unpredictable file handle usage during deployment operations caused by missing file manager close after internal javac compilation. The related file handles would historically be leaked until garbage collected. (RHI-6220)

  • Fixed a heap leak that occurred when the logging configuration was updated frequently. (RHI-6229)

  • Fixed a memory leak that occurred whenever a stats parameter set was deregistered within Rhino, for example when a service was undeployed. (RHI-6230)

  • Fixed a thread leak when removing a user-defined namespace where the SLEE was not in the STOPPED state. (RHI-6250)

  • Fixed a thread leak when replicated resource adaptor entities are removed from the SLEE. (RHI-6252)

  • Fixed a bug that prevented resource adaptor entity raInactive() callbacks being made at the appropriate time when the SLEE was in the STOPPING state. (RHI-6260)

  • Fixed a NullPointerException when adding a service binding to an unverified copied service component. (RHI-6268)

  • Fixed an untended retention of some OCBB state when idle OCBB persistent state objects were stored in their object pool. (RHI-6293)


  • Added basic exit code handling for rhino-console.

    rhino-console will now return with a non-zero exit code if there were usage errors or errors during command execution.

    To restore the exit code behaviour from previous Rhino versions (where failed command execution did not return with an error code), uncomment the rhino.console.legacy-exit-codes=true line in client/etc/

    See rhino-console --help for full list of exit codes. (RHI-3202)

  • The session ownership store now has a configurable cap on the maximum number of outstanding requests that can be queued for processing. A request is immediately failed if queuing it would exceed the queue capacity limit. (RHI-5898)

  • Added new flushconfiguration rhino-console command and associated RhinoHousekeeping flushConfiguration() MBean method.

    This command blocks until all currently unpersisted changes to configuration have been persisted to the management database.

    This is not required during normal use as changes are usually persisted almost immediately, but is instead intended automated environments where guarantees regarding configuration persistence are desired. (RHI-5956)

  • Profile attributes of type (or subtype of) java.util.Map now appear by default in exported profile data as structured key/value pairs rather than a single object blob. A new annotation @com.opencloud.rhino.cmp.codecs.ProfileMapCodec has been added which can be used to customise how map keys and values are exported and imported if their respective types are not automatically supported by Rhino. (RHI-5990)

  • Increased from 500 to 1500 the maximum number of profiles that a Rhino export will allow in a profile table before requiring the user explicitly select between a JMX or snapshot export. (RHI-6111)

  • Added housekeeping operations to report on the current status of key/value stores and the session ownership store in terms of whether or not all relevant keyspace and table updates have been successfully propagated to the backend Cassandra database(s). (RHI-6143)

  • Added a new transaction ID field to the management audit log. This reports a transaction ID when a user-managed transaction is in effect so that management operations connected to that user transaction are more easily identifiable. (RHI-6198)

  • Session Ownership Activities will now implicitly end in the SLEE if they are unreferenced by SBB entities, SLEE facilities, etc (ie. in the same way that Null Activities can implicitly end). An SBB must attach to a Session Ownership Activity or create a reference to it elsewhere, for example by using the Activity Context Naming Facility to bind it to a name if it wishes to keep the activity alive. Session Ownership Activities can of course still be ended explicitly by using the endActivity() method. (RHI-6200)

  • New node shutdown and reboot management APIs have added to the SleeManagamentMBean. In difference to the pre-existing APIs, these new operations do not affect a node’s existing desired state, ie. a node that restarts after such a shutdown will (attempt to) return to exactly the same state it had prior to shutdown. The new restart operations also function correctly with user-defined namespaces (whereby the pre-existing implementation did not). The,, and other similar node management scripts have been updated to default to the new shutdown/restart behaviour. The pre-existing behaviour can still be obtained however, if necessary, using the -legacy-mode command-line option as detailed in each script’s usage help message. (RHI-6204)

  • Updated the RhinoConnection interface to extend This allows consumers of this interface to use try-with-resources to ensure that the connection is closed when they have finished using it. (RHI-6222)

  • Tweaked internal javac compilation to use UnsharedNameTable instead of SharedNameTable. This eliminates heap retention via SoftReferences and provides more reliable heap behaviour during deployment operations. In the unlikely event this causes compilation problems in untested JVMs, the use of SharedNameTable can be reverted to using the undocumented internal 'com.opencloud.util.javac.sharednametable=true' system property. (RHI-6258)

New Features

  • Defined new PartitioningFacility and PartitionedActivityHandle interfaces, and extensions to the ReplicatedStorageFacility, that allow a resource adaptor to group related activity state together when it’s stored in the Cassandra key/value store. (RHI-5888)

  • Profile table create and remove are now also supported within user-managed transactions. (RHI-5906)

  • Added waittilconverged rhino-console command and Ant task that pauses further command/task execution until Rhino reaches convergence between desired and actual states. (RHI-5942)

  • Added a new boolean system property rhino.slee_restricted_lifecycle which can be used to restrict some of the flexibility offered with the new declarative state changes when using legacy APIs for SLEE state management. Specifically it restricts the SLEE start/stop operations such that they consider current actual state as well as desired state when determining whether or not the operation is valid in the current state. For example, when this option is enabled, a SLEE with a desired state of stopped can only be started if its current actual state is also stopped. Without this option enabled (the default), the operation only looks at current desired state when determining validity. (RHI-6008)

  • Added exportdeclarativeconfig and importdeclarativeconfig commands to rhino-console for managing declarative configurations. A declarative export is also possible using the new -d option with the existing rhino-export command-line tool. (RHI-6110)

Other Changes

  • The free-memory watchdog has been removed from Rhino due to the occasional spurious reporting of heap stats by the JVM. (RHI-6070)

  • Windows .bat scripts have been removed. Windows support is now provided via WSL. (RHI-6156)


Bug fix

  • The DeploymentMBean.setEnvEntries method will no longer throw an exception if given an unmodifiable map as an argument. (RHI-5929)

  • Fixed installer handling of defaults for JAVA_HOME and LOCALIPS. Removed non-settable values from defaults file. (RHI-5973)

  • rhino-console commands which manipulate profile attributes can now include commas in string array entries by double-escaping the comma character. e.g. "[Entry1, Entry2\\, with comma, Entry3]". (RHI-6095)

  • Ant tasks for manipulating profile attributes can now include commas in string array entries using a single escape slash. e.g. "[Entry1, Entry2\, with comma, Entry3]". (RHI-6095)


  • A "ZERO-length generation snapshots" warning message that could occur during some activity-related housekeeping operations has been demoted to a debug level message as it’s completely benign. (RHI-5894)


Bug fix

  • Fix internal teardown logic for failed SNMP interface bindings so that subsequent SNMP restarts do not result in duplicate registration errors. (RHI-5794)


Rhino 2.7.0 introduces the following new features

  • Expanded ReplicatedStorage API available to resource adaptors to allow retrieve and update operation behaviour to be customised when using a key/value store as the replication subsystem. (RHI-5849)

  • New implementation variants of the ActivityContextNamingFacility for SBBs to use

    • At java:comp/env/rhino/nonreplicated/facilities/activitycontextnaming is a facility that will only bind non-replicated activities and will only look up bindings in non-replicated storage. Attempting to bind a replicated activity will cause a FacilityException to be thrown.

    • At java:comp/env/rhino/replicated/facilities/activitycontextnaming is a facility that will bind non-replicated activities as well as activities replicated using the namespace’s replication resource, and will only look up names in non-replicated and namespace-replicated storage.

      • If the namespace is replicated using savanna, then this facility behaves no differently than the default ActivityContextNamingFacility implementation and can handle any activity.

      • If the namespace is replicated using a key/value store, then this facility will only handle non-replicated and key/value store replicated activities. Attempting to bind, for example, a Service Activity or Profile Table Activity, which are always replicated using savanna, will cause a FacilityException to be thrown.

    The pre-existing facility implementation remains at the standard JAIN SLEE JNDI location. Its behaviour has not changed.

Note also that the pre-existing system property acnaming.no_replicated_lookup will only continue to affect the standard facility implementation. The custom Rhino-specific variants ignore this system property. Use of this system property, which is a global switch affecting all services, is now discouraged in favour of each service using the facility variants that provide the desired behaviour. (RHI-5860)


  • Increased default configured Cassandra key/value store write thread count from 5 to 10. (RHI-5887)

  • Added new config properties to the key/value store (maxScanTimeThreshold, maxPersistTimeThreshold, and overThresholdTriggerCount) that improve resilience during periods of sustained overload. (RHI-5885)

  • Added -XX:CMSTriggerInterval=600000 to Production Rhino GC settings. This ensures a maximum interval of 10 minutes between CMS collections, improving heap behaviour in substantially idle systems. (RHI-5725)

  • Updated the Rhino certificate keystores to use the industry standard PKCS12 format rather than the legacy and proprietary JKS format. (RHI-5758)

  • Updated default heap sizes. The Rhino installer now defaults to 3GB of heap with 512MB New space. (RHI-5874)

  • Added a new listreferringcomponents command to rhino-console that will list, optionally recursively, all the SLEE components that depend on a specified component. (RHI-4921)

  • Add replication support for SAS trails attached to activities. This sends a marker containing the trail’s steering ID on each trail creation so trails recreated after failover associate with the original trail. RAs using this must call getOrCreateTrail(ActivityHandle) when resurrecting activities. Trail distribution between SAS servers is now pseudo-random, based on the steering ID. (RHI-5461)

  • Redeployment and reactivation of SLEE components on node restart has been multi-threaded to improve node restart times where multiple CPU cores are available to the Java Virtual Machine. (RHI-5687)

  • Updated configuration defaults for in-memory databases. Local (non-replicated) and K/V store databases default to 400MB.

    Updated default configuration for staging queues to match performance characteristics of modern hardware (based on an 8-vCPU VM). The queue size is now 10,000 with a 5s maximum age. The worker thread count is now 150.

    The JVM code cache configuration was also increased to 756MB. (RHI-5688)

  • Updated required Java version for Rhino installation to 1.8, and updated runtime Java version warning alarm to 1.8.0_172. This is consistent with existing documented supported Java versions. (RHI-5742)

  • The rhino-stats -l option will now include the identifier for a parameter set’s parent in its output. (RHI-5750)

  • Added a rhino-console initialglobalcleanup housekeeping operation that initiates the internal GC processes in all Rhino memdb and activity handler instances. (RHI-5783)

  • Ramp-up behaviour can now be configured for all user-defined rate limiters, not just the system input rate limiter. Ramp behaviour for user-defined rate limiters is defined in terms of limiter work units used (rather than events as the system input rate limiter uses). (RHI-5800)

  • The cancellation of a remote timer during a transaction is now reported to the owning node asynchronously during commit rather than synchronously. This allows the commit work necessary in the event router thread to complete faster, increasing event router performance. (RHI-5813)

  • Some lock contention issues in the key/value store that occurred under high load have been fixed to improve performance. (RHI-5814)

  • Made SystemType and SystemVersion configurable in SAS config. As-of Rhino 2.7.0 these attributes are mandatory when using SAS. (RHI-5824)

  • Added a -x option to rhino-stats that causes the minimum and maximum sample values to also be included alongside percentiles in stats output. (RHI-5825)

  • Increased maximum batch size for key/value store persistence writes to 80kB to allow updates to commit as single Cassandra batches. This avoids the risk of partial writes causing call failures when adopting sessions after node failover. (RHI-5827)

Bug fix

  • Fixed a memory leak that occurred in the key/value store when the pending size limit was reached and it stopped storing committed transaction state. (RHI-5885)

  • Fixed the corruption of per-node service activation state that occurred for services with an install level of VERIFIED when symmetric activation state mode was enabled. (RHI-5856)

  • Added a retainedSize stat to memdb stats parameter sets that reports the total size of state retained by the database. Retained state consists of all generations of all committed state irrespective of whether or not any of those generations are obsolete and eligible for garbage collection. (RHI-5880)

  • Fixed a regression in the Cassandra Key/Value Store’s global stats parameter set persistTime sample stat introduced in Rhino The sample stat will now report total persist-phase time as intended rather than the persistence time for individual sets of related transactions. (RHI-5879)

  • Corrected use of wrong password variables during Rhino keystore generation. (RHI-5881)

  • Fixed the cyclic raising and clearing of alarms that occurred when a key/value or session ownership store’s Cassandra connection lost quorum and was unable to execute queries. (RHI-5853)

  • Fix a case where the key/value store could persist stale generations to the backend database, overwriting more recent state. (RHI-5868)

  • Fixed a race condition during service activation between the start of the replicated ServiceActivity and ResourceAdaptor.serviceActive() callbacks being made on the nodes not involved with the creation of the ServiceActivity. The race condition meant that a resource adaptor entity responding to the callback could fire an event to an SBB that attempted to attach to the ServiceActivity, but could not do so because the activity was not yet visible on the node. Rhino will now wait and ensure that the required replicated activity state exists on the node before proceeding to make the resource adaptor callbacks. (RHI-5196)

  • Fixed a NullPointerException that occurred during service deployment if the service contained an SBB component that depended on an event type that in turn depended on a linked or shadowed library component. Fixed the absence of SBB part event type dependencies in the classloader hierarchy of deployed services. (RHI-5782)

  • Fixed PolledMemoryAppender resource leak which occurred on failed socket binding attempts. (RHI-5788)

  • The Group RMI Server, which manages management operations across cluster nodes, now checks that group RMI invocations do not leave dangling transactions. In the unlikely event that they do, the transaction is automatically rolled back and a warning alarm is raised. (RHI-5796)

  • Management operations that obtain very large quantities of data from each cluster node, such as finding all activities, SBBs, etc in a very busy cluster, will no longer have the potential of saturating cluster communications and causing group heartbeat failures and node loss. (RHI-5803)

  • The ServiceActivityFactory will no longer return a null ServiceActivity in cases where the activity has not yet started or has already ended when the activity object is requested. A FacilityException will be thrown instead. (RHI-5843)

  • Fixed various issues with memdb internal sizing statistics:

    • retained committed state size was not being updated when memdb retrieved state from a key/value store and inserted it into local state

    • when loading persistent state from an external database on node boot, the retained committed state size calculation was being performed differently than in normal operation, meaning an incorrect size was being reported

    • recent memdb concurrency improvements meant that retained committed state size and entry counts could end up being updated concurrently without appropriate thread synchronisation, leading to the possibility of inaccurate numbers over time. (RHI-5848)

  • Fixed an SBB lifecycle management issue in the event router which could cause SBB entities to have stale internal state while handling an event due to sbbLoad() not being invoked on them first when it should have been. (RHI-5867)


Bug fix

  • Fixed a miscount that caused the key/value store table statistic KeyUpdatesPending to become negative in some cases when an application disabled state persistence during a session. (RHI-5836)


  • The creation of a remote timer during a transaction is now handled asynchronously during commit rather than synchronously. This allows the event router thread to be released back to the pool faster, increasing event router performance. (RHI-5839)

  • Concurrency improvements have been made to memdb to reduce lock contention under heavy load, thereby improving performance. (RHI-5840)


Bug fix

  • Fixed a memory leak in the key/value store when a database entry became implicitly persist-disabled, due to being related to another persist-disabled transaction, after the entry had been removed from the database but before the updates for that key had been considered for persistence by the key/value store. (RHI-5838)


  • Add a new production safe debug log key to MemDB - memdb.mvcc.summary. This log key provides visibility into MemDB’s Multi-Version Concurrency Control sweeping. (RHI-5835)


Bug fixes

  • Fixed an AssertionError that occurred during key/value store persistence if, for some database key X:

    • the key was updated by a non-persist-disabled transaction

    • generationally later, the key was updated by a persist-disabled transaction

    • both transactions were stored on commit by the key/value store with the same timestamp

    • due to thread scheduling, the persist-disabled transaction was stored in relevant data structures before the non-persist-disabled transaction (RHI-5830)

  • Fixed a key/value store bug that resulted in updates awaiting persistence for any given key that appeared in multiple memdb tables to interfere with each other. This could have resulted in state being persisted to the wrong backend database table, or not being persisted at all. (RHI-5831)

  • Fixed a memdb / key/value store integration issue that meant that memdb could miss a deregistration of transaction interest callback from the key/value store when read-only transactions (from the perspective of a memdb instance) committed. These callbacks are critically important to the proper functioning of memdb’s internal garbage collection. (RHI-5832)


  • Improved the performance of determining the earliest memdb generation that a key/value store was still referencing. The previous algorithm could lead to unexpected CPU load increases under certain load conditions. (RHI-5826)


Bug fixes

  • Fixed an event router infinite looping bug that could occur if an SBB threw a runtime exception from a lifecycle callback method such as sbbLoad() or sbbStore(). (RHI-4339)

  • Updates for stats client sessions with a very small polling period are now rate limited to avoid saturation of cluster communications, which has the potential to lead to group heartbeat failures and node loss. (RHI-5779)

  • Fixed potential active namespace corruption issues when a management client invokes concurrent management operations that can affect the currently active namespace. (RHI-5780)

  • Fixed an initialisation error in the Cluster State Change Facility implementation that prevented resource adaptor entities from receiving correct cluster state information if symmetric activation state mode was in force when a node started. (RHI-5802)

  • Fixed an AssertionError that occurred in the key/value store in some scenarios that included persist-disabled SBB entity trees. (RHI-5823)


Bug fixes

  • Changes to the periodic alarm reporting period will now be reflected across all cluster nodes immediately rather than requiring a restart of nodes not handling the change request in the first instance before the change is applied. (RHI-3511)

  • Fixed a key/value store pending write scanner issue that caused it to select some transactions for persistence when they should have inherited persist-disabled status from related transactions. (RHI-5793)


Bug fixes

  • Fixed a key/value store issue that caused memdb to return state from the key/value store that was not identifiable as more recent than any other previously retrieved state for the same key, which meant that OCBB objects that had cycled through the object pool could end up being used with stale CMP state. (RHI-5653)

  • Fixed a deadlock that could occur in the remote timer server when a node leaves the cluster, leading to the node where the deadlock occurs also failing and leaving the cluster a short time later. (RHI-5754)

  • Fixed remote timer server behaviour handling connections to nodes that fail without shutting down their TCP connections cleanly. Connections will now be closed if a timer event report is not acknowledged within the required timeout period so that normal failover handling will occur for subsequent timer events destined for the same node. (RHI-5756)

  • Changed SessionOwnershipActivity.endActivity() behaviour so that it won’t end the activity until all in-flight result events have been queued. (RHI-5759)

  • Using the housekeeping operation to remove an activity context name binding from a non-resident activity will now check that the activity pkey supplied matches with the binding, rather than just blindly removing the binding regardless of what activity pkey is provided. (RHI-5763)

  • Fixed a key/value store transaction scanning issue that caused transactions committed out of natural order with mixed persistence-enabling flags to become stuck and never persisted, leading to eventual out of memory errors. (RHI-5766)

  • Fixed key/value store persistence issues when committed state that was selected for persistence was concurrently GC’ed by it’s source - either a memdb or activity handler instance. Activity handler persistence failures in particular led to a permanent jam in the key/value store that created a memory leak and eventual heap exhaustion. (RHI-5777)

  • Fixed a key/value store memory leak that occurred when an update scheduled for external database persistence was discarded rather than persisted due to the transaction batch containing a complete create/remove cycle. (RHI-5784)


  • The deprecated configuresas command has been removed from rhino-console. (RHI-5420)

  • The Session Ownership Facility tryAdopt methods will now execute exclusively in the calling thread rather than also utilising the facility’s thread pool for various intermediate functions. (RHI-5739)

  • Implemented a new cluster monitor that will raise an alarm if it detects other event-router nodes have a system clock that differs from the local node more than a configured threshold. (RHI-5762)

  • The rhino-console getactivityinfo command now includes any activity context name bindings associated with the activity in the output, and the findactivitybindings command no longer truncates long name binding names. (RHI-5764)


Bug fixes

  • The description of alarms generated by Rhino’s Watchdog subsystem are now included in Rhino’s alarm catalog. (RHI-5649)

  • Fixed the initialisation, on node restart, of object pools used by in-memory database objects for the Activity Context Naming Facility, and their subsequent cleanup when namespaces are removed. (RHI-5751)

  • Fixed a key/value store issue that caused it to erroneously discard backing database entry removals in some cases when a key update that had already been persisted to the database became persist-disabled. This could later cause problems when state that should not exist was able to be retrieved from the database and reinstantiated into the in-memory database. (RHI-5752)

  • Fixed a NullPointerException that could manifest in the Cassandra key/value store during pending transaction scanning under certain load conditions. (RHI-5746)


Rhino 2.6.2 introduces the following major new features:

  • SLEE timers can now be armed redundantly when using key-value store replication and external session ownership. Redundantly armed timers will be armed on one other cluster node and timer events will be directed to the node owning the SBB entity tree at the time of firing. (RHI-5479)

  • SBBs now have access to a Convergence Name Session Ownership Record, a special type of session ownership record tied to the convergence name of an SBB entity tree. Access to this record is available using the RhinoSbbContext API for SBBs and SbbPartContext API for SBB parts. (RHI-5517)

  • The resource adaptor entity Session Ownership Facility has new methods that allow a node to attempt the atomic adoption of Convergence Name Session Ownership Records. (RHI-5541)

  • Added a new resource adaptor extension property (defined in RhinoExtensionProperties) that indicates if the new session ownership record adoption support added in Rhino 2.6.2 is available and enabled in the namespace the resource adaptor is running in. A resource adaptor can use this property to determine if session ownership behaviour requiring this functionality should be enabled or disabled at runtime. (RHI-5673)

  • Added a new SBB/SBB Part API to permanently disable key/value store persistence of application-related state (as opposed to disabling initial persistence which was only ever intended to be a temporary postponement of state persistence). (RHI-5727)

  • Added a new built-in ServiceNodeActivity and ServiceNodeStartedEvent, similar to the SLEE-defined ServiceActivity and ServiceStartedEvent, but with the following differences:

    • A ServiceNodeActivity is not replicated.

    • A separate ServiceNodeActivity is started for a service on each node where that service starts. A ServiceNodeStartEvent is fired on each ServiceNodeActivity when the activity starts.

    • A ServiceNodeActivity ends (with a normal ActivityEndEvent) when the associated service on the node transitions to the stopping state.

Behaviour changes

  • The housekeeping operations that were previously available to find all non-resident activities and SBB entities from a key/value store have been deprecated and no longer perform that function. This is due to the fact that Cassandra copes poorly with such requests when the key/value store is being used in a production capacity.


  • Added MBean methods, console commands, and an Ant task to configure a service’s initial persistence status. (RHI-5296)

  • Improved the resiliency of the key/value store transaction scanning thread to scan failures. (RHI-5385)

  • The options for showing removed objects in the rhino-console findactivities and findsbbs commands have changed. In addition the option for showing non-resident objects with these commands has been deprecated and no longer performs any function. (RHI-5403)

  • Added a remove(key) operation to the resource adaptor entity Replicated Storage Facility that allows a table entry to be removed from storage without having to read that entry first. (RHI-5453)

  • Added a new maxPersistDeferredTransactionAge configuration option to the key/value store that specifies the maximum age that persist-deferred transactions will be retained for before persistence is forced upon them. (RHI-5455)

  • The Cassandra key/value store now has a configurable maximum cap on the amount of data that it will hold on to pending persistence to the backing database, with a default limit of 125% of served memdb instances capacity. (RHI-5469)

  • Added database read/write response times to key/value and session ownership store statistics. (RHI-5485)

  • The default Rhino transaction timeout used for most management operations has been increased from 2 minutes to 3 minutes. (RHI-5532)

  • The default read and write timeouts for the Cassandra key/value store and session ownership store have been increased to 2000ms. (RHI-5578)

  • Improved distributed lock use when managing object pool configurations during node start. (RHI-5588)

  • Improved how stats parameter sets and parameter set types are configured and registered with the internal SNMP stats manager so that these operations no longer use excessive system resources or continue for a prolonged period of time after node boot when a large number of parameter sets and types exist. (RHI-5590)

  • The distributed locks held while a service is activating have been revised to reduce the likelihood of lock timeouts occurring in other threads and/or other nodes when a service that takes a long time to activate is asked to do so by a management client. (RHI-5611)

  • The SNMP config update thread now sets an explicit transaction timeout based on the lock acquisition timeout period and number of possible retries it may do, to avoid transaction timeout when this time period exceeds the default transaction timeout period. The maximum number of retries is now also configurable by a system property. (RHI-5619)

  • Reduced the time taken to dynamically allocate SNMP counter mappings, such that very large statistics parameter sets that need counter mappings allocated will be now be registered significantly faster. (RHI-5621)

  • Added a -contains <xyz> filtering option to the rhino-console listlogkeys command. (RHI-5632)

  • SBB entity trees retrieved from a key/value store on failover will now be validated for completeness before event delivery. SBB entity trees that fail validation will not be delivered the event but rather be detached from all activities and removed from the database. (RHI-5644)

  • The size of the executor thread pool used by the session ownership store is now configurable in rhino-config.xml. (RHI-5664)

  • Increased default session ownership thread pool size from 5 to 30 to improve performance of synchronous operations (RHI-5740).

  • Added a -H option to rhino-stats that displays the hostname in the statistics, allowing stats to be tracked to their origin host. (RHI-5695)

  • Alarms are now raised by the Cassandra key/value and session ownership stores if a host in a Cassandra cluster the store is connected to unexpectedly leaves the cluster. (RHI-5737)

Bug fixes

  • Updated SNMP MIB counter descriptors to be unique by prefixing the parameter set name. (RHI-4819)

  • The NodeHousekeepingMBean getSbbInfo operation will now no longer internally wrap an UnrecognizedSbbEntityException in a ManagementException. The UnrecognizedSbbEntityException will now be thrown unwrapped as intended. (RHI-5364)

  • Fixed a lock timeout issue that could cause a node to fail to restart if a large number of key/value store-enabled namespaces were configured in the cluster. (RHI-5422)

  • Fixed NullPointerException when checking if a failed key/value store update session should be rechecked. (RHI-5444)

  • When a key/value store-replicated service is deactivated on all nodes where it is running, any nodes that fail during the draining period will have their outstanding SBB entity trees adopted by one of the remaining nodes before the drain completes. (RHI-5462)

  • Fixed a bug in the SAS configuration Ant task <configuresas> that caused it to remove the configured SAS servers if no updated SAS servers were specified. (RHI-5477)

  • The getSbbInfo and getSbbDiagnostics housekeeping commands will, when invoked against a non-resident SBB entity, no longer cause that SBB entity to become resident on the node running the management operation. In addition, the activity handles of non-resident attached activities will now be rendered correctly in the TabularData returned from these methods. (RHI-5488)

  • Fixed uncaught exception alarm caused by a permission check failure during log rollover. (RHI-5492)

  • The getSbbInfo, getSbbDiagnostics, getAttachedActivities, and removeSbb housekeeping operations all now have a new variant that includes a nonResident parameter, which must be set to true for the operation to interact with non-resident key/value store replicated SBB entities. This fixes issues where these operations were operating on state implicitly retrieved locally by the key/value store in the management node rather than the current in-memory state of the SBB entities owning node. (RHI-5495)

  • The Cassandra key/value store will now initialise and start properly if configured in rhino-config.xml with no configuration properties specified, ie. all default values will be assumed. (RHI-5500)

  • Fixed a race condition that could lead to a NullPointerException when attempting to flush key/value store state, eg. during resource adaptor entity deactivation or SLEE stopping. (RHI-5503)

  • Fixed a bug where SBB Parts were not releasing their component references to dependent event types when unverified. (RHI-5520)

  • Creating or deleting a session ownership record containing no additional keys now completes successfully rather than failing with a NoSuchElementException. (RHI-5521)

  • Fixed an IllegalArgumentException that occurred when trying to deploy a service containing an SBB that defined usage parameter interfaces using only the extension deployment descriptor and didn’t define any of the interfaces as the root usage parameter set type. (RHI-5525)

  • Fixed an issue with the resource adaptor entity Cluster State Change Facility where the facility on a given node would not report updates from new nodes added to the cluster in some circumstances. (RHI-5533)

  • Fixed a NullPointerException when attempting to set SBB tracer levels in a service with an install level of INSTALLED. The operation now fails with a more appropriate error. (RHI-5542)

  • Fixed the NodeHousekeepingMBean.getTimerInfo(timerID) operation so that it works correctly for timers set on key/value store replicated activities. (RHI-5545)

  • Cancelling a timer on a key/value store-replicated activity forcefully using a housekeeping operation will no longer leave a dangling transaction on the nodes where the timer is not present. (RHI-5547)

  • Fixed a NullPointerException that occurred during event processing if a replicated activity restored from a key/value store contained attached SBBs from services that were no longer deployed. (RHI-5570)

  • Fixed a concurrency issue that could lead to a NullPointerException in the statistics manager if parameters were subscribed or unsubscribed from a stats session that was already collecting data. (RHI-5572)

  • Fixed a NullPointerException when creating a SessionOwnershipRecord when a map that does not support null values (eg. java.util.TreeMap) was passed as an argument to the builder’s setAttributes method. (RHI-5581)

  • Fixed potential distributed lock timeouts in the deployed component file manager when large clusters are deploying complex applications. (RHI-5592)

  • Fixed possible distributed lock timeouts reading and/or updating per-node activation state during a concurrent restart of many cluster nodes. (RHI-5595)

  • Fixed non-replicated activity GC that could report a confusing IllegalStateException if it was triggered early enough during node boot. (RHI-5600)

  • Fixed a distributed lock manager race condition that could grant an exclusive lock to a waiting thread in error if an acquisition attempt on a highly contended lock timed out but was immediately retried, for example as happens in the SNMP configuration update thread during large parameter set configuration storms. This error could furthermore result in the lock becoming permanently jammed if the erroneously acquired lock was released before the lock was officially granted by the lock manager. (RHI-5614)

  • Cassandra database tables used in the key/value and session ownership stores will now garbage-collect tombstones after a one-hour grace period rather than the general database default of ten days. This period can be configured with the new tombstoneGCGracePeriod configuration property for the key/value and session ownership stores in rhino-config.xml. (RHI-5629)

  • Fixed an issue with the key/value store pending transaction scanner that caused it to miss some related transactions in certain circumstances, leading to those related transaction potentially being persisted out of order. (RHI-5631)

  • Fixed failover of the replicated SLEE-generated service activities so now they will only get adopted by nodes where the corresponding service is running. If a service is not running on any remaining nodes then the activity for that service is removed. This also fixes an AssertionError that would occur, for example, on node recovery when the restarting node considered itself to be the first node where a service was starting again and tried to recreate the service activity, but failed to do so because the activity already existed on another node where it shouldn’t. (RHI-5636)

  • Fixed an issue preventing removal of key/value store-replicated SBB entity trees that were broken after failover by incomplete or inconsistent state being available in the key/value store. (RHI-5643)

  • If a service was deactivated on the node owning the associated SLEE-generated service activity, and the service was still running on other cluster nodes, ownership of the service activity was not being reassigned to one of these other nodes, rather the activity remained owned by the deactivating node. This could cause future problems such as AssertionErrors, for example, if the other nodes were restarted. This issue is now fixed. (RHI-5658)

  • Profile specifications with large numbers of profile attributes will now deploy correctly. Previously a SLEE 1.0 profile specification with more than 255 profile attributes, or a SLEE 1.1 profile specification with more than 253 profile attributes, would unexpectedly fail at the code generation stage. (RHI-5659)

  • Fixed a security permissions issue that caused nodes to fail to restart when using JDK 1.7 if a profile table using the non-default pessimistic locking existed. (RHI-5676)

  • Fixed a problem with a service returning to the Inactive state when the service is deactivated on a node and the ServiceActivity, with replicated SBBs attached to it, needs to be reassigned to another node where the service is still running. (RHI-5682)

  • The configuration manager will now only initialise empty configuration types on boot of the first node in a virgin cluster (for global config types) or on namespace creation (for namespaced config types). This eliminates a class of bug that would, for example, cause a node booting into an existing cluster where all licenses had been manually uninstalled to reinstall the default platform license, but not tell other nodes about it, leading to inconsistent configuration state on the other nodes. (RHI-5689)

  • Fixed the inability to use some housekeeping operations against SBBs that perform JNDI lookups for resource adaptor entity bindings in setSbbContext() when the service they are contained in is inactive on the node performing the operation. (RHI-5691)

  • The Cassandra key/value and session ownership stores will now refrain from terminating database sessions on potentially transient connection issues such as query timeouts or single host failures. (RHI-5698)

  • The rhino-console listserviceralinks command will now also report resource adaptor entity links for SBB Part components in the service. In addition the command will also traverse link and shadow components to find all resource adaptor entity links for the service. (RHI-5699)

  • Fixed the rhino-console command completer for the third argument of the shadowcomponent command. (RHI-5701)

  • Fixed a memory leak that occurred in Rhino if a stats client started collection for a statistics session that had no stat parameter subscriptions. Also fixed a reconnection issue in rhino-stats where it failed to restart stats collection after certain connection failover scenarios, meaning the client didn’t output stats any more after the failover. (RHI-5717)

  • Fixed a NegativeArraySizeException error in rhino-stats when fetching statistics for which a subscription does not exist. (RHI-5731)

  • Fixed a sorting comparator bug in the rhino-console listactivealarms command that could lead to an IllegalArgumentException in particular dataset cases. (RHI-5732)


Behaviour changes

  • Added a new per-node configuration file to override two Java security properties. This file specifies the following default values:


    These values control the cache time-to-live of results for all DNS address resolution in the Java virtual machine. The default behaviour in Oracle Java is to cache the results indefinitely, so this change will result in more DNS queries, but it avoids the need to restart Rhino nodes when a downstream server changes IP address.

    To revert to the previous behaviour, see Java Security Properties in the administration guide. (RHI-5457)

  • Added new alarmType parameter ( to SNMP Alarm Notifications. This OID contains the Alarm Type listed in the alarm catelog. (RHI-5516)

Bug fixes

  • Fixed rare BufferOverflowException triggered by concurrent SNMP counter access. (RHI-5493)

  • Fixed a bug where SBB parts were not releasing their component references to dependent event types when unverified. (RHI-5520)

  • Creating or deleting a session ownership record containing no additional keys now completes successfully rather than failing with a NoSuchElementException. (RHI-5521)

  • Fixed an IllegalArgumentException that occurred when trying to deploy a service containing an SBB that defined usage parameter interfaces using only the extension deployment descriptor and didn’t define any of the interfaces as the root usage parameter set type. (RHI-5525)

  • Fixed an issue with the resource adaptor entity cluster state change facility where the facility on a given node would not report updates from new nodes added to the cluster in some circumstances. (RHI-5533)

  • Fixed a NullPointerException when attempting to set SBB tracer levels in a service with an install level of INSTALLED. The operation now fails with a more appropriate error. (RHI-5542)

  • Fixed the NodeHousekeepingMBean.getTimerInfo(timerID) operation so that it works correctly for timers set on key/value store replicated activities. (RHI-5545)

  • Cancelling a timer on a key/value store-replicated activity forcefully using a housekeeping operation will no longer leave a dangling transaction on the nodes where the timer is not present. (RHI-5547)

  • Fixed a NullPointerException that occurred during event processing if a replicated activity restored from a key/value store contained attached SBBs from services that were no longer deployed. (RHI-5570)

  • Fix a NullPointerException when creating a SessionOwnershipRecord when a map that does not support null values (eg. java.util.TreeMap) was passed as an argument to the builder’s setAttributes method. (RHI-5581)

  • Fix a distributed lock manager race condition that could grant an exclusive lock to a waiting thread in error if an acquisition attempt on a highly contended lock timed out but was immediately retried, for example as happens in the SNMP configuration update thread during large parameter set configuration storms. This error could furthermore result in the lock becoming permanently jammed if the erroneously acquired lock was released before the lock was officially granted by the lock manager. (RHI-5614)

New Features

  • Added a remove(key) operation to the Replicated Storage Facility available to resource adaptors that allows a table entry to be removed from storage without having to read that entry first. (RHI-5453)

  • Add Rhino support for additional SAS event fields message_id and call_info_id. (RHI-5523)

  • Added a new built-in ServiceNodeActivity and ServiceNodeStartedEvent, similar to the SLEE-defined ServiceActivity and ServiceStartedEvent, but with the following differences:

    • ServiceNodeActivities are not replicated.

    • A separate ServiceNodeActivity is started for a service on each node where that service starts. A ServiceNodeStartEvent is fired on each ServiceNodeActivity when the activity starts.

    • A ServiceNodeActivity ends (with a normal ActivityEndEvent) when the associated service on the node transitions to the stopping state.


Bug fixes

  • Fixed NullPointerException when checking if a failed KV store update session should be rechecked. (RHI-5444)

  • Fixed permission issue that could result in lost log messages during a log rollover. (RHI-5456)

  • Fixed an IllegalAccessError exception that occurred when a failed timer event was refired. (RHI-5473)

  • Fixed abnormal execution alarm raised regarding log4j2 rolling file manager access permission. (RHI-5492)

  • Fixed a bug in the SAS configuration Ant task <configuresas> that caused it to remove the configured SAS servers if no updated SAS servers are specified. (RHI-5477)


New Features

Rhino 2.6.1 introduces the following major new features:

  • New session ownership subsystem backed by Cassandra. See Replication Support Services for more information. (RHI-5018)

    • SLEE services and resource adaptors on a given node can claim ownership of an individual SLEE activity or a complete identifiable session.

    • Services can access the session ownership store through a new built-in resource adaptor type definition.

    • Resource adaptors are provided with a new extension facility for access to the session ownership store.

  • New "key/value store" replication mode for in-memory database state backed by Cassandra. See Replication Support Services for more information. (RHI-5012)

    • Various housekeeping management operations have been extended to support interrogation of "non-resident" activities and SBB entities. A "non-resident" object is one whose state is currently stored only in a key/value store’s external database and not in the in-memory database of any active cluster node.

Other new features and items of note:

  • The DataStax Java Driver for the Cassandra database is now bundled with Rhino and support for Cassandra persistence instances has been added. (RHI-5007)

  • A new service extension deployment descriptor option has been added that allows a service to delay persistence of its initial transactional state changes to a key/value store’s external database until such time as the service elects to enable persistence. (RHI-5120)

    • A new DTD version of the oc-service.xml extension deployment descriptor has been added to support this. (RHI-5248)

  • New resource adaptor extension configuration properties have been added that provide a resource adaptor with knowledge about its replicated storage replication method and the availability of the session ownership subsystem. (RHI-5249)

  • A new DTD version of the oc-resource-adaptor-jar.xml extension deployment descriptor has been added that allows a resource adaptor to more extensively configure the options used during the creation of its replicated storage resources. (RHI-5266)

  • The replicated storage resource and availability of the session ownership subsystem have been added as configurable options when creating a user-defined namespace. The settings provided for a namespace are output to the Rhino log when the namespace is created or reinitialised on node restart. (RHI-5263)

  • The structure of rhino-config.xml has been updated slightly to support the new key/value store and session ownership configuration.

  • The Rhino production installer has been updated to include prompts for the initial configuration of the new optional key/value store and session ownership subsystems for Rhino’s default namespace. (RHI-5207)

Bug fixes

  • Fixed an NPE that occurred trying to reassign to another node a service activity that had previously been administratively removed when the SLEE on the node that had owned the activity transitioned from RUNNING to STOPPING. (RHI-5322)

  • The activity handler txEnd and nonTxEnd statistics are now correctly recorded. (RHI-5336)

  • Fixed an internal corruption of metadata that occurred if a component referenced by more than one linked component had one of those linked components removed. This could have led to, for example, service activation callbacks for the remaining linked components not being made to resource adaptors when required by a target service component. (RHI-5347)

  • Fixed a lock manager issue that affected a deactivate-and-activate service operation when more than one service was being deactivated, and improved the resiliency of stopping tasks in general in the wake of unexpected errors during their execution. (RHI-5362)

  • Fixed some numerical overflow errors in stats-related classes that could lead to a NegativeArraySizeException in rhino-stats in some circumstances. (RHI-5375)

  • Fixed an off-by-one error when determining if a late SBB timer should generate a timer event when the PRESERVE_LAST timer option was used. The error meant that a timer event was not generated in the case the last repetition of the timer (or the only repetition, in the case of a non-periodic timer) fired late. (RHI-5379)

  • SLEE 1.1 profile table creation will no longer fail with an NPE if debug logging for the "profile.profile" log key is enabled. (RHI-5424)

  • Fixed exception when activating rhino-extensions examples service (RHI-5436)

  • Improved error handling for adding and removing SAS servers. (RHI-5301)

  • Stats parameter set descriptions output by rhino-stats -l now include a "Short name" column and the content of the "Label" column has been corrected. (RHI-5394)

  • Removed heap limit from rhino-console and rhino-import client tools to prevent OutOfMemoryError during install. (RHI-5418)


  • Added a new @CMPFieldReplication annotation usable by SBBs and SBB Parts that allows the replication of individual CMP fields to be completely suppressed. (RHI-5245)

  • SBBs and SBB Parts can now tag CMP fields with one or more names using the @CMPFieldTag annotation then programmatically iterate over tagged CMP fields using new methods in the CMPFields extension interface. A CMPField interface has also been added as an alternative access mechanism to individual CMP fields to facilitate this new feature. (RHI-5081)

  • Previously, SBB CMP fields using the @PassByReference annotation with scope PERMANENT could not access the SBB object’s encodable context. They now can. (RHI-5406)

  • Added a deregisterProfileMBeans command to rhino-console that allows rogue profile MBeans such as those for uncommitted profiles to be cleaned up. (RHI-5383)

  • The Rhino cluster ID value is now available directly, as a java.lang.Integer value, to resource adaptors, by way of a new extension configuration property, and SBBs and SBB Parts, via the java:comp/env/rhino/cluster-id JNDI name. (RHI-5240)

  • Added a new Cluster State Change Facility resource adaptor listener interface that provides more information about the cluster’s current state with respect to the original listener interface. (RHI-5239)


New Features

Rhino 2.6.0 introduces the following major new features:

  • New logging subsystem based on Log4j 2. See the logging documentation.

    • Built-in Log4j 2 appenders and filters can be used.

    • Log pattern is now configurable.

    • The timestamp in log messages now includes the timezone.

    • Log messages now include diagnostic context in curly braces. This is accessible to components via the Logging Context Facility.

    • The Log4j 2 default rollover strategy is now being used — this results in rolled over log files having constant numbering (1-10) rather than incrementing forever.

    • Tracer levels are stored in the logging configuration rather than the management database, so the script does not clear these. Follow the instructions displayed when re-initialising the database if needed.

    • The async logging facility has been deprecated because Log4j 2 async appenders can be used instead.

    • Full Rhino startup information is logged to new log files after rollover, but they may not at the very beginning of the log when under load.

    • Log files do NOT roll over on startup for production Rhino, to prevent a restart loop from expiring useful logs.

  • SLEE Tracing now uses the logging subsystem directly.

    • There is an extended tracer interface with methods that correspond to most Log4j 2 Logger methods.

    • When using the extended tracer, arguments are not evaluated unless the message is written to an appender, so tracing method invocations with simple parameters do not need to be guarded.

    • Every tracer has a corresponding logger, you can configure those loggers as you would any other logger.

    • Logger names for tracers are fully-qualified and unique internally, but are abbreviated by the log pattern to eliminate redundant components.

  • Metaswitch Service Assurance Server (SAS) support. See the SAS tracing documentation.

Bug fixes

  • Profile MBeans now isolate transactional state between different management clients. Changes being made by one client no longer leak into the view of other clients. (RHI-4317)

  • The configurestagingqueues Ant task no longer transposes maximumAge and maximumSize values. (RHI-4380)

  • Object pool stats are now grouped by namespace, and their parameter set names have been improved. (RHI-4429)

  • The various ProfileProvisioningMBean getProfiles* methods now respect the state of any user transaction currently in progress by the client. (RHI-4458)

  • Added ResourceExecutor stats parameter set type to TransactionManager. These statistics were previously being combined with SynchronizationExecutor. (RHI-4533)

  • Reworked the export of custom security policies assigned to components so that these are now set during import as part of the corresponding deployable unit install rather than as a post-deployment target. This means that the polices are now set during import long before the components are put to any real use, which is required if, for example, a resource adaptor entity needs the custom policy in order to initialise correctly. (RHI-4537)

  • The object pool configuration for a profile table named "default" is now separate from the default profile table object pool configuration. (RHI-4584)

  • Fixed some erroneous transactional behaviour during namespace creation and removal that occurred if the bounding transaction happened to fail during commit. (RHI-4712)

  • Non-replicating activity handlers will now correctly inform their associated resource adaptor if an activity under their control is forcefully ended by a platform administrator. (Replicating activity handlers were already behaving correctly here.) (RHI-4743)

  • Locks held by Profile MBeans in the writeable state on nodes that leave the cluster will now be cleaned up by remaining nodes in the cluster, rather than leaking and leaving those profiles uneditable until cluster restart. (RHI-4815)

  • The cascade uninstaller tool will now correctly manage deactivation of services and resource adaptor entities with different activation states on different nodes, as well as correctly dealing with the symmetric activation state mode. (RHI-4836)

  • CMP reset methods now manage transactional state correctly. (RHI-4857)

  • Fixed a potential MemDB state object sizing issue if toString() was invoked on a persistent state object mid-transaction. (RHI-4858)

  • Tracer management commands operating on services that are undeployed will now fail with a more helpful error message. (RHI-4958)

  • Profile table access is no longer corrupted if multiple profile tables are created from the same profile specification. (RHI-4959)

  • Fixed behaviour of SBB CMP fields storing SBB local objects when using transactional pass-by-reference in the case where an SBB entity is removed after being stored in a CMP field. (RHI-5142)

  • Fixed a code generation issue that caused deployment of an SBB to fail if the SBB didn’t define an Activity Context Interface but the SBB abstract class defined a non-abstract asSbbActivityContextInterface method. (RHI-5258)

  • Fixed an NPE that occurred trying to reassign to another node a service activity that had previously been administratively removed when the SLEE on the node that had owned the activity transitioned from RUNNING to STOPPING. (RHI-5322)

  • Changed default for rhino.skip_lifecycle_checks to false. This is discussed further in the Resource adaptor entity lifecycle states documentation. (RHI-4382)


  • System property "rhino.tracer.defaultlevel" has been removed. Trace levels can be set via the logging subsystem. (RHI-4947)

  • Trace notifications are now rate limited to a rate of 10/second with a burst limit of 1000, using the Log4j 2 BurstFilter. (RHI-4937)

  • The tamper-detection mechanism for audit logs now uses a checksum approach. (RHI-4627)

  • FreeMemory watchdog condition now triggers when 95% of heap is used. This is configurable via the watchdog.oom_percent_used system property. The old system property, watchdog.oom_min_free is deprecated. (RHI-5255)

  • Rhino Stats default memory size has been increased to fix problems with GUI mode. (RHI-5184)

  • An originating node ID field has been added to each of the respective vendor data extension classes included by Rhino in trace, alarm, and state change JMX notifications. (RHI-1962)

  • Stats parameter sets related to object pools for profile tables are now named after the profile table they relate to for easy identification, rather than an internal application identifier. (RHI-2963)

  • Add log messages to report transaction manager synchronization and resource executors queue size configuration. (RHI-4502)

  • Stats parameter set types, and consequently SNMP parameter set type OID mappings, no longer include namespace qualifiers embedded into their name. Namespace qualification is now handled externally from the name. (RHI-4783)

  • An export can now be imported into a different namespace using the import.namespace Ant property. (RHI-4381)

  • The cluster state change facility will now only notify resource adaptor entities in the affected namespace, rather than all resource adaptor entities, when the SLEE running state in that namespace changes. (RHI-5021)

  • Rhino’s config manager now handles namespace-specific configuration items (ie. object pools configs, SNMP parameter set type configs for applications, and limiter endpoint configs) on a per-namespace basis. Configuration items scoped to namespaces are now managed using namespace-specific container configuration MBeans. (RHI-4711)

  • Names of Rhino internal classes now reflect their original source location. (RHI-4167)

  • Garbage collection defaults have changed:

    • Garbage collection debug logging is now written to a file, with rollover settings of 100MB files, 5 archived files

    • Enabled tiered compilation on Java 7 (production Rhino only)

    • Enabled parallel weak reference handling (production Rhino only)

    • Automatically perform a JVM heap dump on an OutOfMemoryError (production Rhino only)

    • Removed unused Incremental CMS options (RHI-4548)

  • The config.log log file has been removed and messages that were previously in this file are now in rhino.log. (RHI-4625)

  • The namespace names 'default' and 'global' (case insensitive) are now reserved for internal use. It is no longer possible to create user-defined namespaces with these names. (RHI-4909)


Bug fixes

  • Fixed bug in activity attachment mapping that caused various failures including event delivery spinning on activity-end cleanup. (RHI-5097)

  • CMP fields of type java.math.BigInteger or java.math.BigDecimal will no longer cause a deployment failure during code generation. (RHI-4516)

  • Fixed an issue in export scripts which created resource adaptor entities before the relevant security permissions had been set. (RHI-4500)

  • Corrected header attached to CSV alarm log, and fixed timestamp field formatting when an alarm originates from a user-defined namespace. (RHI-4631)

  • Fixed the exporter when multiple namespace names are sanitised to the same value. The exporter will now generate unique filenames in the exported data when sanitised names clash, rather than simply overwriting previously written data. (RHI-4705)

  • Fixed some erroneous transactional behaviour during namespace creation and removal that occurred if the bounding transaction happened to fail during commit. (RHI-4712)

  • The internal distributed management lock is now correctly released if an attempt is made to remove a configuration item of an unknown type. (RHI-4795)

  • Fixed an activity end race condition in the activity handler that could lead to the pessimistic or replicated lock for an activity not being released when the enclosing transaction ends. (RHI-4983)

  • Profile, Usage, and Usage Notification Manager MBeans related to a profile table will now be correctly deregistered from the MBean server when a profile table is renamed. (RHI-4975)


  • The rhino-console installlocaldu command now supports an optional -url argument to specify an alternate URL identifier for the deployable unit. (RHI-4939)

  • Rhino client tools now allow the GC_OPTIONS environment variable to be overridden. (RHI-5101)

  • The <setactivenamespace> Ant task now also updates the rhino.namespace system property so that any new connection object instances inherit the same namespace context. (RHI-4764)

  • The system property "file.encoding" is now globally readable by default. This is needed by some JDBC drivers. (RHI-4907)


Bug fixes

  • Fixed a NullPointerException thrown by the createpersistenceinstance and updatepersistenceinstance Ant management tasks. (RHI-4482)


New Features

  • The namespaces feature is now supported for production use.

Bug fixes

  • Fixed double-event scheduling from multiple suspend-resume cycles and interleaved transactions suspending, resuming and firing events. (RHI-3207)

  • Fixed a problem that could cause corruption of internal state when a node failed during deployment. (RHI-4327)

  • Fixed a NullPointerException that occurred when accessing service state in symmetric activation state mode. (RHI-4377)

  • Fixed a race condition that could report a profile as still being edited by some other management client if a client tried to edit a profile immediately after committing or rolling back changes to that same profile. (RHI-4442)

  • Fixed a NullPointerException that occurred when deploying linked components. (RHI-4395)

  • Fix after-transaction logic to always clean up activity event queues. Prevents stuck activities from transactions containing resources that fail between commit and cleanup. (RHI-4326)

  • Services and resource adaptor entities that are in the STOPPING state when a node is started will now correctly revert to the INACTIVE state during bootup when the symmetric activation state mode is not enabled. (RHI-4421)

  • Fixed a race condition between the creation of a profile in a user transaction and a concurrent long-running timeout and rollback of that transaction. This race condition meant that some metadata state for the failed profile creation was not cleaned up, preventing any further profile creation attempts for that profile to succeed. (RHI-4424)

  • Fixed compilation issues when deploying SBBs with a very large number of CMP fields. (RHI-4392)

  • Fix malformed ObjectName generation that prevented interaction with object pool configurations for components in user-defined namespaces. The "use-defaults" property of object pool configurations has been removed because it did not function in an obvious manner. (RHI-4391)

  • The namespace that each management operation was performed on is now included in the management.csv audit log file, present as the 7th field in the CSV. Rhino will use the old audit log file format if the "rhino.audit.log_format" system property is set to "2.4" (but this should not be set if namespaces are being used because it will not be possible to tell which namespace an operation was run in). (RHI-4352)

  • ServiceUsageMBean, ProfileTableUsageMBean and ResourceUsageMBean are now included in the management audit log. (RHI-4427)

  • The snapshot tool can now be used from a remote host. (RHI-4406)

  • Fixed Java GC options in the Windows Rhino SDK scripts. (RHI-4409)


  • Improved the mechanism used to detect and protect against concurrent profile edits occurring over the profile management interface. This change should prevent unexpected lock timeouts if the compare-and-set locking operation takes longer than one second, eg. slow hardware. (RHI-4239)

  • Added ability to optionally exclude individual configuration types when importing a Rhino export. This is particularly useful for cases where the target Rhino instance does not have a JDBC driver for the persistence configuration being imported. (RHI-4386)


Bug fixes

  • Fixed an UnrecognizedLinkNameException when listing resource adaptor link names. (RHI-4211)

  • Fixed a NullPointerException when a management client tried to get the current trace level for a tracer. (RHI-4278)

  • Fixed event router warnings when stage items were rejected for execution, typically because of overload. (RHI-4241)

  • Fixed a bug that prevented the per-node SNMP agent from being deactivated. (RHI-4318)

  • Fixed a bug that prevented an SNMP OID mapping from being registered if it was cleared when Rhino started. (RHI-4308)

  • In the case where a resource adaptor entity or profile table is created from a linked or shadowed component, only the install level of the resolved target component is now relevant when deciding whether or not to allow the operation to proceed. The install level of the virtual component itself is irrelevant. (RHI-4243)

  • Fixed a potential concurrency race condition that could lead to the SLEE getting stuck in the STOPPING state if a service was deactivated on some nodes when the symmetric activation state mode was enabled. (RHI-4254)

  • Fixed a number of issues affecting the cascade uninstaller when dealing with linked, shadowed, and copied components. (RHI-4207)

  • Fixed some issues with the cascade uninstaller failing to correctly determine the necessary uninstallation order in some complex scenarios, particularly involving copied components. (RHI-4213)

  • Removed a spurious message regarding the removal of copied components when running the cascade uninstaller in assumed-yes mode. (RHI-4215)

  • The cascade uninstaller will now successfully clean up copied or linked components that have active resource adaptor entities or profile tables created from them. (RHI-4240)

  • Fixed a bug that prevented passwords being updated with the rhino-user utility. (RHI-4201)

  • Fixed a possible change to the active namespace after using the exportall command in rhino-console. (RHI-4252)

  • Some issues affecting the scoping and cleanup of statistics parameter sets used by namespaces have been fixed. (RHI-4212)

  • SLEE, service, and resource adaptor entity state change notifications now include vendor-specific data that identifies which namespace the notification originated from. (RHI-4193)

  • Trace and usage notifications now include vendor-specific data that identifies which namespace the notification originated from. (RHI-4264)

  • SLEE 1.0-style alarm notifications now include vendor-specific data that specifies the namespace that the notification originated from. (RHI-4265)


  • Improved thread safety of RhinoConnection for use by multi-threaded clients. (RHI-4289)

  • Improved external database connection logging. (RHI-4186)

  • The Rhino SDK now has the "CMSClassUnloadingEnabled" JVM option enabled by default, to prevent out-of-memory errors under certain conditions. (It is already enabled by default for a production Rhino installation.) (RHI-3490)

  • Reduce repetitious log messages about deployable unit verification when importing. (RHI-4210)

  • Set default heap size for Rhino client tools to 64MB. (RHI-3176)


New Features

Rhino 2.5.0 introduces the following major new features:

  • Scattercast cluster communications mode is now a supported configuration in production environments. Scattercast management must now be done using management commands, not by editing configuration files. See the Rhino Administration and Deployment Guide for details. (RHI-3551)

  • The database configuration for external persistence of Rhino’s in-memory database state, along with JDBC resource configuration for applications, can now be dynamically updated at runtime rather than requiring a node or cluster restart. (RHI-3785)

  • Full JVM statistics are now available under the JVM parameter set. (RHI-3890)

  • Cluster-symmetric activation state is now supported as an option for services and resource adaptor entities. When this option is enabled, an activation state change that affects a service or resource adaptor entity will be reflected on all nodes in the cluster, and if a new node enters the cluster it will inherit the cluster-wide activation state for each of these components. (RHI-3934)

The following is an early preview feature and is not supported in production environments:

  • Rhino now supports multiple deployment namespaces. Namespaces are created by an administrator, and each namespace is isolated from all others. Each namespace contains its own deployable units and components, resource adaptor entities, profile tables, SLEE and component activation states, etc. Namespace management is available in the Rhino command line console but not yet in Rhino Element Manager. (RHI-3926)

Installation Changes

  • Update minimum supported version of Java 8 to 1.8.0_60. Earlier versions contain bugs that affect Rhino operation. (RHI-3745)

  • Rhino SDK requires Java 8 to run the embedded Rhino Element Manager. (RHI-4178)


  • Alarms have been added for the following conditions:

    • if a forward or reverse timewarp is detected, in addition to logging an error message as has always been the case (RHI-3101)

    • if the filesystem does not support sufficiently long file names. (RHI-3965)

    • if a threshold rule trigger or reset condition fails to evaluate, for example because it refers to a unknown parameter set or statistic. The alarm will be cleared if the rule is deleted or replaced, or a missing parameter set is restored. (RHI-410)

    • if watchdog.no_exit is set. This is a dangerous mode to run in and should never be used in a live environment. (RHI-3798)

  • The Rhino command-line client now reports alarms when they occur and includes the SLEE state and alarm count in the prompt. This new behaviour can be disabled by setting the system property "rhino.console.disable-listeners" to true. (RHI-2101)

  • The deactivate-and-activate-services operation is now a lot more atomic. Dropped call issues that previously could have occurred if a service took a long time to activate should no longer occur. (RHI-3783)

  • Added a component classloader auditing function that will look for potential classloader problems amongst the component’s dependencies. (RHI-4050)

  • Added command to reboot Rhino nodes to their current state. (RHI-3873)

  • SNMP index names are no longer truncated. The old behaviour can be restored by uncommenting the "" line in read-config-variables. (RHI-3796)

  • Add new Threshold Rule management API call to retrieve all configured rules at once. (RHI-4049)

  • Reduced severity of log message for cleanup of leaked OCIO buffers. This does not affect the reliability of the node. (RHI-3200)

  • New sample Systemd service descriptor for RHEL 7 and related systems. (RHI-3715)

Bug fixes

  • Fixed the potential for the SLEE, a service, or a resource adaptor entity to get stuck in the STOPPING state if a lock timeout happened to occur during the deactivation operation. (RHI-3453)

  • Services and resource adaptor entities will no longer get stuck in the STOPPING state if a temporary database error occurs when trying to reset their state back to INACTIVE. (RHI-3650)

  • Fix GroupHeartBeat failure on boot into a network containing a one way partition (RHI-3663)

  • The SLEE will no longer get stuck in the STOPPING state if a start operation is attempted while STOPPING. (RHI-3792)

  • UsageMBeans no longer return partial results if a node responds with an error. The error is now passed back to the client as a ManagementException as per the API (RHI-3850)

  • Added support for SBB Parts to the getsecuritypolicy and setsecuritypolicy Rhino Console commands. (RHI-3908)

  • Cluster will more gracefully handle one way network partitions. (RHI-3924)

  • Fixed snapshot decode of exported profile tables containing CMP fields that define serialisability only by way of a DatatypeCodec. (RHI-3986)

  • Fixed stall in savanna groups when rapidly shutting down many nodes in sequence (RHI-3989)

  • SBB part security permissions are now correctly applied to generated service code. (RHI-3994)

  • Fix NPE on node start when -d option is used alone with (RHI-4000)

  • The object pool for a profile table defined by a SLEE 1.1 profile specification will now correctly initialise on profile table creation if the initial pooled size is greater than zero. (RHI-4001)

  • Fix a NullPointerException if linked/shadowed services are deployed when setting a security policy. (RHI-4021)

  • The ResourceAdaptor.serviceActive() callback will now be made after an activating service has also been started, if the SLEE is in the RUNNING state, rather than before. This removes a race condition that previously existed if the resource adaptor fired an event intended for the activating service in the callback method - depending on timing the event may or may not have been delivered to the service. (RHI-4029)

  • Database flush now properly flushes on all nodes. Database flush now respects timeout. (RHI-4030)

  • Fixed an NPE that occurred when running rhino-export if a component with an install level of INSTALLED depended on another component that was not yet installed. (RHI-4190)

  • The Rhino SDK start-rhino scripts now support command-line options to force the SLEE into the Running or Stopped state after the Rhino SDK has completed initialisation. (RHI-3189)

  • When running the Rhino SDK on Windows, fixed the generation of *.class.$$ files that polluted the RhinoSDK directory whenever a deployable unit was installed. (RHI-4187)