iProcess Engine can't restart if RPC/TCP ports are left open

iProcess Engine can't restart if RPC/TCP ports are left open

book

Article ID: KB0084032

calendar_today

Updated On:

Products Versions
TIBCO iProcess Engine (Oracle) 11.4.1

Description

Problems during a shutdown of iProcess Engine can leave some RPC or TCP ports blocked and open. This can lead to issues during the restart where some of the processes cannot register with the RPCBIND process. This can lead to problems starting the RPC_TCP_LI, WQSRPC or WISRPC processes and you may see the following entries in the swrpcsvr01.log when debugging to find the cause.

[T=00001]161004224729.062824:T004: swrpc_get_port_callback () : Attempting to register RPC Listener server on 391875/56003
[T=00001]161004224529.054478:T001: check_rpc_prog (tcp) :     'sw_register_rpcpport_server: RPC: Port mapper failure - RPC: Timed out
[T=00001]161004224729.063249:x004: svc_tcp.c 214 sw_bindresvport(): bind() failed(-1). errno=22, sd=76, IP=

Issue/Introduction

iProcess Engine may leave ports open when a graceful shutdown fails. This article provide some information on how that situation can be resolved.

Environment

iProcess Engine (Oracle) for AIX

Resolution

No specific information is available on why the ports are not closed during the iPE shutdown, but there are some actions that can be taken when trying to resolve the problem.
  1. Check that the rpcbind or RPC portmapper process is running.
  2. Make sure that all iProcess processes were shutdown after the swstop and swstop -p using "ps -ef | grep $SWDIR".  You may need to "kill" any processes that remain.
  3. Use the following command to verify no RPC port left open (you can use rpcinfo -d to clear them):
    rpcinfo –p | grep 10737                   (iProcess has predefined RPC ports for WIS/WQS that start with 10737). 
    rpcinfo -p | grep 391875                  (check your swdefs file for the RCP port used)                      

Additional Information

iPE, rpcinfo, rpcbind