Here’s what I’ve noticed:
Using Developer, do a “Find Dependents” on the following service: LXKProductSiebelIn.pub:processProduct. This returns 3 results, 1 of them wrong:
---- LXKProductSiebelIn/LXKMachineTypeModelSiebelIn.trigger:subscribeToProductNRT (this doesn’t even exist in the package!!!)
---- LXKProductSiebelIn/LXKProductSiebelIn.triggers:subscribeToProductBatch (correct)
---- LXKProductSiebelIn/LXKProductSiebelIn.triggers:subscribeToProductNRT (correct)
From the “Find Dependents” window, if you try to go to the bad trigger it doesn’t find it.
If you take a look at the broker, you will see the associated broker client queue and will see that it is subscribing and processing documents!!!
The first time I saw this, I reloaded the package and the bad trigger disconnected and everything worked normally.
However, this problem resurfaced after the QA:7000 IS server was cycled
This invalid trigger is invoking the LXKProductSiebelIn.pub:processProduct service causing each Product to be processed twice.
Since this trigger doesn’t show up in developer, it must be on the file system somewhere.
Can you investigate where this invalid trigger is coming from?
Can you please give me a clue in deleting the trigger from the file system