FioranoMQ Resource Adapter enhancements
Product Name: FioranoMQ
Version: 9.4.1
Fiorano Software is releasing version 9.4.1 of FioranoMQ. This release notes provides information about the enhancements and the resolved issues in this release.
Note: Visit the Fiorano Support Portal http://support.fiorano.com for details about any subsequent patches for this release. We recommend you to check for Patches prior to the installation.
Note: To upgrade your current FioranoMQ to FioranoMQ 9.4.1, please use the migration scripts provided at $FIORANO_HOME/fmq/bin/<migration folder>. Please follow the instructions provided in the readme.txt file provided in the same directory.
This section describes the new features introduced in the FioranoMQ 9.4.1 release.
Last Value Cache
Mainly applicable in the financial domain and pricing infrastructure world, the 'Last Value Cache' feature enables late-starting consumers (typically trading applications) to easily get an accurate ‘snapshot’ of data from a set of Topics concurrently, without the race-conditions that typically accompany this calculation using an external message broker without specific support for the feature.. This feature is introduced as an extension to the existing PubSub functionality of the FioranoMQ JMS Broker.
Spring Integration samples
FioranoMQ now shops with a comprehensive list of Spring integration examples covering all of the JMS features provided by Spring framework.
This section describes issues resolved in 9.4.1 release:
Messages are not rolled back properly when XA transactions are suspended even after the client connection is closed.
When the Pub-Sub flow control algorithm is disabled in the presence of a few slow subscribers, Non-Persistent messages are sometimes dropped in LIFO order instead of FIFO, when the in-memory connection buffers are full.
When large numbers of messages are consumed at a high rate, “Broken Pipe” socket error is thrown, eventually causing the Subscriber connection to break.
The Security Database gets corrupted with invalid user information when password length exceeds the max character limit.
Expired messages are not redirected to Dead Message Queue in Replicated High Availability mode.
Improper handling of ‘deliveryTransacted’ parameter at application server and ‘XAEnabled’ flag at Fiorano Resource adapter leads to message rollback.
In case of Bridge and Repeater, the API to remove a non-existing channel displays a successful operation result.
In a specific scenario, when a new bridge channel is added on a link, senders and receivers are not created on the queues which are linked by the channel.
A Receiver on a Target Queue does not get deleted on deletion of a channel in the Bridge.
The ‘Max client connections’ parameter in the dispatcher profile does not work properly when set to a zero value.
‘receiveNoWait’ call unnecessarily waits on empty Queues.
This section describes the new features introduced in the FioranoMQ 9.4.0 release.
FioranoMQ Resource Adapter enhancements
Support has been added for FioranoMQ Resource Adapter to use the Log4j implementation. Improvements have been made in ServerSession pooling mechanism of the FioranoMQ RA to ensure proper message flow and reduce the huge backlog of unacknowledged messages in the Queue.
C# Runtime Compression Support
Support has been added for message compression/decompression in C# runtime library which uses the ZLIB format. Using the ZLIB format ensures compressed messages received from the Java runtime library are decompressed to proper messages.
JMX API to get the Dropped messages count
A new JMX API is added to get the number of messages that are dropped for a Subscriber under certain scenarios. This feature is enabled only if the ‘EnableMessageMonitoring’ flag is enabled.
Support to configure keyStore and TrustStore
KeyStore and TrustStore for SSL/TLS communication can be initialized using JDK specific system properties, without the need to install the legacy Security Managers to initialize the same.
Option to forcefully kill Client Connections from FioranoMQ server
Support has been provided to disconnect client connections from the FioranoMQ Server through JMX operations and the web-management tool’s connection tab. The forceful connection kill will ensure a graceful connection close even if the AutoRevalidation feature is enabled on a client connection.
PSQ data cleanup
Support for Cleanup of Persistent Session Queue Data in case of slow subscribers has been added when the server restarts.
HA Replication
HA Replication calls revamped
HA Replication calls for message read and message commit have been revamped to handle replication call failures at the passive server. These are handled properly to ensure that messages are not delivered again when the passive server becomes active. So, while doing this it is made sure that the Active and Passive databases are exactly identical.
HA Replication support for Connection Consumers
Support for HA Replication calls has been handled for Connection Consumers, enabling application-server integration with FioranoMQ in HA mode.
HA Replication calls for message browser
HA replications are extended to support Queue message browsers.
Performance improvement
Performance improvement have been made in most of PTP scenarios when run in HA Replication mode.
eStudio
Fiorano MQ 9.4.0 comes with a brand new eclipse based Studio called as eStudio. The following features are available in eStudio.
1. Profile Editor for offline server profile configuration
2. Connection Management perspective to manage both Admin and JMX connections to a Server
3. UI crafted for Rich User Experience
Significant user feedback has been incorporated within eStudio to provide a richer user-experience.
This section describes issues resolved in 9.4.0 release:
[SI# 4344] Unable to browse or receive messages in a queue with RDBMS configured, though messages are shown from Studio and Database tables.
Memory leak observed while closing Queue Receiver on an RDBMS enabled Queue destination.
[SI# 4314] Problem in allocation of file handles to FioranoMQ’s data base layer, which leads to max file handle limit reached error.
[SI# 4272] Few HA object references are not cleaned up properly when passive server is restarted multiple times.
[SI# 4272] Heap growth observed when Non-Persistent messages of size > 1 MB (default in-memory Queue buffer size) are sent on to a Queue
[SI# 4271] Memory Leak fixed in Client Runtime while creating "PingEnabled" JMS Connections from the same JVM to two different MQ Servers
[SI# 4329] FioranoMQ PTP DB goes out of sync in Replicated HA under rare scenarios
[SI# 3899] In Web Management Tool, passive durable Subscriber’s count on a Topic shows negative values
[SI# 4273] Problem with Browse Message functionality of WMT (Web Management Tool) when accessed from outside LAN to the FioranoMQ server with multiple IPs, Public and Private IP.
[SI# 4273] Queue browsing functionality is not working in Web Management Tool when connected to a server running with non-TCP protocol.
Exception occurs in Publisher application when HA servers are in Transition state, with Publish behavior during AutoRevalidation set as blocking.
Improper 'managed connection matching' implementation in FioranoMQ Resource Adapter is leading to unlimited connection creation and heap growth in FioranoMQ server when integrated with Seaser framework.
Unable to read Client-Side Persistent Messages with 'String' property set using C/C++ runtime library.
Resolved inconsistencies in allowing special characters in a Queue name
Negative Queue Sender count observed in WMT's Monitor tab under certain scenarios.
BytesMessage throws exception while reading UTF with empty string.
JMX Notifications are not working with jdk 1.6
Issues with running DB recovery tool for analyzing CSP Cache and few other configurable parameters.
NullPointerException on HA server console when PASSIVE server is shut down during Transition state
Activating server doesn’t switch to Active state when Passive server is killed immediately after DB sync-up
Expired messages are not getting cleared from backup server in HA replicated mode
Queue/Topic Destination when deleted gets re-created automatically, in case an active consumer is listening on it.
Adding multiple socketAcceptors doesn't start all the socketAcceptors even after making changes in Configs.cfg
Secondary shared HA server doesn't run when configured using Configs.cfg because of incorrect name-value parameter semantics.
Messages are redelivered in case of PubSub with JMSRedelivered flag set to ‘false’, when FioranoMQ server is restarted multiple times.
The following changes are included in the FioranoMQ 9.3.1 release:
Default PrefetchCount for the JMS Queues has been changed to '30'. PrefetchCount is the number set for each QueueReceiver, so that whenever it requests for more number of messages from the JMS Queue, the Server will send those messages based on this count set. For more information on PrefetchCount and related parameters, please check Chapter 24: Performance Tuning And Deployment Parameters in FioranoMQ Handbook.
This section describes the new features introduced in the FioranoMQ 9.3.0 release.
1. CSP (Client Side Persistence) support for LPC mode
CSP support has been added for a client using LPC (Local Procedure Call) mode in FioranoMQ. In LPC mode, JMS clients hook onto FioranoMQ server locally within the kernel process without the need for socket connections. These clients are revalidated when the HA servers are under Active transition states, and during this state messages are stored into CSP directories.
2. Web console UI improvements
Web console views have been optimized to handle large data from the MQ server. The views by default shows 25 entries and rest of the entries can be traversed by clicking on provided navigation links. Number of entries per page is configurable. The optimized page view will have more responsive GUI when large number of entries to be displayed.
3. Support for use of multi-byte characters for FioranoMQ object names and Configurations
The names given for the admin objects like queues, topics, connection factories etc and client related parameters like message selectors, ClientIDs now support Japanese characters in them.
4. Slow Subscribers identification
FioranoMQ server will now fire notifications whenever a Subscriber is identified to be slow in subscribing messages.
5. C# RTL logging
Support has been added for C# Client Side logging to record information relating to the flow of client applications and error statements as applications execute and close. C# RTL logging implementation uses the .Net framework’s Trace Listeners and the Trace Switches where the log levels can be controlled externally through the <application-name>.config files.
6. Route configuration persistence
Support has been added to save routes configuration.
7. LDAP call optimizations
Optimizations are made related to redundant calls to LDAP provider from FMQ Server when getting the ACL information.
8. HA Replicated calls revamped
HA Replication calls for creating admin objects (like Queues, Topics, Connection Factories) and security principals (like FioranoMQ users, groups and Access control Lists (ACLs) are made similar to the message replication calls i.e., if the replication fails for any reason in the passive server (either failure propagated from passive server or failure during communication), the similar call in the active server is not made. So, while doing this it is made sure that the Active and Passive databases are exactly identical.
The following changes are included in the FioranoMQ 9.3.0 release:
1. JSSE package classes used for SSL-enabled communication (that is, when Connection Protocol is set to SUN_SSL) have been changed from com.sun.net.ssl.* to javax.net.ssl.*
2. In case of configuring Dispatcher Servers through Web Console, Studio or from MQAdminConnection, AdminURL and ConnectionProtocols parameters are removed as they are obsolete.
3. Improvised javaDocs for JMX Notification classes.
This section describes issues resolved in 9.3.0 release:
1. Memory leak in terms of number of threads created per TopicConnection in the Server JVM when the topicConnection is ‘started’ and is used for creating underlying sessions almost at the same time.
2. Memory leak in case of Persistent messages observed when the incoming messages are rarely (or never) ‘selected’ by the QueueReceiver running with Message Selectors set.
3. Passive durable subscribers’ count becomes negative when the durable subscriber is unsubscribed and re-created after each message.
4. Error with code “DESTINATION_UNSUBCRIBE_FAILURE_ERROR” on Subscriber Client console when the durable subscriber on a topic is unsubscribed and re-created after each message.
5. ArrayIndexOutOfBoundsException on server console when the durable subscriber on a topic is unsubscribed and re-created after each message.
6. ServerMetaData used for Dispatcher configuration should be made configurable much similar to other MetaData classes through web console.
7. ArrayIndexOutOfBoundsException while displaying licensing information of a never expiring license file in Web Management Console.
8. Utility JMX method to create journaling destinations on all destinations on which Message Journaling is enabled.
9. JMX Method getPersistentQueueBufferFactor on Queue MBean results in exception when invoked in Rpl HA.
10. JMX Methods listAllClients and getCompleteConnectionInfo results in incorrect information in case of UnifiedConnections.
11. Deletion of a preferred server and re-creating a normal dispatcher server with same ConnectURL is making the newly created dispatcher server as Preferred.
12. Messages sent from MSMQ to FMQ server are not received in proper format
13. DB Recovery tool always concludes SDB database as corrupted
14. Exception occurs on deleting a user with an Acl entry having default permissions
15. Enhancement to fire Advisory messages when Client Side Persistence corruption occurs
16. System Handle count of a C runtime application increases gradually when it is run continuously
17. C runtime application crashes when it is run in the server-less mode
18. New api, disconnect(ClientId)of MQAdminService added to the C runtime library
19. Java, C, C# RTLs should check for CSP Message expiry
20. Enhancement for having unique names for all Java client threads
21. Enhancement to make Jetty server logs configurable
22. ‘Failed to add RuntimeMBeans to the tree’ message in JMX Action Sink of Web Console
23. Unable to create LDAP Queue/Topic using Web Console
24. ‘removeLinkTopic()’ and ‘removeReplyTopic()’ of repeater component are not working properly in Web Console
25. Incorrect information shown in Durable Subscribers tab in Web Console when same subscription details are created on a different topic
26. Unable to delete the Acl permissions in Web console for some destinations like, JMX_SERVICE_QUEUE, JMX_CONNECT_QUEUE etc
27. Improper alert message is shown when a duplicate Bridge link is added
28. HA servers do not switch to ACTIVE/PASSIVE state when failovers are made during the DB synchronization.
29. Enhancement to add a JMX API to dump the active thread information into server.log files using ‘AdminService’ MBean.
30. General users can only be added to Administrators group by a member of ‘Administrators’ group, thus preventing the security threat of any user can add members to Administrators group.
31. FioranoMQ Server creates cron job with incorrect redirection if absolute path is used for –profilesDir.
This section describes the new features introduced in the FioranoMQ 9.2.1 release.
1. XA support for .Net clients
XA support has been added for CSharp runtime library. The resource manager implemented in CSharp RTL enables transactions between RTL resource manager and the FioranoMQ server’s resource manager. The CSharp RTL uses the System.Transactions namespace which provides both an explicit programming model based on the Transaction class, as well as an implicit programming model using the TransactionScope class.
2. Message Selector performance improvement
Code optimizations are done when evaluating conditional statements of a message, which improves the overall performance of simple integer and string message selectors.
This section describes issues resolved in 9.2.1 release:
1. On machines with multiple network interfaces installed, the numbers of open file descriptors keep increasing with time.
2. Memory keeps increasing when lookup method of C/C++ RTL is invoked repeatedly when the FioranoMQ server is down.
3. Improper replication of persistent messages sent to queue when the network between HA servers fluctuates that results in the failure to deliver such messages to connected clients
4. .Net framework in 64 bit machines throws SynchronizationLockException when [MethodImpl(MethodImplOptions.Synchronized)] is used on static methods.
5. Destinations created with Japanese characters have problems storing their respective Acls in the SDB database.
6. CSharp runtime’s getMessageID() doesn’t return the complete message id.
7. Dashboard login throws an error if any of the connections exists with 'null' clientID, which occurs when Queue/Topic connections are left in the CREATED state without setting the clientID or creating an underlying session.
8. Fiorano Exception classes must be serialized in .Net RTL to propagate them across network.
9. Dashboard logs out automatically while handling large amount of data from FioranoMQ server, like the scenario of increasing number of connections, sessions, users etc.
10. Incorrect number of active producers/consumers shown in the Queues/Topics view of Dashboard.
11. Dashboard sometimes shows non-existing client connections under the connections tab when unified domain is used.
This section describes the new features introduced in the FioranoMQ 9.2.0 release.
1. Audit management
Audit Management provides a clear picture of the actions performed on Server’s security realms. This helps Administrators in detecting any security violation and conducting post-mortem analysis on the logged information. With the help of policies/rules, you can fine tune the server to log specific activities performed by a set of users or the successful/unsuccessful login attempts and so on.
2. Internationalization of dashboard and refining log statements
All log statements are internationalized and Japanese UI statements are added in dashboard.
3. CSP DB recovery tool
DB recovery tool is modified to handle database corruption in Client Side Persistence cache. If CSP cache is corrupted because of No disk space issue or client crash issue, the user will be able to recover the database and send those messages to the server.
4. SSL support for C# clients
SSL support has been added for CSharp runtime library. The CSharp client application can now use SSL capabilities of the server.
5. Bridge profile
Configuration files are added for bridges between FioranoMQ and other MQ vendors like SonicMQ, ActiveMQ, OpenMQ. Samples are also added to produce/consume messages from other vendors. See chapter 12 in FioranoMQHandBook for detailed information on how to configure profiles.
6. Python APIs
New JMS interface has been introduced in Python script for connecting Python applications to the FioranoMQ server. The Python APIs are extended to use the native C runtime library that has complete feature support. The Python package can be downloaded similar to other non-java client libraries.
The following changes are included in the FioranoMQ 9.2.0 release:
1. EnsureUniquenessOfClientID is changed to true. This flag will ensure that no two connections will be created with the same clientID. This is present in earlier version of releases also but its default value was set as false. Before migrating to this release, all clients connections need to be verified whether they are using a unique clientID or not.
2. StoreNPMessageInDb is removed as this flag does not have any effect.
3. Users with blank passwords are not allowed and password also cannot be changed to blank password.
4. Default dashboard ports for bridge and repeater is modified.
5. Shared HA servers cannot be started without specifying -dbPath argument while running the server.
6. Browse Queues option in ConfigureQueues is moved to MonitorQueues in fmq dashboard.
This section describes issues resolved in 9.2.0 release:
Client has to discard messages that are marked deleted while sending messages from CSP cache.
Connection close API is required at server level when auto revalidation is not enabled.
Message selectors functionality doesn’t work in repeater.
Hierarchical topics creation is not working in C clients.
Hierarchical topics deletion is not shown in dashboard.
Route deletion throws Null Pointer Exception when destination type is changed.
Server is printing the wrong IP Address on some machines.
Invalid reply topic names are accepted in repeater.
Directory Service logs are not shown in dashboard.
Duplicate links are created in bridge when same link is added multiple times through dashboard.
The implementation title is not substituted in the service display name when server is running as windows service.
Negative passive durable subscriber count is shown in durable subscribers view in dashboard when durable subscribers are created with same name multiple times.
The Windows service script does not work when profile name contains back slash "\".
JVM arguments are not handled properly in the windows service script.
Duplicate links are created in repeater when same link is added multiple times through WMT.
Connections with same client ID are not disconnected properly from dashboard.
Unable to configure Message Journaling on destinations in offline mode.
Repeater link configurations are not shown properly in JMX APIs'.
Dispatcher API addServerToCluster() accepts invalid arguments while adding members to its cluster.
Dashboard logs are to be made rolling and configurable for increasing log levels.
ConnectionFactory need to be edited for creating an SSL connection to server in C clients.
Memory graphs are throwing exceptions in StandAloneBridge dashboard logs.
Dispatcher is not listing all parameters of member servers in dashboard.
HA boot up wait time needs to be configurable.
Batching is not configurable at runtime in C clients.
CSP message browsing is not working for messages with string properties.
Memory leak is present in C clients logging implementation.
Expired messages are not moved to dead message queue in Route.
Multiple pings to gateway server are required to check whether the local machine is present in the network.
Dashboard doesn't have an option to add preferred server to dispatcher.
Reply topic configurations are not working properly in repeater.
Monitoring data shows double the number of connections in monitor.txt.
Dashboard is not displaying lock information in HA view.
Multiple lookups in multiple threads are throwing exceptions occasionally.
FioranoMQ server doesn't start on system reboot with Linux service scripts.
Compression should not be enabled by default for large messages.
JMSMessageID is not retained on messages passing through route.
C clients are hanging sometimes on server cable pull out.
File appender name of Loggers is not persisted in configurations.
Newly created users are not shown in repeater dashboard.
Import topics in dashboard is not working when Hierarchical topics are present
Dispatcher profile cannot be configured in offline mode through Studio.
Resource Adapter is not working for JBoss 5.
Stream message samples are not present.
onException of exception listener is not called properly in clients.
HA shutdown script is not present to stop both active and passive servers.
This section describes the new features introduced in the FioranoMQ 9.1.0 release.
1. Directory Services Implementation
FioranoMQ 9.1.0 ships with a directory service implementation that allows users to share and manage FioranoMQ (FMQ) profiles in a centralized manner. Apart from helping manage the profiles via a central repository, the directory service also greatly simplifies the storing of information pertaining to each server is registered with the profile. The directory service is also used to manage resources other than profiles.
For more information, refer to Chapter 29 - Fiorano Directory Services in the FioranoMQ Handbook
2. HA Implementation Enhancements
FioranoMQ9.1.0 has several enhancements in the implementation of its High Availability servers. The changes ensure that the present solution will achieve better state synchronization between the two HA servers and robustness while handling network outage scenarios. A lock file based solution has been introduced for this very purpose.
1. State change is determined by a ping between the HA servers. In event of ping failure between HA servers, exclusive lock on a file on a third machine is used.
2. Additionally, Gateway Server IP address and port properties needs to be specified for HA profiles. This has been done to detect network failure between the HA server machines and the gateway machine.
Note: Gateway Machine is the machine hosting the LockFile.
3. To give preference to ACTIVE server to remain ACTIVE in case of network failure between HA servers, the following changes have been done:
· ACTIVE server tries to re-acquire lock on the LockFile after each configured interval.
· PASSIVE server will wait for a specified time before trying to acquire the lock on LockFile in case of a network failure between HA servers.
4. The server state of the last standalone server is persisted in the lockfile which implies that if this particular server is restarted without the passive server it would still achieve standalone state.
The lock file based mechanism ensures that, even when the private link between the servers goes down, there is no chance of both the servers becoming active. Under no circumstance will both the servers be active/ standalone at the same time.For more information, refer to FioranoMQ 9 High Availability Guide.
3. Message Journaling Support
Message Journaling is a FioranoMQ9.1.0 feature that allows an application to replicate the messages arriving at a destination to another destination of similar type. Message Journaling essentially means to copy a message from one destination to another destination of similar type. When Journaling is enabled, a console-based application can be written in order to consume messages from either of these two destinations. This functionality can be used to audit all the messages that have ever been received on a particular destination.
For more information, refer to Chapter 16 - Message Journaling in the FioranoMQ Handbook.
4. Destination Level configuration
Parameters at the Subsystem level that are also relevant on a per-destination basis are now configurable at the destination level. For instance, users can now have different values of PurgeLevelIndex for different topics.
For more information, refer to Section 27.1 - Support for Destination Level Configuration in the FioranoMQ Handbook.
5. Queue/Topic depth monitoring
Depth monitoring is used to monitor the number of pending messages that are currently available on a destination. Depth monitoring fires JMX notifications in situations when the depth of a destination crosses a particular threshold in either direction (increasing or decreasing queue sizes) or if destination is idle for a particular amount of time. Depth monitoring in FioranoMQ 9.1 is only implemented for Queues. Future versions may extend this feature to Topics.
For more information, refer to DepthMonitoringEnabled parameter available in Chapter 3 - Queue Subsystem Level Configuration as a part of the FioranoMQ Reference Guide.
6. Samples to integrate with the Spring Framework
JMS samples have now been provided that are compatible with and configurable using the Spring Framework. The Spring Framework in a messaging context can be used to provide configurative registration of message listener objects for transparent message consumption from message queues via JMS, an improvement of message sending over standard JMS APIs.
For more information, refer to Section 27.8 - Integration with Spring framework in the FioranoMQ Handbook.
7. Enhancements in DB recovery tool
The recovery tool now provides much information on what exactly is corrupted, together with the steps that have been taken in recovering the same.
For more information, refer to Chapter 24 – DB Recovery Tool in the FioranoMQ Handbook.
8. Other Enhancements
FMQ Samples without JNDI are now available.
Support for Large Messages in C and C++ runtime is provided.
Improved thread management in FMQ Dashboard.
Support for Dynamic topics in Repeater.
Support for Offline configuration of individual destinations is provided.
The summary of Mbeans and their distinction in the JMX tree is now visible from the dashboard.
The following changes are included in the FioranoMQ 9.1.0 release:
1. Default PingEnabling
FioranoMQ9.1.0 now has default support for pinging. Pinging a connection helps identify if the connection has gone stale or is broken due to network problems. This feature, which was also available in previous releases, is now enabled by default in FioranoMQ9.1.0 for all profiles.
For more information, refer to Section 4.8 – Pinging in the FioranoMQ Handbook
2. Inconsistency in text based configuration resolved
Prior to FioranoMQ9.1.0, there were a few irregularities with the Text based configuration file within each profile. This caused a few difficulties for users who were used to editing profiles using Studio. A few parameters like the URL in the RDBMS manager were not being set even after saving profile via the Studio. The text based configuration is now much more robust while handling a profile saved using Studio.
This section describes issues resolved in 9.1.0 release:
Separate session threads to be named differently.
Unable to reset password without the providing the current password for Administrators.
ListActiveClientConnections of AdminService MBean should include information about ClientIDs.
Non persistent messages must be dropped when sent in batch mode with insufficient credentials.
Server does not start properly with old databases; need to provide DB up gradation tool.
Client to start multiple pinger threads, in case, connections are made to multiple servers (running on different machines).
Text based configuration support needed for StandAloneBridge and StandAloneRepeater profiles.
PTP clients go into blocked state when messages are purged from the queue.
Closing a queue sender with queue name set to ‘null’ is throwing exception on the console.
Sometimes Unified Sessions doesn’t gets closed in Unified domain.
Unable to create route with message selector.
Dynamically added link does not start in repeater.
Replicated HA Primary server should not run with shared HA Secondary server and vice versa.
Bridge does not reconnect properly.
In Repeater/Bridge starting an already started link leads to incorrect behavior.
Running create-database script when Configs.cfg only is changed doesn't result as expected.
WMT: A timer thread started for the graphs does not stop even after you log out from it
Export/Import Topics or Queues functionality works incorrectly in WMT when description is set to null or empty string.
Dashboard is not allowing to delete topics with their names containing '*'
Security Credentials {Username and Passwd} are not getting changed properly when editing the Link Configuration for Bridges.
In ConfigureUsers TAB of Dashboard, the number of action buttons for ChangePassword operation needs to be optimized.
Adding MonitorLink and saving configuration leads to NPE
Policies Tab is not updating ACL properly in the scenario of removing default ACL.
This section describes the new features introduced in the FioranoMQ 9.0.1 release.
1. DataBase upgradation
utility
A script based utility has been added to automate upgrade of older versions
of FioranoMQ databases to FioranoMQ 9. This enables user to use their
old databases with latest FioranoMQ version, thus ensuring that
any data available in the old database is compatible with the latest FioranoMQ
version. The script while accepting minimal inputs provides all relevant
migration changes seamlessly. More detailed instructions on running this
script and the various input parameters required are explained in the
README file at
{FIORANO_HOME}/fmq/bin/Linux_DBMigration/Readme.txt or
{FIORANO_HOME}\fmq\bin\Windows_DBMigration\Readme.txt in the latest version.
This section describes the new features introduced in the FioranoMQ 9.0.0 release.
1. Enhanced Property file based HA profile configuration
All the important parameters like backup HA IP address, port, gateway IP address etc, which are used in HA configuration files are grouped at the start of the HA configuration files. This enables users to edit the configuration files easily to set up replication HA and shared HA profiles.
2. Client Side logging support in C/C++ runtimes
Support has been added for Client Side logging to record information relating to the flow of client applications, error statements and information relating to the memory being freed up as applications execute and close. This helps in getting more debug information in case of production issues. For more information on how to set different log levels, to enable or disable logging, and to set log names please refer to FioranoMQ CRTL Guide and FioranoMQ C++ RTL Native Guide for C and C++ runtimes respectively.
3. Enhanced Client Side Persistence (CSP) in C/C++ runtimes
New APIs have been added in order to browse the CSP messages, such as getting the number of messages in CSP Queue or Topic, retrieving queues, topics on a connection etc. Please refer to the FioranoMQ CRTL Guide and FioranoMQ C++ RTL Native Guide for C and C++ runtimes respectively for a detailed description of each API.
4. Enhanced FioranoMQ web console
The following new tabs have been added for configuration or monitoring:
A dispatcher tab which enables operations such as adding and removing servers to the Dispatcher-enabled MQ Server.
A Sockets view tab to monitor all the open Sockets on the FMQ Server.
A System properties tab which lists all the java system properties that are set in the JVM in which the FMQ Server is running.
An Enhanced Connections tab which lists all the JMX connections made to the FMQ Server.
5. Bug fixes (including bugs reported through the Fiorano Support Portal).
For more details, see Resolved Issues section.
This section describes issues resolved in 9.0.0 release.
Crash in C runtime with multiple disconnects with server while using CSP
In HA after multiple failovers messages are not received consistently
In case of persistent messages, the messages does not get persisted into the message store when the message index in the message store reaches to the maximum integer value that is Integer.MAX_INT.
In the web management tool, the image files created for generating the graphs does not get deleted.
Delay in message delivery in case of onMessage exception
ListTopics is not displaying all topics information properly
Invoking MBean operations such as showLinkTopicConfiguration and showReplyTopicConfiguration in Repeater leads to improper results.
The subscriber throws socket timeout exception when the server takes long time to come back due to power failure.
The log files does not get created in the path specified by the dbPath argument.
Exception while adding file appender to Logger through JMX
In Solaris machine StandAloneRepeater Profile gets corrupted after saving its configuration.
Show Alerts in WMT related to memory status
New Hierarchal Topics samples in C/C++ clients
Web Management tool should show the server’s starting time
Exception on restarting the dispatcher after adding servers to cluster and saving configuration.
This section summarizes the minimum system requirements for FioranoMQ. The actual product documentation includes the same in detail:
|
Platform |
Requirements |
|
Windows |
Microsoft® NT Server 2003, XP Professional Java 5 or above Processor: 1 GHz or faster 32-bit or 64-bit processor Min Physical RAM : 2 GB Min Disk Space : 5 GB |
| Linux |
Red Hat, Suse, Debian Java 5 or above Processor: 1 GHz or faster 32-bit or 64-bit processor Min Physical RAM : 2 GB Min Disk Space : 5 GB |
|
HP-UX |
11i and above Java 5 or above Processor: 1 GHz or faster 32-bit or 64-bit processor Min Physical RAM : 2 GB Min Disk Space : 5 GB |
| IBM AIX |
5x and above Java 5 and above Processor: 1 GHz or faster 32-bit or 64-bit processor Min Physical RAM : 2 GB Min Disk Space : 5 GB |
| Solaris |
9x and above Java 5 and above Processor: 1 GHz or faster 32-bit or 64-bit processor Min Physical RAM : 2 GB Min Disk Space : 5 GB |
Note:
Minimum
5
GB of hard disk space is required to run Fiorano MQ server. As
number of persistent messages increases in the server, more disk space is
required to store those messages.
Fiorano Studio requires Java 5 or above
The entire FioranoMQ documents are available online. The FioranoMQ documentation includes:
|
Document Name |
Description |
|
FioranoMQ Concepts Guide |
Contains description on concepts and features of FioranoMQ. |
|
FioranoMQ Handbook |
Contains detailed description on how to use FioranoMQ and its features. |
| FioranoMQ Reference Guide |
Contains detailed description and examples for all the parameters used in FioranoMQ server and other components of FioranoMQ. |
|
FioranoMQ Best Practices Guide |
Contains the information about the performance tuning and deployment parameters. |
|
FioranoMQ High Availability Guide |
Contains the salient features of FioranoMQ's HA solution. It explains the working and the underlying architecture of the entire solution. It also provides step by step instructions on enabling HA in FioranoMQ. |
|
FioranoMQ Getting Started
|
Contains the information on startup to assist users of FioranoMQ. This document introduces users to the components of FioranoMQ and briefly explains the working of these components. |
|
FioranoMQ JMX API Guide |
FioranoMQ exposes a lot of JMX API’s which the user can invoke at runtime to change the configuration and behaviour of the MQ server in online mode. This document lists the set of MBeans exposed through JMX, and the attributes and operations within the MBean which the user may want to invoke. |
|
FioranoMQ C-RTL Guide |
This guide provides an introduction to FioranoMQ C RunTime library. Provides a summary of the various functions based on their usage and a detailed description of the APIs included in this library. Details out the steps involved in compiling and running CRTL sample applications. This guide also contains the sample programs illustrating the use of C-RTL for PubSub and PTP operations. |
|
FioranoMQ C++ RTL(Native )Guide |
This guide contains an overview of the C++RTL specific Data types and Constants, Error handling, Dot Net, API References, Sample Programs, and FAQ’s. This guide also describes usage of C++ Runtime for connecting to FioranoMQ server. The various sample programs illustrates the use of simple Publish-Subscribe and Point-To-Point operations |
|
FioranoMQ Native Csharp RTL Sample Application Guide |
This guide contains the sample programs illustrating the use of Native CSharp-RTL for PubSub and PTP operations. |
|
FioranoMQ API Documentation |
This guide describes of all the classes used in C# RTL. |
|
FioranoMQ FAQ’s |
This Online Help contains compilations of information about FioranoMQ, which are usually the result of certain questions constantly being asked. |
Submit and track your support issues at http://support.fiorano.com
This requires a valid login; please contact your sales representative for the Fiorano Support Portal Login.
If you have any questions and/or comments on FioranoMQ, please feel free to contact us at:
Fiorano Software Technologies Pvt. Ltd.
Our Website - http://www.fiorano.com
Evaluation Support – presales@fiorano.com
Check out our Developer Zone at Uwww.fiorano.com/devzone/dev_zone.php
United States:
1-800-663-3621 (Toll-Free within the USA) or +1-650-326-1136 (9 AM to 5 PM Pacific Time)
Asia Pacific:
+91 80 40170000 (9 AM to 5 PM India Standard Time)
Japan:
+81 3 5464 3874 (9 AM to 5 PM Japan Standard Time)
Europe and Middle East:
+44 (0) 1932 895005 (9 AM to 5 PM London Standard Time)
Copyright © 2008-2011, Fiorano Software Pte. Ltd. and affiliates.
All rights reserved.
This software is the confidential and proprietary information of Fiorano Software ("Confidential Information"). You shall not disclose such Confidential Information and shall use it only in accordance with the terms of the license agreement enclosed with this product or entered into with Fiorano.