R12.1.3: Internal Concurrent Manager does not manage processes correctly after CPU patches applied

Regardless if you have already applied the CPU patch which causes this or not, you need to prepare for the potential to encounter the "Concurrent Managers Are Not Going Down Properly After Appling Patch 16735285 in R12(12.1.3)" issue reported in MOS document ID 2063862.1 after any change so make sure you add this to your test cases immediately!  You could also have another take away by finding out more about the Concurrent Managers by looking up the package FND_CONC_RAC_UTILS reported in the error message to see if there are other procedures that maybe you could utilize in the future!!

Concurrent Manager: Killed/Giving Up

Troubleshooting a situation with our Concurrent Manager on 11.5.10.2 I ran into a problem I have never seen before.  Running similar to researching an issue like a previous post, I was trying to find out why the OS thread for the Internal Manager was taking CPU cycles and when I looked in the Administer Concurrent Manager form I can see that the Internal Manager had been up for months.  First thing I try is to Verify it, but that and every other step I was taking would end up just Pending so I started digging for why we needed the CM to be bounced.

In the Internal Manager log I could see the following entry:

Process monitor session ended  : <date>

Process monitor session started : <date>

(the above were repeated hundreds of times)

Killed
The SID_processID@SID internal concurrent manager has terminated with status 137 - giving up.

What is interesting, is that the <date> above was many months prior to when I tried to give the Internal Manager the Verify command.  What does this mean?  Well we have another opportunity to proactively monitor our log files for this known issue!