I encountered this today in Policy Manager:
Before I go and restart anything, I wanted to toss this out to the group to see if anyone has a sane fix.
This happens when a service debugger for a policy(in this case /OAMServices) is already running on a different machine and you try to debug the same policy. If that is not the case, killing the java process and restarting policy manger should do the trick for you.
I believe that running the Service Debugger for a published service generates an audit message, as well. You should be able to see who was running the debugger at that time--just in case someone else was logged in and actually using it
Retrieving data ...