Until LiveCycle ES2, the JMS was used in LiveCycle to manage processes and tasks. This has led to some of the odd and painful incidents..

LiveCycle ES2 uses Workmanager API (JSR-237) which will definitely make the LiveCycle community happier..

The Livecycle server can also have the java parameters to control the workmanager throttling options.
Here are the option that you can tweak as java parameters:

  • adobe.work-manager.queue-refill-interval
  • adobe.workmanager.debug-mode-enabled
  • adobe.workmanager.memory-control.enabled
  • adobe.workmanager.memory-control.high-limit
  • adobe.workmanager.memory-control.low-limit

More details at – http://kb2.adobe.com/cps/825/cpsid_82568/attachments/WorkManagerThrottle.pdf

—-
Original article at http://blog.pandyaparth.com/2010/04/livecycle-es2-removes-jms-and-uses-workmanager-api-yay/.