Skip to content

Latest commit

 

History

History
22 lines (12 loc) · 1.1 KB

JMSRequestReplyNonPersistent.md

File metadata and controls

22 lines (12 loc) · 1.1 KB

JMSRequestReplyNonPersistent

What condition does this detect?

JMS Request/Reply shoud use NON-PERSISTENT messages

This is a Process rule - the rule will test each process of the application

Why is this condition important?

When you have a Request/Reply activity using JMS this is meant for an online-synchronous communication, that means that the option to persist the message in the EMS is not relevant because it is expected to get a reply at this specific moment, so if the receiver goes down and continue to process later the message will be nobody to answer to. So there is no real advatange of persisting the message in this configuration but we're losing performance as part of it.

How to fix it?

Review the configuration of your JMS Request/Reply activities to mark it as NON_PERSISTENT in the Advanced Configuration

How do I use this rule?

The rule is enabled by default. To disable it if unwanted, clone the default "BW6 Quality Profile" quality profile and then disable the rule.


< Return to Rules list | << Return to main README file