igsmux_mt consumes high amount of CPU

[Former Member]

Hi experts

IGS is configured on 2 ports 40101 and 40102 hence 2 igspw_mt process

now there are 2 igsmux_mt process

1 is consuming around 60% of CPU

Name PID CPU% PgSp Owner ServerV3 0 "h" for help

igsmux_m 557252 61.5 11.9 ap5adm ClientV3 0 "q" to quit

java 446516 8.9 59.7 root

plaixlps161:ap5adm 6> ps -ef|grep -i igsmux

ap5adm 557252 806988 480 Sep 12 - 14461:03 /usr/sap/AP5/SYS/exe/run/igsmux_mt -mode=profile -restartcount=0 pf=/usr/sap/AP5/SYS/profile/AP5_D01_plsapap501

ap5adm 590052 1306756 0 09:43:37 pts/1 0:00 grep -i igsmux

ap5adm 610450 393276 0 Sep 12 - 2:45 /usr/sap/AP5/SYS/exe/run/igsmux_mt -mode=profile -restartcount=0 pf=/usr/sap/AP5/SYS/profile/AP5_D01_plsapap501

As there are 2 port watcher process der r 2 igsmux_mt process rt so if i kill 1 the high consuming process it will be restarted

is it ok if i kill it?

any idea to troubleshoot why this is consuming high amount of CPU?

Also when i test connection it shows IGS could not be reached

Awaiting reply

Regards

Ameya

Edited by: Ameya Joshi on Sep 16, 2009 10:03 AM

Edited by: Ameya Joshi on Sep 16, 2009 10:09 AM

[JPReyes]

I'll be very carefull if you decide to kill it... also i think you should check igswd_mt because it may need to be killed/restarted too..

Read,

Theres a discussion there that might shed some light...

Regards

Juan

[Former Member]

Thanks Juan

I already read that thread

In it is mentioned igswd_mt i.e watchdog thread automatically restarts the port watcher process igspw_mt rt

Also 1 more thing

in transaction SIGS , in the adiministration menu there are no incoming calls i mean the calls graph is at 0

now the mux process listens the call from listener and forwards it to port watcher rt

now as no calls are the mux should not be active rt?

Also when i test the chart engine it shows IGS not reached

Awaiting your reply

[JPReyes]

now as no calls are the mux should not be active rt?

Not sure about that.... not really an expert in IGS, but If its taking that amount of resources and not calls are registered... I would tend to think that a kill/restart should not be an issue.

Regards

Juan