Increase thread limit for RPM

Issue:

How to setup work manager to increase the thread limit for RPM.  

I used below steps to configure it for my local instance, that worked..

We will need to create this work manager ahead of time in Weblogic,  perform the steps below and then re-deploy so it gets that modified XML file in updated deployment.

For Retail J2ee app 13.2.x on weblogic,                                                                                                                                                                        

  1. Run XDoclet to generate deployment descriptors if building locally
    Do NOT run XDoclet again or the changes to the deployment descriptors will be overwritten and will need to be redone
  2. Open weblogic-ejb-jar.xml for editing
  3. For each MDB reference add the following entry inside the <weblogic-enterprise-bean> element:

<dispatch-policy>threading_workmanager</dispatch-policy>

The result should look something like this:

<weblogic-enterprise-bean>

    <ejb-name>app_nameTaskMDB</ejb-name>

    <message-driven-descriptor>

        <destination-jndi-name>jms/Queue_name</destination-jndi-name>

    </message-driven-descriptor>

    <reference-descriptor>

    </reference-descriptor>

    <dispatch-policy>threading_workmanager</dispatch-policy>

</weblogic-enterprise-bean>

  1. Now open the Weblogic Server Admin Console
  2. Navigate to Environment > Work Managers
  3. Select New, then select 'Maximum Threads Constraint', and click Next
  4. Enter a name for the constraint, set the count to the maximum number of desired threads, and then select Next
  5. Under Servers select the app server that you would like to deploy the constraint to, most likely AdminServer, and select Finish
  6. Now, select New, then select 'Minimum Threads Constraint', and click Next
  7. Enter a name for the constraint, set the count to the minimum number of desired threads, and then select Next
  8. Under Servers select the app server that you would like to deploy the constraint to, most likely AdminServer, and select Finish
  9. Now, select New, then select 'Work Manager', and click Next
  10. The name of the work manager should match the one given for the dispatch-policy element in weblogic-ejb-jar.xml ('threading_workmanager' in the example above)
  11. Under Servers select the app server that you would like to deploy the constraint to, most likely AdminServer, and select Finish
  12. From the list select the new Work Manager
  13. Open the drop down menu for 'Minimum Threads Constraint' and select the minimum threads constraint that was just created in the previous steps
  14. Open the drop down menu for 'Maximum Threads Constraint' and select the maximum threads constraint that was just created in the previous steps
  15. Select Save

Restart the server, rebuild and redeploy the application

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

This blog is our place to ramble about technical topics that we (and hopefully you) think are interesting while installing Oracle Retail Products.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today