TMS for MQ Series Fails To Boot Up With Error : "LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_INVAL" (Doc ID 1499121.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version 10.3.0 and later
Information in this document applies to any platform.

Symptoms

 

Cannot boot TMS for MQ Series. When booting it up, following error is reported :


LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_INVAL

 

Find here after a piece of Ulog with Tuxedo traces (atmi+iatmi+xa) enabled while TMS Server (called then MQXA):

 

115140.theBoxName!MQXA.14090344.1.0: 07-24-2012: Tuxedo Version 10.3.0.0, 32-bit
115140.theBoxName!MQXA.14090344.1.0: LIBTUX_CAT:262: INFO: Standard main starting
115140.theBoxName!MQXA.14090344.1.0: TRACE:ia:  { tpsvrinit(12, "MQXA -g 4 -i 30001 -u theBoxName -U /home/product/mqtest/LOG/ULOG -m 0 -A")
115140.theBoxName!MQXA.14090344.1.0: TRACE:ia:    { tpopen()
115140.theBoxName!MQXA.14090344.1.0: TRACE:xa:      { xa_open(0x2001cfc4, 0, 0x0)
115140.theBoxName!MQXA.14090344.1.0: TRACE:xa:      } xa_open = -5
115140.theBoxName!MQXA.14090344.1.0: LIBTUX_CAT:466: ERROR: tpopen TPERMERR xa_open returned XAER_INVAL
115140.theBoxName!MQXA.14090344.1.0: TRACE:ia:    } tpopen = -1 [tperrno TPERMERR]
115140.theBoxName!MQXA.14090344.1.0: TRACE:ia:  } tpsvrinit = -1 [tperrno TPERMERR]
115140.theBoxName!MQXA.14090344.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
115140.theBoxName!MQXA.14090344.1.0: LIBTUX_CAT:300: ERROR: _tlog_open: _gp_tblopen: UNIX sys call error - 2
115140.theBoxName!tmboot.24051914.1.-2: CMDTUX_CAT:825: ERROR: Process MQXA at testbox failed with /T tperrno (TPERMERR - resource manager error)

 

 To check how the TMS for WebSphere MQ Series has been settled (piece of Tuxedo configuration file) :

 

GROUP3
        LMID=testbox GRPNO=4 TMSNAME=MQXA
        OPENINFO="MQSeries_XA_RMI:channel=theMQChannelYuCreatedOnMQSeriesServerSide,AXLIB=/the/full/path/to/reach/the/libtux.so,trptype=TCP,conname=theMQSeriesServerHostanme(yourMQSeriesListenerPort),qmname=yourQManager,tpm=TUXEDO"

 

To check which libraries were use to build up theTMS was built up (piece of RM file within udataobj directory available in your TUXDIR ($TUXDIR/udataobj/RM)) :

 

MQSeries_XA_RMI:MQRMIXASwitchDynamic:-L${MQDIR}/lib -lmqmxa -lmqic –lmqmcs

 

Changes

 

There is a machine mac-A on which Tuxedo application runs and on which a MQ Series application runs too.

However, Tuxedo must connect to ANOTHER MQ Series application running on a REMOTE machine mac-B.

That is why CHANNEL and CONNAME parameters are required by WebsSphere MQ Series to allow a remote connection from Tuxedo Application available on mac-B to connect to the MQ Series Queue Manager running on mac-A.

 

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms