Issue

• Users are using a SwitchYard application deployed on multiple FSW 6.0.0 nodes that use a JPA binding to poll new records from a database. In the next step after polling the records from the database the SwitchYard service is supposed to convert the Entity to XML and should send it to a JMS queue (through JCA-JMS Binding) and update the value for a respective database column accordingly once this activity finishes. It works fine in single node environment where the SwitchYard application is only running on single FSW node but, where the application is deployed in multiple FSW nodes it seems that the service running on the other nodes also consumes the same entity and therefore produces duplicate results in the end.
• On Camel JPA component level users have set attribute consumeLockEntity to true as suggested in this KCS [1] , however still the issue persists. Is this consumeLockEntity property supposed to work as expected while used with JPA Binding of SwitchYard as well in case of a distributed environment? Is it a known issue in SwitchYard ?

[1] JPA consumer in clustered FSW 6 environment