MTA Application Locks When Passing Objects Directly To The Search Opcode

(Doc ID 1503842.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Information in this document applies to any platform.
*** Checked for relevance on 05-27-2014 ***


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 procesing next jobs


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms