OEBPM plugin feature causes PDSOE to hang after adding an ABL Service (REST) to the project


Article Number000088723
EnvironmentProduct: OpenEdge Developer Studio
Version: OE 11.7
OS: All Windows platforms
Other: 32-bit PDSOE
Question/Problem Description
Adding an ABL Service to a PASOE server project causes the PDSOE process to remain busy for 30 seconds and more.
This happens several times and looks to occur randomly.
While busy, it is not possible to work with PDSOE.
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement NumberDefect PSC00365004
Activating the "UI Responsiveness Monitoring" in the PDSOE, and reviewing the "Error Log" view shows the performance issue to be caused by the "Progress OpenEdge BPM Feature".

The lines of interest in the error log are the following:


Uninstalling the "Progress OpenEdge BPM Feature" resolved the performance issue:

User-added image
Until the issue is fixed use the workaround below.
If not used, uninstall the "Progress OpenEdge BPM Feature" from the Progress Developer Studio
Last Modified Date4/20/2018 3:06 PM

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Was this article helpful?


Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025