JMS Message Throttling Using Work Manager. What is Work Manager?. A Work Manager defines a set of request classes and thread constraints that manage work performed by WebLogic Server instances.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
A Work Manager defines a set of request classes and thread constraints that manage work performed by WebLogic Server instances.
WebLogic Server lets you configure how your application prioritizes the execution of its work based on rules you define
Fair Share Request Class
Response Time Request Class
Min Threads Constraint
Max Threads Constraint
Context Request Class
From the weblogic admin-console navigate to Environment-> Work Managers
Create a New Work Manager
Once the WM is created navigate to that WM and create a constraint for instance “Maximun Thread Constraint” and set the desired thread count.
Work Manager created in admin console can be used while configuring the proxy service as Dispatch policy in JMS Transport Configuration.
Navigate to JMS Connection factory which is referred by the JMS proxy service.
Under the Client tab, set the Maximum Messages per session as “1”.
JMSQueueOSBProxyBusinessServiceBpel Sync Process
In the simulation, Bpel Process would wait for 5 seconds before the respective instance completes.
OSB Proxy Service is disabled and 5 messages are put into the queue.
After putting the messages into queue the proxy service is enabled and the messages are processed in the below pattern.
MSG5 in 20th Second
MSG5 in 20th Second
As per the pattern each message will take 5 seconds to get processed from Queue.
So if the thread constriant has configured as “2”,then for every 5 seconds 2 messages will get processed from the Queue.