Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

UCCX don't close sessions

Hi folks

Bare with me and my lack of knowledge on the subject.

We have an UCCX (8.0.2.11004-12) that have some "odd features".

While going through the logs on it i did a bit of debugging as well. One command (show open ports all) gave me a scare.

Since thursday (6 days) the same sessions have been in the state "wait_close". Is this normal for a UCCX not to close its sessions when the clients have sent "fin"?

If it was only a couple of these sessions i wouldnt be worried but there are approx. 460 of them

The reason i was looking is that form time to time the UCCX hanges and have to be rebooted in order to work propperly.

/Tony

7 REPLIES
VIP Super Bronze

UCCX don't close sessions

Are we talking about an ODBC database connection? If yes, then the script *must* close the connection with the DB Release step. Even if the script didn't release things the End step at the end of the script should force the connection closed though.

The only other session I can think of would be the internal contact session that holds variable values and metadata about the call while it passes through the MIVR subsystem. By default this is erased 30 minutes after the call completes (System > Parameters menu). Unless someone has changed it this should not be hanging out indefinitelly. You can also monitor these sessions through Tools > Real Time Monitoring and choosing Sessions from the Java applet menus.

If you meant something other than the above two definitions of a session please clarify.

PS- You should apply the latest service update which is 8.0(2)SU4 and has been out since December 2011. The 8.0 release of CCX had a lot of defects due to the Windows to GNU/Linux migration. IMO it didn't stabilize until 8.5.1(SU4)-ish. I lack a specific defect to defend this advise; it's just my kneejerk reaction to any problem report in that version of CCX.

Please remember to rate helpful responses and identify helpful or correct answers.

New Member

Re: UCCX don't close sessions

Hi

Thanks for the reply

How would i know if its one or the other?

The  Default Session Timeout* has been changed from 30 minutes to 45 minutes, so they should be closed.

A short version:

admin:show open ports all

Executing.. please wait.

COMMAND     PID          USER   FD   TYPE   DEVICE SIZE NODE NAME

FCCServer 16583      uccxuser   29u  IPv4 44499961       TCP 10.33.xxx.18:3001->xxx.30.xxx.26:2670 (CLOSE_WAIT)

FCCServer 16583      uccxuser   30u  IPv4 44466110       TCP 10.33.xxx.18:3001->xxx.33.xxx.70:1574 (CLOSE_WAIT)

FCCServer 16583      uccxuser   31u  IPv4 44471800       TCP 10.33.xxx.18:3001->xxx.30.xxx.23:4035 (CLOSE_WAIT) FCCServer 16583      uccxuser   29u  IPv4 44499961       TCP 10.33.xxx.18:3001->xxx.30.xxx.26:2670 (CLOSE_WAIT)
FCCServer 16583      uccxuser   30u  IPv4 44466110       TCP 10.33.xxx.18:3001->xxx.33.xxx.70:1574 (CLOSE_WAIT)
FCCServer 16583      uccxuser   31u  IPv4 44471800       TCP 10.33.xxx.18:3001->xxx.30.xxx.23:4035 (CLOSE_WAIT)

Some of the IP-adresses have 20+ sessions.

To me this looks like the clients disconnect but the server keeps the sessions open.

/Tony

PS! We have started the prosess of upgrading it from 8.0 on MCS to 8.5 on UCS and VMWare.

Message was edited by: tony loktu

VIP Super Bronze

Re: UCCX don't close sessions

Ok, that's the chat server. I ran a quick search but can't find an obviously-matching defect. If you want a definitive answer on this one, I suspect Cisco TAC is in your future.

New Member

Re: UCCX don't close sessions

Hi

Thanks for your reply

I was hoping TAC wouldn't be the future for this case but if i have to then thats what i'll do.

Thanks

/Tony

New Member

Hi,I am facing exactly the

Hi,

I am facing exactly the same problem as described by tonyloktu. The chat server TCP connections  are  remaining in CLOSE_WAIT state for a long time leading to shortage of ports and hence failure of FCCSERVER service. There is about 2700 TCP connection. And we can see them by typing the command: "show open ports all":

======

FCCServer  1432      uccxuser 1494u  IPv4  83033048       TCP 10.206.0.10:3001->10.31.80.14:57270 (CLOSE_WAIT)
FCCServer  1432      uccxuser 1495u  IPv4  83033070       TCP 10.206.0.10:3001->10.31.40.19:59547 (CLOSE_WAIT)
FCCServer  1432      uccxuser 1497u  IPv4  83033142       TCP 10.206.0.10:3001->10.29.112.161:57001 (CLOSE_WAIT)
FCCServer  1432      uccxuser 1498u  IPv4  83033188       TCP 10.206.0.10:3001->10.31.128.95:58848 (CLOSE_WAIT)
FCCServer  1432      uccxuser 1499u  IPv4  83033221       TCP 10.206.0.10:3001->10.193.255.11:57555 (CLOSE_WAIT)

=======

I opened a TAC case and they suspect a firewall traffic blocking but i'm not sure of this analisys because when sniffing the traffic in the server side I can see the client requests sent by CAD & CSD (Cisco Agent and Supervissor Desktop). I can also see the telnet requests when trying to connect with telnet on some ports.

I found the bug CSCsq34636 on the Cisco bug toolkit. But our UCCX version 8.5.1.11004-25 is in the fixed release.

Can you please tell me if you could resolve your problem?

Is it related to the network or it's just an application bug?

Thanks for your help

Nadjib

New Member

Hi Nadjib We ended up withou

Hi Nadjib

 

We ended up withou any answer, i'm afraid

 

/Tony
 

New Member

Hi tony,Thank you for your

Hi tony,

Thank you for your quick answer.

Have a nice day.

Nadjib

787
Views
4
Helpful
7
Replies
CreatePlease to create content