The wM document has described this for adapter load balance as following and will solve your problem. Please note that not all adapters automatically have sharedEventOrdering property in the adapters.cfg file. If not there, you need manually add it into the adapters.cfg file.
Load Balancing Adapters:
Creating adapters on multiple machines, with the exact same name (and the same Client Group) connecting to the same broker, provides load balancing and failover capabilities. If for some reason one of the machines goes down, the other machine still has the adapter running. To achieve parallel processing of events by all the machines one has to ensure that the sharedEventOrdering property in the adapters.cfg file is set to none.
If configured as described above, the events are dispatched between the adapters in a round robin way. This is a very useful feature for implementing true adapter failover by hosting different instances in different machines as it does provide extended multiprocessing for heavy tasks (using sharedEventOrdering None).
Being able to distribute an adapter on different machines and have them run as one logical adapter is handy to guarantee “availability” and performance through multi-processing is a very good feature.
Note : You have to check that “State Sharing” is set to “Enabled” under “Manager/Clients/Sessions/” (that would correspond to “shared true” parameter in adapters.cfg but it doesn’t seem to be modifiable).
Many adapters have this parameter set to true by default.