Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 nikhil kumar (nikhilk7251)
Verizon Data Services
Senior software engineer
Verizon Data Services
IN
nikhilk7251 Member since 2016 61 posts
Verizon Data Services
Posted: Jan 16, 2018
Last activity: Mar 9, 2018
Posted: 16 Jan 2018 8:27 EST
Last activity: 9 Mar 2018 6:10 EST
Closed

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.

To see attachments, please log in.
Data Integration
System Administration

Posted: 7 years ago
Posted: 18 Jan 2018 8:38 EST
Sudhakar Reddy Yaparla (YSudhakarReddy)
JPMorgan Chase & Company

JPMorgan Chase & Company
US

Hi,

Can you please share the log files for analysis, and where is the Control-M agent is configured ?

Application server, data base details pega version as well.

To see attachments, please log in.
Posted: 7 years ago
Posted: 7 Feb 2018 5:18 EST
nikhil kumar (nikhilk7251)
Verizon Data Services
Senior software engineer
Verizon Data Services
IN
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
To see attachments, please log in.
Posted: 6 years ago
Posted: 9 Mar 2018 6:10 EST
Sudhakar Reddy Yaparla (YSudhakarReddy)
JPMorgan Chase & Company

JPMorgan Chase & Company
US

Hi,

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. 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice