Problem with "REMOTE TRACER" in one of my Environments...
In UAT "Remote Tracer" functionality works fine... in DEV "Remote Tracer" window loads but the list of sessions is empty...
Where should I start to Troubleshoot this?
Which table in RULES or DATA does the User/Operator Session information live?
***Edit*** in both environments:
Class Code-Pega-Requestor is mapped to table DATA.pr_other in database PegaDATA.
amazon.com
US
I went to check if the problem still existed ***PRIOR*** to attempting restart, and also to see which node(#29) I was on... the problem has RESOLVED on its OWN... to the best of my knowledge the DEV server was not bounced in the interim.
ls -la /jboss/jboss-eap-6.3/standalone/log/*bounce*
-rw-r--r-- 1 athenapi amazon 0 Sep 12 12:00 /jboss/jboss-eap-6.3/standalone/log/bounceflagfile
Thanks for the response
amazon.com
US
Turns out the DEV server *WAS* bounced in the interim (manually by one of our Developers)... our bounceflagfile only gets touched during the weekly cron-job auto-bounce and not when bounced manually. we are in the process of updating the manual bounce script to match the cron-job bounce script so that next time we can know the exact timestamp of the last bounce... Any idea about why an App Server bounce should help fix the remote tracer issue though? Bouncing is not something we want to do with any regularity in our higher environments.