RA JMS Recommendations / Known Issues
Recommendations based upon performance metrics:
1. Sender: JMS message sending is basically unlimited for JMS providers with standard configuration settings. It depends on the ability of the AutomationEngine to execute the sending of messages
Successfully tested: Up to 200 messages/minute of standard size (under 4MB) with 2 CPs, 4WPs on a single-node Automation Engine system.
Limitations: sending over 200 messages/minute with large payload sizes (more than 4MB).
2. Receiver: JMS message receiving is unlimited with standard provider configuration settings. Tens of thousands of standard messages can be received in under a minute.
Successfully tested: 10.000 messages/minute of standard size (under 4MB) with 2 CPs, 4WPs on a single-node Automation Engine system.
Limitations: none with standard provider configuration settings
3. It is not recommended to send and receive payload sizes above 200MB using the AE JMS agent.
4. Since the JMS messages are written directly into memory before being passed to the providers, for:
· payload sizes above 1MB, we recommend adding memory to the Java process running the agent. Starting the agent with the –Xmx2096m switch should also be considered.
· payload sizes above 10MB for messages larger than 10MB, we recommend doubling that memory availability to the Java process running the agent
Do(s) & Don't(s) with Known issues:
1. Check available memory for starting the RA JMS agent.
2. If sending or receiving large payloads (above 1MB) make sure the switch '–Xmx' is added to the start script with an appropriate amount of memory specified.
3. If using Oracle WebLogic, confirm the authentication information for the agent, and add it to the Connection Object in the General tab.
4. Check your JMS provider limitations on payload size settings and Queue/Topic storage
5. Confirm the provider's use and format of Dynamic Queuing. Selecting "Dynamic Queue" where the provider does not have this feature causes errors.