Shared JMS Queues between 2 Application Instances
Let me describe our current setup. We have 2 application instances of SAP Manufacturing Execution 6.1 located in 2 servers (server A and server B). Both instances share the same version of the source codes and both are using a shared database. The purpose of this setup is to make use of a load balancer.
What we have found out is that our JMS Queues (which we use for importing various objects) are getting shared between the two application instances which are supposed to be located in different servers.
Example scenario is below:
1. Shop order is imported into server A.
2. Our custom logic would then place that in a JMS Queue.
3. A custom message driven bean listens to the queue and performs the actual processing.
However, there are instances wherein even if the order was imported into Server A, actual processing happens in server B.
Is this because of the shared database between the 2 instances?
Is there a way to have separate JMS Queues between the 2 application instances?
This was resolved by creating a custom LOCAL Virtual Provider.