Support Centre

Find articles, help and advice.

 
Welcome, Guest Login

Support Center

BES - Message Channels Failing to start : iss_getsocket() Incorrect call to routine

Last Updated: Jul 04, 2014 12:05PM UTC

Symptoms

Message Channel(s) fail to initialise.
ppState showing Message Channel(s) in 'Failure to Start' status

$PPLOG/POWERpack_Log showing
20130827 10:48:25 POWERpackTrans:(MCNAME) 10:48:25.187099 000000000 Failure: SYNTAX(40)
20130827 10:48:25 POWERpackTrans:(MCNAME) 10:48:25.187430 000000000 Description : Incorrect call to routine
20130827 10:48:25 POWERpackTrans:(MCNAME) 10:48:25.187691 000000000 Source: 2051 s_net.sin_port = iss_getsocket()
20130827 10:48:25 POWERpackTrans:(MCNAME) 10:48:25.187884 000000000 Group() Rule()
20130827 10:48:25 POWERpackTrans:(MCNAME) 10:48:25.190939 000000000 Terminated DB Connection rc=0
20130827 10:48:25 POWERpackTrans:(MCNAME) 10:48:25.191239 000000000 Terminated LEFT Connection rc=0

Cause

The iss_getsocket() routine manages synchronisity through the use of a locking file $PPWORK/iss_GetSocket.lck
In certain conditions this file can be left around and prevent iss_getsocket() from completing causing it to timeout after 10 seconds.

Resolution

Removing the file manually should allow the iss_getsocket() to complete successfully.
Message Channels may need to be restarted if in a failure state : ppStart -n [MCNAME]

Contact Us

desk.com@interlinksoftware.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete