MTA Application Locks When Passing Objects Directly To The Search Opcode
(Doc ID 1503842.1)
Last updated on MARCH 06, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.4.0]
Information in this document applies to any platform.
Application created in framework MTA locks after process 1 fetch.
We have found that the last function in framework is: pin_mta_worker_job_done() the pin_mta_worker_exit() is not run.
Steps that are made in app:
1. In init_search prepare flist with dummy poid. Number of results is equal fetch_size from pin.conf. When init_search runs again prepare new flist with the same. Stop prepare after 10 runs of init_search.
2. In worker_opcode call: PCM_OP_TEST_LOOPBACK
3. Log exec of fuctions:
pin_mta_post_worker_init - OK RUN
pin_mta_worker_job_done - OK RUN
pin_mta_worker_exit - NOT RUN
The function pin_mta_worker_exit is not run and Application locks after 2nd run of init search, workers are not processing next jobs
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document