I am in process of converting legacy Message Broker API code, Activesw - which was bought by WebMethods - which was bought by SoftwareAG, to JMS. We are many generations behind. We will still use the WebMethod broker and have installed JMS adapter which will allow us the use JMS and spring-frame work container.
Anyways I have a message type (A) with concurrency set to 3 and number of thread worker set to 3. I am using Default Message Container. The java code, observer, that subscribes to the message type (A) is not thread safe. In fact java code is stateful. Keep in mind, this is legacy code and very expensive to rewrite. I need to be able to process 3 messages at a time in parallel.
The problem is that the thread worker share the DB connection when processing messages parallel , thus corrupt the data.
1) Is there a way to tell the thread not to share resources among thread workers.
2) Is there a way to tell the thread worker to complete the message processing in entirety before processing next one in queue.
Any help will be greatly appreciated,