Contents

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For more information on High Availability, refer to the FioranoMQ the High Availability Guide section.

Primary Server Configuration

...

Presented below are the details for the parameters in Fiorano ->HA->HAConnectionManager->FioranoHAConnectionManager->config> HA > HAConnectionManager > FioranoHAConnectionManager > config.

Port

The Port parameter specifies the port on which the HA Manager listens on for connections from the peer HA Server. This parameter listens for a connection from HA Peer Server in order to know the status of its peer.

...

The range of integer values considered valid by the Port parameter in java are is -2^31 to 2^31 -1.

Note: The port may not be used by other services when being used to listen to Peer servers..

...

The range of integer values considered valid by the SocketInitializationTimeout parameter in java are is -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

Presented below are the details for the parameters in Fiorano ->HA->HAConnectionManager->HAServiceManager->HASubSystems->QGMSStubManager> HA > HAConnectionManager > HAServiceManager > HASubSystems > QGMSStubManager.

MinServiceID

The MinServiceID parameter defines a serviceID in FioranoMQ with each request associated with a subsystem. The range of serviceIDs associated with a subsystem defines the operations that are accessible to that subsystem. The MinServiceID defines the minimum value of the range that exists for the serviceIDs.

...

The range of integer values considered valid by the MinServiceID in java areis -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

The default value for the MaxServiceID parameteris null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MaxServiceID in java areis -2^31 to 2^31 -1.All values less than zero retrieve the same result.

...

Presented below are the details forthe parameters in Fiorano ->HA->HAConnectionManager->HAServiceManager->HASubSystems->TGMSStubManager> HA > HAConnectionManager > HAServiceManager > HASubSystems > TGMSStubManager.

MinServiceID

The MinServiceID parameter defines a serviceID in FioranoMQ. Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine the operations accessible to the subsystem. The MinServiceID defines the minimum value of the range that exists for the serviceIDs.

...

The default value of the MinServiceID  parameter is null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MinServiceID in java areis -2^31 to 2^31 -1.All values less than zero retrieve the same result.

...

The range of integer values considered valid by the MaxServiceID in java areis -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

Presented below are the details for the parameters in Fiorano ->HA->HAConnectionManager->HAServiceManager->HASubSystems->SyncRealmStubManager> HA > HAConnectionManager > HAServiceManager > HASubSystems > SyncRealmStubManager.

MinServiceID

The MinServiceID parameter defines a serviceID in FioranoMQ. Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine the operations accessible to the subsystem. The MinServiceID defines the minimum value of the range that exists for the serviceIDs.

...

The range of integer values considered valid by the MinServiceID in java areis -2^31 to 2^31 -1.All values less than zero retrieve the same result.

...

The default value for the MaxServiceID parameteris null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MaxServiceID in java areis -2^31 to 2^31 -1.All values less than zero retrieve the same result.

...

Presented below are the details for the parameters in Fiorano ->HA->HAConnectionManager->HAServiceManager->HASubSystems->SyncNamingStubManager> HA > HAConnectionManager > HAServiceManager > HASubSystems > SyncNamingStubManager.

MinServiceID

The MinServiceID parameter defines a serviceID in FioranoMQ. Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine the operations accessible to the subsystem. The MinServiceID defines the minimum value of the range that exists for the serviceIDs.

...

The default value of the MinServiceID  parameter is null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MinServiceID in java areis -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

The default value for the MaxServiceID parameteris parameter is null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MaxServiceID in java are-2^31 to 2^31 -1.All values less than zero retrieve the same result.

...

Presented below are the details for the parameters in Fiorano ->HA->HAConnectionManager->HAServiceManager->HASubSystems->NamingStubManager> HA > HAConnectionManager > HAServiceManager > HASubSystems > NamingStubManager

MinServiceID

The MinServiceID parameter defines a serviceID in FioranoMQ. Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine the operations accessible to the subsystem. The MinServiceID defines the minimum value of the range that exists for the serviceIDs.

...

The default value of the MinServiceID  parameter is null. If the value is specified as null, there is no range defined for the serviceIDs. The range of integer values considered valid by the MinServiceID in java areis -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

The MaxServiceID parameter defines a serviceID in FioranoMQ.  Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine determines the operations accessible to the subsystem. The MaxServiceID defines the maximum value of the range that exists for the serviceIDs.

...

The default value for the MaxServiceID parameteris parameter is null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MaxServiceID in java areis -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

Presented below are the details forthe for the parameters in Fiorano->HA->HAConnectionManager->HAServiceManager->HASubSystems->SyncQueueStubManager

...

The MinServiceID parameter defines a serviceID in FioranoMQ. Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine determines the operations accessible to the subsystem. The MinServiceID defines the minimum value of the range that exists for the serviceIDs.

...

The default value of the MinServiceID parameter is null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MinServiceID in java areis -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

The MaxServiceID parameter defines a serviceID in FioranoMQ.  Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine determines the operations accessible to the subsystem. The MaxServiceID defines the maximum value of the range that exists for the serviceIDs.

...

The default value for the MaxServiceID parameteris parameter is null. If the value is specified as null, there is no range defined for the serviceIDs.The range of integer values considered valid by the MaxServiceID in java areis -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

The MinServiceID parameter defines a serviceID in FioranoMQ. Each request is associated with a subsystem. A range of serviceIDs associated with a subsystem determine determines the operations accessible to the subsystem. The MinServiceID defines the minimum value of the range that exists for the serviceIDs.

...

The range of integer values considered valid by the MinServiceID in java areis -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

The range of integer values considered valid by the MaxServiceID in java areis -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

Presented below are the details forthe for the parameters in Fiorano ->HA->ReplicableRealmMgr->RpRealmManager->FioranoRpRealmManager->config> HA > ReplicableRealmMgr > RpRealmManager > FioranoRpRealmManager > config

AclZipPath

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize realm related (ACL based) information a zip file containing the ACL information present in this server must be created. The AclZipPath parameter allows the configuration of the path where this file is located.

...

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize principal related (User-based) information, a zip file is created using the information related to the principal present in the Server. The PrincipalZipPath parameter allows the configuration of the path in where this file is located.

...

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize principal related (User-based) information, a zip file is created using the information related to the principal. The PrincipalUnzipDir parameter allows the configuration of the path where this zip file is temporarily unzipped.

...

The range of integer values considered valid by the SocketTimeout parameter are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

Presented below are the details of the parameters in Fiorano ->HA->ReplicableNamingMgr->RpNamingManager->FioranoRpNamingManager->config> HA > ReplicableNamingMgr > RpNamingManager > FioranoRpNamingManager > config.

ZipPath

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize name related information a zip file using  naming naming related information present in the Server is created. The ZipPath parameter allows the configuration of the path where this file is located.

...

The range of integer values considered valid by the SocketTimeout are is -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

Presented below are details of the parameters in Fiorano ->HA->HAKRPCProvider->FioranoHAKRPCProvider->config> HA > HAKRPCProvider > FioranoHAKRPCProvider > config.

BackupHAPort

The BackupHAPort parameter specifies the port of the backup peer Server on which the peer is listenens for status listens to status requests sent by the Server.

...

The BackupHAIPAddress parameter specifies the IP address of the backup peer Server on which the peer listenens listens for status requests sent by the Server.

...

The range of integer values considered valid by the SocketTimeout are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

The range of integer values considered valid by the SocketCreationTimeout are is -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

Presented below are the details of the parameters in Fiorano->HA->HAManager->StatusPersister->FioranoStatusPersister->config.

Path

In Replication-based HA mode state information is replicated between FioranoMQ Servers through replication channels. Loading and storing of the replicated is are done by the StatusPersister. The Path parameter helps to configure the path of the file where the status that is persisted is located.

...

The Primary parameter is a boolean parameter that indicates whether the acting Server acts as the primary HA Server when in the Replication HA mode. In FioranoMQ's HA implementation, one of the two HA Servers is the primary server while the other is  is the secondary Server. For more information about FioranoMQ's HA implementation, please refer to FioranoMQ Concepts Guide Chapter 16 or FioranoMQ to High Availability Guide section.

Valid values:

The default value of the Primary parameter is yes.

...

The range of integer values considered valid by the PingInterval are is -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

The GatewayServerPort parameter helps to specify the port on which the Gateway machine listenens listens for incoming requests.

Valid values:

...

The range of integer values considered valid by the GatewayServerPort are is -2^31 to 2^31 -1.

Note: The port should not be in use..

SocketCreationTimeout

SocketCreationTimeout isthe is the time in milliseconds within which the socket has to connect with the peer Server failing which the socket creation attempt fails.

...

The range of integer values considered valid by the SocketCreationTimeout are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

In FioranoMQ's HA implementation a gateway machine is used to detect the HA Server which is no longer available on the network. It makes sense to use the actual gateway Server of the network in which the enterprise Enterprise Server is deployed as the Gateway machine for HA.

The GatewayServerIPAddress parameter helps to specify the IP address on which the Gateway machine listens for incoming requests.

...

The range of integer values considered valid by the MaxWaitTimeout are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

This parameter indicates the wait time to detect backup server during local server bootup. If the backup server is not available then local server will switch to standalone after acquiring the lock. A higher value of this parameter can avoid one of the server switching to standalone, thus avoiding unnecessary database replication at the cost of more wait time during server boot up.

...

This parameter indicates the maximum number of times gateway server will be pinged for detecting a server failure. This will be useful in case of a weak network link between gateway server and ha server. Increasing this parameter should be done after consulting the Fiorano support team as increasing this parameter can disrupt ha functionality.

Default value: 1

AutoPassiveResetEnabled

Boolean to denote if the automatic reset of the passive server is enabled or not.

Enabling this flag will switch on the “automatic reset of passive server” feature, and will result in active server initiated restarts/shutdowns of the passive server in case of exception limit breaches within the configured time thresholds. Restarts/shutdowns will be initiated with every breach of 'FioranoException' or 'IOException' exception counts. Whereas, in case of 'Disk Full' errors, passive server shutdowns will be initiated directly without any passive server restart attempts.

Enabling this flag auto enables other supporting APIs with their default values:

  • MaxPassiveExceptionLimit: to set the exception limits.
  • MaxPassiveIOExceptionThresholdPercentage: to set the IOException threshold percentage.
  • MaxPassiveRestartAttempts: to set the maximum number of restart attempts.
  • PassiveExceptionTimeThreshold: to set the threshold time.

The feature will prevent any potential hindrance to message processing which can occur due to any unhandled errors caught because of the passive server unresponsiveness.
Unresponsive passive servers will block the message flow, with the active server being stuck at the waiting stage and throwing large error logs of every message sent. This could also result in piling up of the CSP cache eating away the resources.

Hence, to overcome such situations, restarting or shutting down an unresponsive passive server is the way out, making sure that the primary broker continues serving the message flow either in the ACTIVE state or the STANDALONE state, minimizing flow blockages and HA performance degrades.

Server restart is required for changing default values

Valid values:

  • true – automatic reset of passive server will be enabled.
  • false - automatic reset of passive server will not be enabled.

Default Value :

  • false - automatic reset of passive server will not be enabled.

MaxPassiveExceptionLimit

Maximum exception limit after which the passive server will be reset. The exception-count will get reset to '0' after every passive server restarts/shutdowns.

Server restart is required for changing the default values.

Valid values: Positive integer values
Default Value: 100 (breach happens at 101st exception)

Note: Values less than 0 are considered as illegal value as the count cannot be negative. The value '0' will result in passive reset with just a single exception hit.

MaxPassiveIOExceptionThresholdPercentage

Percentage of IOExceptions to be taken into account for checking if the maximum exception limit is breached.

Server restart is required for changing the default values.

Valid values: Positive float values
Default Value: 25.0 (i.e takes in 25 IOExceptions for every 100 IOExceptions caught)

Note: Values greater than '100' are considered as illegal values as it will increase the exception count much more than the actual number of exceptions caught. The value '0' will result in not considering any IOExceptions caught for calculating the exception limit count, whereas the value '100' will consider all the IOExceptions caught.

MaxPassiveRestartAttempts

The maximum number of attempts to reset passive server by restart after which it will be shut down.

In most cases, restarting a passive server will suffice its recovery. However, in certain cases of HA state correction, shutting down the passive server is recommended. Hence, after the breach of the desired number of restart attempts, the passive server will shut down.

The restart attempts count is reset back to '0' only after the active server is restarted.

Server restart is required for changing the default values.

Valid values: Positive integer values
Default Value: 5

Note: Values less than '0' are considered as illegal values as the number of attempts cannot be negative. Value '0' will result in an immediate shutdown of the passive server once the exception limits are breached.

PassiveExceptionTimeThreshold

Time threshold within which if the exception limit is breached, the passive server will be reset.

Server restart is required for changing the default values.

Units: Milliseconds
Valid values: java.lang.Long values
Default Value: 300000 (5 minutes)

Note: Values less than '0' are considered as illegal values as time cannot be negative. Whereas '0' is considered as infinite time.

FioranoFMQKernel

Presented below are the details for the parameters in Fiorano->HA->FMQKernel->FioranoFMQKernel->config.

...

The default value for the MQUnDeploymentLists parameter is kernel.lst,DefaultMQObjects.lst.

A comma-separated list of .lst files is a valid value for this parameter.

...

When in the Active mode the HA Server works normally. While in the Passive mode, the HA Server only monitors its peer and does not handle any client requests. All client connection connections to the Server when it is in the Passive mode are refused. If a peer Server goes dead the Server goes into the Standalone state. In order to not accept any client connections while in passive state, a few components of the Server need to be undeployed. When the Server is in the Active state these components need to be undeployed.

...

The default value for the ExternalUnDeploymentLists parameter is null.

A comma-separated list of .lst files is a valid value for this parameter.

...

When in the Active mode the HA Server works normally. While in the Passive mode, the HA Server only monitors its peer and does not handle any client requests. All client connections to the Server when it is in the Passive mode are refused. If a peer Server goes dead then the acting Server goes into the Standalone state. In order to not accept any client connections while in a passive state, a few components of the Server need to be undeployed. These components are redeployed when the Server starts accepting connections.

...

Given a relative path for a file name the files are searched for in the directory: <current-profile>/deploy/. If  If an absolute path is given files are searched in that directory.

...

The components to be undeployed are listed in Fiorano files. The ExternalDeploymentLists  parameter parameter helps specify lists of files (separated by commas) containing external components that are to be redeployed when necessary.

...

The default value for the ExternalDeploymentLists parameter is null.

A comma-separated list of .lst files is a valid value for this parameter.

...

The range of integer values considered valid by the SocketTimeout are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

The SocketTimeout indicates the time in milliseconds before the socket timesout timeout for the replicable component occurs. Replication of all queue related information must be done within this time.

...

The range of integer values considered valid by the SocketCreationTimeout are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

The Port specifies the port on which HA Manager listens for connections from the peer HA Server. In addition, the HA Server listens for a connection from its HA peer Server to determine  the the status of its peer on this port. The Port parameter is used specifies this port.

...

The range of integer values considered valid by the SocketCreationTimeout are is -2^31 to 2^31 -1

Note: The port specified should not be in use..

NagleAlgo

The NagleAlgo is a boolean parameter that determins determines whether Nagle's Algorithm, is enabled at the time of socket creation with the peer HA Server. Nagle's algorithm is used in TCP/IP networks for congestion control. It works by coalescing a number of small outgoing messages and sending them all together. If there is a sent packet for which the sender has received no acknowledgment, the sender output needs to be buffered until it if there isa is a full packet worth of output which can then be sent in one go.

...

The range of integer values considered valid by the SocketInitializationTimeout are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The default value for the MaxServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

The default value for the MinServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

The default value for the MaxServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

The default value for the MinServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The default value for the MaxServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero are retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

The default value for the MinServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

The default value for the MinServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The default value for the MaxServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

The default value for the MinServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The default value for the MaxServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The default value for the MaxServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

The default value for the MinServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MinServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The default value for the MaxServiceID is null. A null value indicates that there is no defined range of serviceIDs.The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MinServiceID value defines the minimum value of that range.

...

FioranoMQ generates a serviceID with each request associated within a subsystem. The range of serviceIDs that are associated with a subsystem define defines the operations that are accessible to that subsystem. The MaxServiceID value defines the minimum value of that range.

...

The range of integer values considered valid by the MaxServiceID are is -2^31 to 2^31 -1All values less than zero retrieve the same result.

...

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize realm related (ACL based) information, a zip file is created using the ACL information. The AclUnzipDir parameter allows the configuration of the path where the zip file is temporarily unzipped.

...

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize principal related (User-based) information, a zip file is created using the information related to the principal present in the Server. The PrincipalZipPath parameter allows the configuration of the path in where this file is located.

...

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize principal related (User-based) information, a zip file is created using the information related to the principal. The PrincipalUnzipDir parameter allows the configuration of the path where this zip file is temporarily unzipped.

...

The range of integer values considered valid by the SocketTimeout parameter are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

The range of integer values considered valid by the SocketTimeout parameter are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

The BackupHAPort parameter specifies the port of the backup peer Server on which the peer is listenens listens for status requests sent by the Server.

...

The BackupHAIPAddress parameter specifies the IP address of the backup peer Server on which the peer listenens listens for status requests sent by the Server.

...

The range of integer values considered valid by the SocketTimeout are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

The range of integer values considered valid by the SocketCreationTimeout are is -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

Presented below are the details for the parameters in Fiorano->HA->HAManager->StatusPersister->FioranoStatusPersister->config.

Path

In Replication-based HA mode state information is replicated between FioranoMQ Servers through replication channels. Loading and storing of the replicated is done by the StatusPersister. The Path parameter helps to configure the path of the file where the status that is persisted is located.

...

The range of integer values considered valid by the PingInterval are is -2^31 to 2^31 -1. All values less than zero retrieve the same result.

...

The GatewayServerPort parameter helps to specify the port on which the Gateway machine listenens listens for incoming requests.

Valid values:

...

The range of integer values considered valid by the GatewayServerPort are is -2^31 to 2^31 -1.

Note: The port should not be in use..

...

The SocketCreationTimeout indicates the  the time in milliseconds within which socket must connect with the peer Server failing which the socket creation attempt fails.

...

The range of integer values considered valid by the SocketCreationTimeout are is -2^31 to 2^31 -1.

All values less than zero retrieve the same result.

...

In FioranoMQ's HA implementation a gateway machine is used to detect the HA Server which is no longer available on the network. It makes sense to use the actual gateway Server of the network in which the enterprise Enterprise Server is deployed as the Gateway machine for HA.

The GatewayServerIPAddress parameter helps to specify the IP address on which the Gateway machine listens for incoming requests.

...

In FioranoMQ's HA implementation a gateway machine is used to detect the HA Server which is no longer available on the network. It makes sense to use the actual gateway Server of the network in which the enterprise Enterprise Server is deployed as the Gateway machine for HA.

The GatewayServerIPAddress parameter helps to specify the IP address on which the Gateway machine listens for incoming requests.

...

The range of integer values considered valid by the SocketCreationTimeout are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

AutoPassiveResetEnabled

Boolean to denote if the automatic reset of the passive server is enabled or not.

Enabling this flag will switch on the “automatic reset of passive server” feature, and will result in active server initiated restarts/shutdowns of the passive server in case of exception limit breaches within the set time thresholds.
Restarts/shutdowns will be initiated with every breach of 'FioranoException' or 'IOException' exception counts.
Whereas, in case of 'Disk Full' errors directly passive server shutdowns will be initiated without any passive server restart attempts.

Enabling this flag auto enables other supporting APIs with their default values:

  • MaxPassiveExceptionLimit: to set the exception limits.
  • MaxPassiveIOExceptionThresholdPercentage: to set the IOException threshold percentage.
  • MaxPassiveRestartAttempts: to set the maximum number of restart attempts.
  • PassiveExceptionTimeThreshold: to set the threshold time.

The feature will prevent any potential hindrance to message processing which can occur due to any unhandled errors caught because of passive server unresponsiveness.
Unresponsive passive servers will block the message flow, with the active server being stuck at waiting stage and throwing large error logs of every message sent. This could also result in piling up of the CSP cache eating away the resources.

Hence to overcome such situations restarting or shutting down an unresponsive passive server is the way out, making sure the primary broker continues serving the message flow either in ACTIVE or STANDALONE states, minimizing flow blockages and HA performance degrades.

Server restart is required for changing the default values

Valid values:

  • true – automatic reset of passive server will be enabled.
  • false - automatic reset of passive server will not be enabled.

Default Value :

  • false - automatic reset of passive server will not be enabled.

MaxPassiveExceptionLimit

Maximum exception limit after which the passive server will be reset. The exception-count will get reset to '0' after every passive server restarts/shutdowns.

Server restart is required for changing the default values.

Valid values: Positive integer values
Default Value: 100 (breach happens at 101st exception)

Note: Values less than 0 are considered as illegal value as the count cannot be negative. The value '0' will result in passive reset with just a single exception hit.

MaxPassiveIOExceptionThresholdPercentage

Percentage of IOExceptions to be taken into account for checking if the maximum exception limit is breached.

Server restart is required for changing the default values.

Valid values: Positive float values
Default Value: 25.0 (i.e takes in 25 IOExceptions for every 100 IOExceptions caught)

Note: Values greater than '100' are considered as illegal values as it will increase the exception count much more than the actual number of exceptions caught. The value '0' will result in not considering any IOExceptions caught for calculating the exception limit count, whereas the value '100' will consider all the IOExceptions caught.

MaxPassiveRestartAttempts

The maximum number of attempts to reset passive server by restart after which it will be shut down.

In most cases, restarting a passive server will suffice its recovery. However, in certain cases of HA state correction, shutting down the passive server is recommended. Hence, after the breach of the desired number of restart attempts, the passive server will shut down.

The restart attempts count is reset back to '0' only after the active server is restarted.

Server restart is required for changing the default values.

Valid values: Positive integer values
Default Value: 5

Note: Values less than '0' are considered as illegal values as the number of attempts cannot be negative. Value '0' will result in an immediate shutdown of the passive server once the exception limits are breached.

PassiveExceptionTimeThreshold

Time threshold within which if the exception limit is breached, the passive server will be reset.

Server restart is required for changing the default values.

Units: Milliseconds
Valid values: java.lang.Long values
Default Value: 300000 (5 minutes)

Note: Values less than '0' are considered as illegal values as time cannot be negative. Whereas '0' is considered as infinite time.

FioranoFMQKernel

Presented below are the details for the parameters in Fiorano->HA->FMQKernel->FioranoFMQKernel->config.

...

These components are listed in FioranoMQ specified files. The MQUnDeploymentLists  parameter parameter helps specify lists of files (separated by commas) containing Fiorano specific components that are to be undeployed when necessary.

...

The default value for the MQUnDeploymentLists parameter is kernel.lst,DefaultMQObjects.lst.

A comma-separated list of .lst files is a valid value for this parameter.

Given a relative path for a file name the files are searched for in the directory: <current-profile>/deploy/. If  If an absolute path is given files are searched in that directory.

...

When in the Active mode the HA Server works normally. While in the Passive mode, the HA Server only monitors its peer and does not handle any client requests. All client connection connections to the Server when it is in the Passive mode are refused. If a peer Server goes dead the  Server goes into the Standalone state. In order to not accept any client connections while in passive state, a few components of the Server need to be undeployed. When the Server is in the Active state these components need to be undeployed.

...

The default value for the ExternalUnDeploymentLists parameter is null.

A comma-separated list of .lst files is a valid value for this parameter.

...

The components to be undeployed are listed in Fiorano files. The ExternalDeploymentLists  parameter parameter helps specify lists of files (separated by commas) containing external components that are to be redeployed when necessary.

...

The default value for the ExternalDeploymentLists parameter is null.

A comma-separated list of .lst files is a valid value for this parameter.

...

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. To be able to synchronize all topic related information a zip file containing  topic topic related information present in the Server is created. The ZipPath parameter allows the configuration of the path in which that file is located.

...

The range of integer values considered valid by the SocketTimeout parameter are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

...

In the Replicable mode of the FioranoMQ HA Server, consistency between the individual HA Servers must be maintained at all times. In order to be able to synchronize name related information a zip file using  naming naming related information present in the Server is created. The ZipPath parameter allows the configuration of the path where this file is located.

...

The range of integer values considered valid by the SocketTimeout parameter are is -2^31 to 2^31 -1

All values less than zero retrieve the same result.

Adaptavist ThemeBuilder EngineAtlassian Confluence