XCOM listeners won't start
search cancel

XCOM listeners won't start

book

Article ID: 136053

calendar_today

Updated On:

Products

XCOM Data Transport XCOM Data Transport - Windows XCOM - SUPPORT

Issue/Introduction

Copyright (c) 2012 CA.  All rights reserved.

xcomqm working with shared memory -- 000026

xcomqm: CA XCOM Data Transport r11.6 18040 SP01 64bit for Windows Family (CPIC &

 TCP/IP)


error:

We are unable to Xcom files and are experiencing the Socket closed errors again.

 

 

XCOMM0811I STARTING SECURE TCP/IP CONNECTION TO PORT=08045, IP=

XCOMM0813I SECURE TCP/IP CONNECTION REQUESTED WITH DEST=**NONE**, PORT=,

            IP=

XCOMM1510E System SSL Function gsk_secure_socket_init: RC = 420: Reason = Socket  closed

            by remote partner

XCOMM0093E ERROR ACTIVATING SESSION - SESSION NOT ESTABLISHED

XCOMM1168I PLEXQ LISTENER TASK STOPPING

XCOMM0071I XCOMJOB NOW TERMINATING

XCOMM0897I TOTAL ELIGIBLE zIIP TIME = 0 MICROSECONDS

XCOMM0897I TOTAL ACTUAL   zIIP TIME = 0 MICROSECONDS


In the xcom.log from the Windows side you can find message: XCOMN1004E CA XCOM TCP/IPV4 listener failed to start on port 8044.

Environment

Release : 11.6

Component : CA XCOM Data Transport for Windows

Resolution

Client had to reboot their server based on the following:


I had the user capture an xcomd trace and after reviewing the service trace provided I had them reboot the server:


 XCOMd : LOGGED >>> 2019/08/07 00:30:54 PRG=xcomd PID=14908; XCOMN0088I The XCOMD CA XCOM Data Transport Scheduler Service started, Version r11.6 18040 S

XCOMd <cont:> P01 64bit for Windows Family (CPIC & TCP/IP).;

XCOMd service 404: InitService routine

XCOMd service 591: Event CAXCOMTERMINATIONEVENT already exists. Resetting event state.

XCOMd service 623: Event CAXCOMSUSPENDEVENT already exists. Resetting event state.

XCOMd service 655: Event CAXCOMRESUMEEVENT already exists. Resetting event state.

XCOMd service 1176: PostServiceInit routine

Additional Information

I had the user capture an xcomd trace and reviewed the service trace provided and noticed the following:


 XCOMd : LOGGED >>> 2019/08/07 00:30:54 PRG=xcomd PID=14908; XCOMN0088I The XCOMD CA XCOM Data Transport Scheduler Service started, Version r11.6 18040 S

XCOMd <cont:> P01 64bit for Windows Family (CPIC & TCP/IP).;

XCOMd service 404: InitService routine

XCOMd service 591: Event CAXCOMTERMINATIONEVENT already exists. Resetting event state.

XCOMd service 623: Event CAXCOMSUSPENDEVENT already exists. Resetting event state.

XCOMd service 655: Event CAXCOMRESUMEEVENT already exists. Resetting event state.

XCOMd service 1176: PostServiceInit routine


 Taking an xcomd trace for us to to review:


- Go to the GUI Global Parameters, Trace section, set the trace level to 10.

- In that same section, please turn on the trace for each Component

- Click Update button after selecting the Turn On radio button for each component.

- Stop xcomd

- Go to the C prompt and change directory to %XCOM_HOME% and issue command: card3.bat on

- Start xcomd

- reproduce the problem by starting a remote transfer

- Stop xcomd

- From C prompt issue command: card3.bat off

- Go to the %xcom_home%\trace directory and send us the traces.