Shared File System Assumptions and Limitations

The following are some of the assumptions and limitations you must be aware of when using the Shared File System option to store FIFO data for ActiveMQ.

• Encrypted passwords for database storage are not currently supported. The file system based storage option described in this topic provides an alternative that does not require you to expose the database passwords.
• If an ActiveMQ node loses its connection to its database or file system storage, ActiveMQ will shut down. This is the intended behavior. Sterling B2B Integrator currently does not employ out of the box monitoring for the ActiveMQ instances utilized for FIFO. To ensure seamless FIFO processing, the ActiveMQ nodes must be monitored and restarted if the instances are shut down for any reason.
• When ActiveMQ loses its database connection in conjunction with a Microsoft SQLServer database, ActiveMQ may hang during the shut down process. As a result, it may be difficult to determine if the ActiveMQ node has failed and requires to be restarted. It is recommended that you use the shared file system storage when using ActiveMQ in combination with a SQL Server database to avoid processing interruptions in failure scenarios.
• For information on file locking limitations while using ActiveMQ file system, see http://activemq.apache.org/shared-file-system-master-slave.html.
• If you are reconfiguring any ActiveMQ options, ensure that you have executed all FIFO business processes. Failure to execute all FIFO business processes may result in the existing FIFO business processes remaining in an ‘Active’ state, in turn resulting in loss of FIFO ordering for the processes in the ‘Active’ state. To continue successful processing, the business processes in the ‘Active’ state will have to be manually halted and restarted.