WF_EVENT.raise performance issue

Question

Hi,
We have built with JDeveloper an Extension for Applications.
When we execute the function WF_EVENT.raise ... an event is raised that handles the backoffice execution of all data.
The problem is that the process is waiting on the raise object as long as the backoffice program is running. This means that the screen keeps locked as long as the backoffice process is bussy. We just wanted to use events to disconnect the front application and the backoffice process. The event has a subscription that specifies a workflow to be launched.
Does somebody has an valid explanation for this ? Why does the raise event stays locked so long ? Even when I separate the code into an pl/sql block it takes 60 seconds to launch the event.
PL/SQL block used :
declare
l_event_name VARCHAR2(50) := 'oracle.apps.xxint.cp.startup';
l_document_id VARCHAR2(250):= '20CD413C17573E54E04400005A998170';
l_user VARCHAR2(100);
l_retcode NUMBER;
l_retmsg VARCHAR2(2000);
l_paramlist_t apps.wf_parameter_list_t;
BEGIN
wf_event.addparametertolist('INTERFACENAME', 'XXTN_PO_WORK_ORDER', l_paramlist_t);
wf_event.addparametertolist('ECX_DOCUMENT_ID', l_document_id, l_paramlist_t);
wf_event.addparametertolist('ECX_DOCUMENT_NUMBER', 118356, l_paramlist_t);
wf_event.addparametertolist('ECX_DEBUG_LEVEL', '3', l_paramlist_t);
wf_event.raise(
l_event_Name -- p_event_name in varchar2
,118356 eventKey p_event_key in varchar2
, NULL -- p_event_data in clob default NULL
, l_paramlist_t -- p_parameters in wf_parameter_list_t default NULL
, NULL -- p_send_date in date default NULL
l_paramlist_t.DELETE;
COMMIT;
END;

Answer 1

Hi,
When the event is raised, the event manager will process the synchronous subscriptions in the same database session, then return control to the calling code. Any asynchronous subscriptions will be executed when an agent listener is scheduled to run for the deferred agent.
If the subscription starts or continues a workflow, then this will continue to flow in the same database session (as any Workflow does). The flow continues until it can go no further, and then returns control.
So you have two possible solutions to your problem:
1 - customize the workflow to defer to the background once it has been initiated;
2 - change the subscription to be asynchronous (set the phase to > 100).
Of these two, the second one is the best way forward.
HTH,
Matt
WorkflowFAQ.com - the ONLY independent resource for Oracle Workflow development
Alpha review chapters from my book "Developing With Oracle Workflow" are available via my website http://www.workflowfaq.com
Have you read the blog at http://thoughts.workflowfaq.com ?
WorkflowFAQ support forum: http://forum.workflowfaq.com