Error List

Error List for the ‘WL103-WTC’ Category

BEA-180023 - Commit of xid failed with status xae.

Description:
WTC failed to commit the transaction with status xae.

Cause:
The transaction became a heuristic hazard, or the resource manager encountered an error.

WL103-WTC , , , ,

BEA-180057 - Invalid return challenge.

Description:
The challenge returned by remote Tuxedo domain is not valid.

Cause:
This is caused by an incorrect configuration and mismatched password.

WL103-WTC

BEA-180094 - tBridge failed to initialize JMS targetName queue.

Description:
The tBridge tried to locate and initialize the targetName queue, but an error was returned. The tBridge cannot continue.

Cause:
The JMS targetName queue does not exist or the JMS server is not running on the system.

WL103-WTC , , , , , ,

BEA-180130 - The value number is not a valid number format for TUXEDO GID.

Description:
The configured GID is not in valid number format.

Cause:
The configured TUXEDO GID is not in valid number format.

WL103-WTC

BEA-180173 - Invalid private key for identity alias alias from key store ks, detected by m

Description:
The SSL socket factory failed to get private key from key store.

Cause:
An invalid key store or the private key alias configure does not exist in the key store, or an incorrect private key store passphrase is configured.

WL103-WTC ,

BEA-180000 - Invalid attributes exception trying to create Subcontext: iae

Description:
Invalid attributes exception when trying to create sub-context.

Cause:
An attempt was made to add an attribute set that has been specified incompletely or incorrectly.

WL103-WTC , , ,

BEA-180034 - Error occurred while searching xmlinput for the document root element.

Description:
An error occurred while searching for the document root element in the XML input string.

Cause:
The input XML string was not formatted correctly.

WL103-WTC , , ,

BEA-180068 - Invalid WSRPCRQ type type.

Description:
The type of discriminator is not supported.

Cause:
Client is not talking to a valid handler.

WL103-WTC ,

BEA-180105 - Unable to find a transaction manager. Transaction recovery will not continue.

Description:
While attempting to recover transactions from Tuxedo into WebLogic Server, the system was unable to find the WebLogic Server transaction manager.

Cause:
A transaction manager could not be found.

WL103-WTC , , , ,

BEA-180141 - Message header contains invalid magic number, connection closed.