Connection Conversation Manager service in Cisco Unity Serviceability

Unanswered Question

Hi,

When doing some configuration changes , the administrator is asked to :

"Restart the Connection Conversation Manager service in Cisco Unity Serviceability for these changes to take effect". However, we can't find this service in the control center !!!

anu suggestions? I just restarted the whole UC server and it worked.

best regards,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Jaime Valencia Wed, 02/25/2009 - 17:42

if this is a CUCMBE u did looked in the CUC serviceability and not in CUCM serviceability... right??????

the service is just sitting there in CUC:

Control Center - Feature Services ->

Connection Conversation Manager

pretty hard to miss

HTH

java

if this helps, please rate

fahad ck Thu, 08/18/2016 - 01:04

Hi,

Is that possible to restart the "Connection Conversation Manager" service via CUC CLI ?

Cisco Unity connection : Active version: 11.0.1.21900-11

There were an issue that the CUC pub GUI cannot be accessed its giving 'HTTPS 404 error'

while checking the services via CLI it found Tomcat service down, it start running after reboot the tomcat service via CLI. But still PUB (GUI / RTMT) cannot be accessible

And there were no issue with Sub(one PUB & one SUB) sub is accessible

Current issue:

1. CUC Pub cannot be accessible 

2. Voice mail cannot be retrieved

Early response would be appreciated!

Note: attached the Tomcat log from Pub

Attachment: 
fahad ck Thu, 08/18/2016 - 01:10

After the Tomcat restart following error received : : test - tomcat_memory : Failed - Tomcat's memory usage is unusually high.

i hope this can be neglected.

seems to be a bug: CSCtj50884

-----------------------------------------------------------------------------------------------------------------------

Found the following from the logs

JavaThread "localhost-startStop-2" daemon [_thread_in_native, id=14307, stack(0x87b7b000,0x87bcc000)]

--------------------------------------------------------------------------------------------------------------------

A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0045eed5, pid=1298, tid=2275924848
#
# JRE version: Java(TM) SE Runtime Environment (7.0_85-b15) (build 1.7.0_85-b15)
# Java VM: Java HotSpot(TM) Server VM (24.85-b06 mixed mode linux-x86 )
# Problematic frame:
# C  [libc.so.6+0x60ed5]  fgets+0x35
#
# Core dump written. Default location: //core or core.1298
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  T H R E A D  ---------------

Current thread (0x0b2dd400):  JavaThread "localhost-startStop-2" daemon [_thread_in_native, id=5526, stack(0x87a2d000,0x87a7e000)]

===================================================================

jvm_args: -Djava.library.path=/lib:/opt/cisco/connection/lib:/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib:/opt/cisco/connection/lib:/usr/local/Nuance/Recognizer_Service/amd64/lib:/usr/local/Nuance/OAM/x86/lib:/usr/local/Nuance/Common/x86/lib:/usr/local/Nuance/Common/amd64/lib:/usr/local/platform/lib:/usr/local/Nuance/Recognizer/lib -XX:+UseParallelGC -XX:GCTimeRatio=10 -XX:ErrorFile=/usr/local/thirdparty/jakarta-tomcat/logs/diagnostic-info.jvm-crash.%p.tomcat.txt -Dsun.zip.disableMemoryMapping=true -XX:OnOutOfMemoryError=/home/tomcat/tomcat_diagnostics.sh -XX:OnError=/home/tomcat/tomcat_diagnostics.sh -Dnet.sf.ehcache.skipUpdateCheck=true -XX:-UseSplitVerifier -Djavax.net.ssl.trustStore=/usr/local/platform/.security/tomcat/trust-certs/tomcat-trust.keystore -Djavax.net.ssl.trustStorePassword=OqlcSyEJfpeGF1EF -Djavax.net.ssl.trustStoreType=PKCS12 -Djavax.net.ssl.keyStore=/usr/local/platform/.security/tomcat/certs/tomcat.keystore -Djavax.net.ssl.keyStorePassword=UYvv3cUY782qoNbD -Djavax.net.ssl.keyStoreType=PKCS12 -DamKeyGenDescriptor.provider=JsafeJCE -DamCryptoDescriptor.provider=JsafeJCE -DamRandomGenProvider=JsafeJCE -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/usr/local/thirdparty/jakarta-tomcat/conf/logging.properties -Xmx1216m -Xms256m -XX:MaxPermSize=448m -Djava.endorsed.dirs=/usr/local/thirdparty/jakarta-tomcat/endorsed -Djava.security.policy==/usr/local/thirdparty/jakarta-tomcat/conf/catalina.policy -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp -Dcommons.daemon.process.id=7258 -Dcommons.daemon.process.parent=7257 -Dcommons.daemon.version=1.0.7 abort

Nordyne01 Wed, 10/28/2015 - 06:34

I had the same problem at first.  You need to make sure that you are under the Cisco Unity Connection Serviceability instead of just Cisco Unified Servicibility in order to restart this service.

nibin_joseph Tue, 04/26/2016 - 12:04

I had an issue reported by the users organisation wide that they are not able to access voicemail and send voicemail.

The fix was: restarted 2 services "Connection Conversation Manager" & "Connection Mixer". Once these services are restarted, wait for a couple of minutes and check the functionality of the voicemail by sending and accessing the same.

You can find both these services in :

Cisco Unity Connection Web Page(Version 8.6.2.22900-9) >  Cisco Unity Connection Serviceability > Tools > Service Management > Critical Services.

Note: Restart(Stop & Start) the services one after the other (Wait for the fisrt one to come up and go for the next service)

jzangmeister Fri, 04/29/2016 - 10:50

We had a similar issue and it seems to reoccur after connection conversation manager has been running for a long period of time.  This latest occurrence was after the connection manager service was up for 2301 hours.  Access to voicemail is sporadic when the issue occurs in our environment.  Most of the time users can access voicemail, but every so often a user cannot.  Restarting the connection conversation manager service on each server resolves the problem.  FWIW, we're running CUC and CUCM version 10.5(2)SU2 which I thought was a version that resolved this bug.

Actions

This Discussion