Rhino Changelog

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 NullPointerException that occurred during node startup if a Rhino installation containing existing management database state was moved to a different filesystem directory. (RHI-5774)

Fixed a potential NullPointerException when handling SQLExceptions in the persistent database storage subsystem. (RHI-5548)

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)

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)

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 sorting comparator bug in the rhino-console listactivealarms command that could lead to an IllegalArgumentException in particular dataset cases. (RHI-5732)

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

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

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

Fixed NPE 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)

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

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 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)

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

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)

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

The namespaces feature is now supported for production use.

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)

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)

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)

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)

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:

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 "snmp.name.max-length=19" 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)

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 start-rhino.sh. (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)

Fixed a NameNotFoundException that could occur when updating the environment entries of an SBB when a service that this SBB participated in was not active. (RHI-3012)

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

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

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

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

Fixed a NullPointerException on node start when -d option is used alone with start-rhino.sh. (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)

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

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 new Threshold Rule management API call to retrieve all configured rules at once. (RHI-4049)

Fixed a problem that caused the values for some statistics parameter sets to be returned in the wrong order when queried using SNMP. (RHI-3879)

Fixed an issue where the encodable context object retrieved during an SBB CMP field encode or decode could come from a different SBB object than the one the SBB entity in the current thread is associated with.

A side effect of this fix is that an encodable context is no longer available
to replicated CMP fields that use permanent pass-by-reference.  The requirement
for such cases is, however, expected to be extremely rare. (RHI-3860)

Fixed a problem with the exporter that caused it to generate an export that could not be imported into any other Rhino instance because it contained commands that tried to to deploy and verify the SLEE standard types. (RHI-3840)

This issue will affect exports from Rhino 2.4.0.16.  The exports can be
fixed by editing the "build.xml" script and removing the lines to deploy
and verify the javax-slee-standard-types.jar deployable unit.

This can either be done by hand or using the following "sed" command:

sed -i.bak '/lib\/javax-slee-standard-types.jar/d' ./build.xml

Fixed an issue where a conflicted OID alarm was not cleared when the OID was unregistered. (RHI-3825)

When a OID mapping is removed and then recreated it will now return to the active state if possible rather than being marked as inactive. (RHI-3835)

The state of cleared SNMP counter mappings is now displayed in Rhino Console and the cleared state of these counter mappings is now persisted and will remain cleared after Rhino is restarted. (RHI-3836)

If a deployed component registers a shutdown hook, and that hook does not return when Rhino tries to shutdown using System.exit(), Rhino will forcibly halt the VM using Runtime.halt() after a timeout. The timeout has a default value of 60000ms and can be overridden by setting the "rhino.halttimeout" system property. (RHI-3772)

All SNMP OIDs used by Rhino are now statically defined. (RHI-3779)

They are documented on this page:

https://developer.opencloud.com/devportal/display/RD2v4/3+Rhino+SNMP+OID+Mappings

SNMP OIDs for service metrics parameter sets now start at 500 and dynamically assigned OIDs for other stats parameter sets start at 700. (RHI-3824)

Enable tab completion of profile name arguments for removeprofile management command. (RHI-3766)

Add more detail to the descriptions in the SNMP notification MIB files. (RHI-3838)

An export of a profile table with a name containing illegal filename characters will no longer produce (or attempt to produce) an exported data file containing illegal characters. (RHI-3129)

Fixed XML Parsing error in META-INF/oc-service-license.xml due to illegal DTD attribute definition in oc-service-license-xml_1_1.dtd (RHI-3515)

Fixed negative item count deltas seen in StagingThreads statistics when a staging configuration change is made. Peak thread count is now bounded by the maximum thread pool size. (RHI-3622)

A copied component’s parent-child relationship with components copied from it will now be preserved if the former component is affected by a binding operation. (RHI-3711)

Fixed exporter issue with links, shadows, and component copies involving SLEE-defined component types. (RHI-3713)

The install level of linked and shadowed components will now be preserved by rhino-export. (RHI-3714)

Fixed corruption of active service resource adaptor entity link bindings when copying and deleting per-node activation state. (RHI-3721)

Fixed issue importing SNMP config exports that could subsequently lead to duplicate SNMP OID mappings being created. (RHI-3722)

SNMP OID mappings for usage parameter set types are now backwards compatible with versions of Rhino prior to 2.4.0. Rhino will now preserve existing OID mappings when importing a Rhino 2.3.1 export, rather than generating new mappings for usage parameter set types. Note that while Rhino can now cleanly import from Rhino 2.3.1 and earlier, exports created from previous 2.4.0.x releases need to be modified if OID compatibility needs to be retained: delete the ".default" extension from all the usage parameter set type mappings in the SNMP config export before importing it. (RHI-3741)

Fixed an issue which could disrupt message delivery after the 2,147,483,647th message on a Savanna group, leading to a group heartbeat failure and node restart. (RHI-3758)

Disable MemDB striping by default by setting stripe count to 1. (RHI-3761)

SNMP configuration updates that fail to be applied internally due to a lock acquisition timeout will now automatically be retried up to ten times before Rhino will give up on that update. (RHI-3764)

Fixed an ordering issue that could cause a node to associate resource adaptor entity bindings with the wrong SBBs during service activation. (RHI-3775)

Activating services were not being correctly initialised when the ServiceManagementMBean deactivateAndActivate operations were called - amongst other things the SBBs were missing their entity link JNDI bindings. This has now been fixed. (RHI-3784)

Added support for component linking and shadowing. A linked component is a virtual component that redirects any incoming reference to an alternative component. A shadow hides an already installed component, again redirecting any incoming references to an alternative component. (RHI-3527)

Fixed compilation error in generated service code when using sbb part event handlers. (RHI-3695)

The default usage parameter set no longer counts towards the maximum limit for a service, profile table, or resource adaptor entity, so will therefore always be available regardless of the number of named usage parameter sets created. (RHI-3699)

Fixed a timing issue in copying per-node activation state at node boot time that could lead to missing a state update if an activation state change occurred before the node was fully initialised. (RHI-3701)

The -c and -d options will now be disabled in start-rhino.sh for subsequent node restarts initiated by the -k option. (RHI-3703)

Fixed generation of javac command line parameters when deploying a service with SBBs that reference many SBB parts. (RHI-3704)

A Rhino node that is shut down in a controlled manner will now also wait for all outstanding SNMP configuration changes to be persisted before terminating. (RHI-3630)

The exporter now generates an import script that imports SNMP configuration information before installing deployable units, etc. This ensures that any new dynamically-mapped stats parameter set types created by Rhino will not conflict with any existing OID and counter mappings from the export. (RHI-3636)

Fixed management access to individual usage parameters via SLEE Usage MBeans. (RHI-3654)

Fixed a bug in the service bindings validator that failed to correctly identify the reuse of copied components that were in use by other services, thus leading to corruption in the dependency tree of these other services when an offending binding was applied. (RHI-3675)

A deployable unit jar file missing a manifest will now deploy correctly. (RHI-3643)

Added ability to specify a start and stop priority order for services and resource adaptor entities, used when the SLEE transitions from STOPPED to RUNNING or RUNNING to STOPPING. (RHI-3307)

SNMP parameter set type configuration data has been split up from a single monolithic configuration item to one configuration item per parameter set type. This significantly reduces the CPU usage of the SNMP statistics manager on node restart when a large number of parameter set type configurations are installed. SNMP configuration exports from previous Rhino versions are still installable in the current version but will be refactored into the new format during the configuration install process. (RHI-3567)

Some SNMP-related rhino-console commands have changed:

Added a new system property for transaction timeout of service activation operations. (RHI-3582)

Fixed a ConcurrencyFailure where startActivitySuspended and SBB attaching does not acquire isolation lock. (RHI-3579)

Fixed a memdb state cleanup issue that could prevent other nodes joining the cluster from being able to obtain a copy of replicated memdb state. The issue manifested as a "java.lang.IllegalStateException: stream already closed" error logged by the existing cluster node serving the replicated state. (RHI-3584)

Fixed NPE that could occur during the installation of a deployable unit if a deployment descriptor in a component jar could not be successfully parsed. (RHI-3598)

When used in the same SBB, two SBB parts that declare the same usage parameters interface type extending the same parent type will now successfully pass deployment verification rather than be rejected with a false error indicating that they have been declared with different extends types. (RHI-3615)

If an SBB and its SBB parts together declare more than one event handler method for the same event type, this error will now be reported at SBB verification time, rather than generating invalid code that cannot be compiled at SBB deployment time. (RHI-3616)

Fixed double counting of events fired by an SBB as accepted in event statistics. (RHI-3620)

Fixed an ArrayIndexOutOfBoundsException that could sometimes occur when a stats client polled a sample statistic for an update. (RHI-3624)

Stats parameter sets for SBB metrics will now all be visible to stats clients immediately after a service is deployed, rather than on first service use or Rhino restart. (RHI-3625)

Fixed a potential deadlock in the resource adaptor Cluster State Change Facility when multiple cluster nodes are restarted at the same time. (RHI-3629)

Treat profile-spec-ref as dependency when exporting profile tables. (RHI-3507)

Fixed an NPE that could occur attempting to subscribe to or unsubscribe from monitoring of a stats parameter set that only exists on a subset of Rhino nodes. In the unsubscribe case the NPE could cause nodes to shutdown and restart. (RHI-3518)

Fixed a memory leak which could occur in certain failure scenarios involving transaction time outs. (RHI-3557)

Rhino now requires Java version 1.7 or later. (RHI-3552)

A new extended Container Managed Persistence (CMP) API for support of Arrays, fast serialization, pass by reference and much more.

A new component type "SBB Part", a sub-component of a JAIN SLEE SBB. The SBB Part can define dependency links that enable components to re-define their dependencies (dynamic binding) during runtime.

Fully compatible and compliant with all existing applications.

Improved multi-nodes startup time by allowing nodes to boot up and initialise concurrently. (RHI-3217)

Added a new SBB local home interface as a Rhino-specific extension that allows a service to receive callbacks when it is about to be activated or deactivated. (RHI-3330)

SNMP counter ID mapping implemented. This permits the user to override the default mapping values given to usage parameter counters and gauges. This can be used to ensure that adding new counters to a parameter set doesn’t change the ID used by existing counters. (RHI-3330)

Rhino’s stats subsystem will now report sample distribution values for any sample population rather than just a certain range of samples. (RHI-1114)

The rhino-console command "removeactivitybinding" will now print an error message if the specified activity binding does not exist (RHI-1643)

Profiles can now be used from within the raVerifyConfiguration resource adaptor lifecycle method. (RHI-1999)

A node previously in the Running state no longer has the opportunity to forget this and restart in the Stopped state if the node fails to bootup and initialise properly during a restart. An alarm will now be raised if an exception occurs while attempting to transition the node to the Running state during bootup (ie. as a result of the -s argument or previous Running state). (RHI-2115)

Event router will no longer stall processing an event if an SBB increases its event delivery priority. (RHI-3350)

Rhino export now determines if the component is using standard or extension usage parameter sets and only generates the create-usage-parameter-set elements if its the standard case. (RHI-3355)

Fixed a classloader NoClassDefFoundError issue when deploying an SBB with an Activity Context Interface containing an attribute whose type implements FastSerializable and contains constructors referencing previously unresolved classes. (RHI-3366)

Provide earlier feedback of state exchange failures, for example if no address is available for listening. (RHI-3141)

Fixed an issue where serialization errors during database writes would raise an exception and an alarm and reset the connection instead of simply retrying the commit. (RHI-3346)

Fixed a classpath issue with the bundled Ant start script which caused RMI classloading issues with dynamically defined tasks using custom classes over a Rhino remote connection. (RHI-3455)

Fixed a race condition in the rate limiter in which work could be unnecessarily rejected. (RHI-3465)

In MemDB, exit the JVM as soon as an underlying Savanna group leaves the primary component. This fixes an edge case affecting clusters in which a subset of Savanna groups go non-primary, leaving a node only partially stopped and unable to release database resources and locks. (RHI-3268)

Fixed a NullPointerException that could occur in exceptional circumstances when initialising a replicated activity handler with cluster state during node startup, ultimately causing the node startup to fail. (RHI-3339)

Fixed a race condition which could cause failures in getting a JDBC connection to an external database in some connection pool configurations (RHI-3353)

Fixed a problem rolling back transactions when more than one JDBC datasource is enlisted. (RHI-3356)

Fixed an infinite event router loop that occurred if an SBB failure occurred during the activity cleanup phase of activity end processing. (RHI-3183)

Fixed an exception that could occur detaching an SBB from an activity during activity end processing if the SBB state for some reason did not agree with the activity state. (RHI-3183)

Added watchdog.oom_gc_enabled option that runs an explicit GC when the over memory use limit condition is reached. Default is to try to detect if this behaviour is required (-XX:DisableExplicitGC absent and a G1 collector present = System.GC() at over limit, otherwise don’t System.GC). (RHI-3374)

Increased default heap size for quorum nodes, current size could cause continuous CMS collections on Java 7. (RHI-3257)

Rhino will no longer perform an activityUnreferenced() callback to a resource adaptor that requested it for an activity that is unreferenced but is already ending. (RHI-3247)

Rhino’s periodic activity liveness scanner now checks if an idle activity is unreferenced and performs the appropriate callback to the owning resource adaptor if requested. One result of this is that unreferenced null activities, orphaned due to conditions such as overload, will now be noticed by the scanner and cleaned up appropriately. (RHI-3248)

Exporter fix:, SBB dependencies on resource adaptor entity link name bindings are now correctly associated with service activation (a’la SLEE 1.1) rather than SBB deployable unit installation (a’la SLEE 1.0). (RHI-3325)

An SBB may now successfully invoke suspendDelivery() and resumeDelivery() on a given event context in a single transaction as much as they like. Furthermore, isSuspended() will now return the correct transactional state. (RHI-2374)

Removing per-node activation state containing active services will no longer leave dangling references to resource adaptor entity link name bindings. (RHI-3328)

A profile may now successfully invoke ProfileContext.getProfileName() to obtain its identity during profileActivate(). (RHI-2793)

Fixed export of certain profile attribute types. This change is backwards compatible with exports produced by previous Rhino versions except for the special treatment of the "\u" character sequence now introduced. When using an export produced by a previous version of Rhino, any "\u" character sequence encased in a CDATA block should be changed to "\\u" otherwise Rhino will attempt to parse the characters following it as a unicode value. (RHI-3179)

The event router will no longer stall processing events for an activity if an exception such as lock timeout occurs while trying to obtain the transactional state for the activity. (RHI-3236)

Root SBBs that detach and remove themselves will no longer cause the event router to fail and roll back the transaction after event delivery. (RHI-3287)

Fixed incorrect SNMP OIDs for tables representing Rhino statistics. Updated associated MIB export logic to reflect the corrected table format. The old OID structure for statistics was: 1.3.6.1.4.1.19808.rhino(2).statistics(1).<parameter_set>.table(2).<column>.<index> The corrected OID structure for statistics is: 1.3.6.1.4.1.19808.rhino(2).statistics(1).<parameter_set>.table(2).entry(1).<column>.<index> The entry OID was previously missing. Any tooling which relied upon the old OIDs will need to be updated to include the extra '.1' for the entry object. (RHI-3303)

Fixed a slow memory leak which could occur when repeatedly connecting from a stats client at a high rate over a long period of time. (RHI-3313)

Fixed alarm entries incorrectly logging to all appenders on log file rollover instead of just the "AlarmsLog" appender. (RHI-3314)

Sample statistics will now be correctly reported to existing stats sessions if a monitored stats parameter set is removed and later recreated. (RHI-3320)

Profile queries no longer require a db lock on the default profile, removing a potential point of resource contention when using a pessimistically locked profile table in an application. (RHI-3273)

Added a new profile specification option, via the extension deployment descriptor, that allows the SLEE-defined copy of profile CMP field values from the default profile when a new profile is created to be disabled. Disabling this copy can remove a point of lock contention in applications that use pessimistically locked profiles to store or share session state. (RHI-3274)

Added "getdescriptor" command to rhino-console, which displays the SLEE descriptor for a component including the outgoing and incoming references. (RHI-3306)

Ensure that the committed view of attached SBB entities is ordered. This fixes a deadlock scenario involving: a) more than one replicated SBB attached to a replicated activity b) multiple cluster nodes simultaneously delivering an event on the replicated activity. (RHI-3280)

Rhino startup options can now be overridden by putting them in a file named "options" in the config directory. (RHI-3084)

Fixed a bug that meant the audit statistics for a node joining an existing cluster were incorrectly calculated during the first monitoring period. This could result in an OverLicensedCapacity alarm being incorrectly raised for the duration of the next monitoring period. (RHI-3336)

Follow-up to fix for RHI-3198, to prevent a spurious "over licensed capacity" alarm being raised and audit log record being written when a new node joins a running cluster. (RHI-3264)

Fixed a bug in which competing transactions could fail to initialise a set of statistics (a parameter set), resulting in an exception when the parameter set was used. (RHI-3263)

If the JMX Remote Adaptor m-let cannot bind to its configured ports at startup, it will now retry indefinitely until it succeeds. This prevents the situation where no cluster nodes are listening for management connections. (RHI-3260)

Fixed a number of bugs that could leave a database connection error alarm raised after the connection to the backing store for the in-memory database was re-established. (RHI-3255, RHI-3258, RHI-3262)

The timeout specified for the shutdown command will now be used correctly when handling backing database persistence during Rhino node shutdown. (RHI-3256)

Fixed a bug related to RHI-3226, that also caused Rhino to repeatedly resynchronise the backing store for the in-memory database. The problem occurred if multiple persistent databases were configured and one of the databases failed and recovered at the same time as the Rhino node assigned to handling the database connections failed and recovered. (RHI-3253)