My Oracle Support Banner

Tuxedo CORBA NO_RESPONSE Exceptions After XA Database Resource Crash and Restart (Doc ID 1284724.1)

Last updated on FEBRUARY 01, 2024

Applies to:

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

Symptoms

Database XA resource crashed and restarted. XA Tuxedo application initially get CORBA INVALID_TRANSACTION exceptions and afterwards start getting CORBA NO_RESPONSE exceptions.

The application making the CORBA call request appears to complete successfully but never receives a response and eventually will timeout with NO_RESPONSE exceptions.

Transaction failure recovery then brings performance to a crawl where Tuxedo servers appear hung.

Application error logs contained the following CORBA exceptions:

IDL:omg.org/CORBA/NO_RESPONSE
IDL:omg.org/CORBA/INVALID_TRANSACTION


Tuxedo ULOG contained timeout errors.
These occured due to a too high tcp keep alive setting:

LIBTUX_CAT:495: ERROR: tpreturn tpcommit reported TPETIME - timeout occured
CMDTUX_CAT:7027:ERROR: tms_timeout xa_rollback returned XAER_RMERR for group GRP0

These may be seen in addition to the ones above if a service timeout occurs:

CMDTUX_CAT:1836: WARN: Server(1234567) processing terminated with SIGKILL after SVCTIMEOUT
CMDTUX_CAT:4482: ERROR: .SysServiceTimeout: SRVR0, group GRP1, id  <pid#> server killed due to a service time-out

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.