Posted: 16 Jan 2018 8:27 EST Last activity: 9 Mar 2018 6:10 EST
Pega is trying to use Control-M agent listener port 7006(BIX) , huge thread dump is happening in System.Out.log file
Hi Team ,
I have a scenario in prod env where the SystemOut.log file size is increasing continuously because of thread dumps .
We have analysed and we found that the Control-M agent listener port 7006(related to bix extraction) is being utilized by pega application , which is causing the Control-M agent to go down . We haven't referred the port 7006 anywhere at the pega end , what could be the probable cause for pega trying to use this port number.
Hi Sudhakar ,
Attaching the Systemout and pega logs . Control M agent is configured in control m application only . Pega version is 7.3.
We have found that 7006/tcp has been configured for error interpretation service and the same port is being used by control M agent . Whene ever there is thread dumps then the jvm process related to error interpretation service is occupying the port 7006 making the control M down .
afs3-errors 7006/tcp # error interpretation service
afs3-errors 7006/udp # error interpretation service
I also want to know what is the use of error interpretation service and when will it be triggered
I analysed the file and can see thread dump happened due to the requestor execution taken more than 120 seconds on loadworktypebyrequestsource activity at step 4.2.2. And didn't see the Contorl M agent causing the issue.