Developer Partner Community

  • October 21, 2015

Separating the dispatch policy for OIM Eventhandler MDBs by Peter van Nes

Juergen Kress
PaaS Partner Adoption


In OIM JMS queues are used for storing the reconciliation events. These events are read from the JMS queues by Message Driven Beans (MDB)  for processing. Each type of event is processed by a specific MDB and is stored in a dedicated queue of the OIMJMSModule.

The MaxThreadsConstraint  for the OIMMDBWorkManager sets the maximum number of concurrent threads for MDBs processing reconciliation events. A high number of concurrent threads of a specific MDB, e.g. oimKernelQueueMDB, can therefore allocate all available threads from the OIMMDBWorkManager. Therefore there may be leaving only some or none threads for the other MDB.

This can be avoided by separating the dispatch policies for different MDBs in two steps. First create a dedicated Workmanager and MaxThreadConstraint (MTC) for one or more MDB. Second change the dispatch policy for the MDB to the just created MTC.

In the steps below a WorkManager and MTC will be created. The existing dispatch policy for the oimKernelQueueMDB will be replaced with the created WorkManager. Multiple MDB may share the same dispatch policy. Always keep in mind that adding a new WorkManager as a dispatch policy will increase the total number threads. So if you want to keep the number of total threads unchanged, reduced the Count in MaxThreadsConstraint-1 .

Create WorkManager and MTC
MaxThread Constraint

· Logon to the Weblogic Console

· Select Lock & Edit in ‘Change Center’

· Open Environment > Work Managers in the ‘Domain Structure’

· Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.