bea.com | products | dev2dev | support | askBEA
 Download Docs  Site Map  Glossary 
Search

WTC Subsystem Messages

The WTC 1.0 catalog contains messages in the range BEA180000 - BEA189999. Messages in this catalog are part of the weblogic.wtc Internationalization package and the weblogic.i18n Localization package.

BEA-180000

Info: Start parsing the configuration MBean info.

Description

WTC will now be initialized according to the MBean config info entered.

Cause

All other initialization has completed and now this method is ready to begin reading its own configuration info.

Action

No action required.

BEA-180001

Info: WTC finished parsing the configuration MBean info.

Description

WTC finished initialization according to the MBean config info entered.

Cause

All WTC configuration MBeans were parsed without any problems.

Action

No action required.

BEA-180002

Error: Invalid attributes exception: 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.

Action

Internal error. Contact BEA Customer Support.

BEA-180003

Error: Naming exception error: ne

Description

Naming exception while creating sub-context.

Cause

Specified name can not be resolved.

Action

Internal error. Contact BEA Customer Support.

BEA-180004

Error: Name already bound error: nabe

Description

Failed to bind Tuxedo or Corba connection factory to JNDI.

Cause

The name used by the Tuxedo connection factory or Tuxedo CORBA connection factory already bonded to another object.

Action

Do not use the same name as Tuxedo or Tuxedo CORBA connection factory.

BEA-180005

Error: Invalid attributes exception error: iae

Description

Invalid attributes exception occurred when trying to create Tuxedo or Tuxedo CORBA connection factroy.

Cause

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

Action

Internal error. Contact BEA Customer Support.

BEA-180006

Error: Naming excepton error: nae

Description

Naming exception occurred while binding Tuxedo and Tuxedo CORBA connection factory to the JNDI.

Cause

Specified name can not be resolved.

Action

Internal error. Contact BEA Customer Support.

BEA-180007

Error: Unable to register the resource with transaction manager: se

Description

Unable to register the resource with transaction manager.

Cause

WTC is not running with server transaction manager.

Action

Contact BEA Customer Support.

BEA-180008

Error: A transaction identifier exists for a non-existing domain accesspoint.

Description

A transaction identifier exists for a non-existing remote Tuxedo domain.

Cause

The remote Tuxedo domain involved in the transaction is no longer in the WTC configuration.

Action

Manually correct the transaction or temporarily add the remote Tuxedo domain back to the configuration and wait for the transaction to complete, if the removal of the remote Tuxedo domain is intentional. Otherwise, add the Tuxedo domain back to the configuration.

BEA-180009

Error: Could not complete the execution for MBean named: mbname

Description

The processing of the MBean configuration could not complete.

Cause

The definition contains some input information that is not consistent with the usage model.

Action

Check the MBean definition to see if the indiviual attributes are consistent with the rest of the MBean definitions.

BEA-180010

Error: Could not create a TDMLocalTDomain exceptioninfo

Description

The TDMLocalTDomain constructor failed to create a new instance.

Cause

The AccessPoint attribute definition for the WTCLocalTuxDom MBean is invalid.

Action

Check the AccessPoint attribute of the WTCLocalTuxDom MBean.

BEA-180011

Error: Could not create a TDMRemoteTDomain exceptioninfo.

Description

The TDMRemoteTDomain constructor failed to create a new instance.

Cause

The AccessPoint attribute definition for the WTCRemoteTuxDom MBean is invalid.

Action

Check the AccessPoint attribute of the WTCRemoteTuxDom MBean.

BEA-180012

Error: The LocalTDomain ltdname is not known.

Description

Can not continue setting up the TDMRemote object because the LocalTDomain is not valid.

Cause

The LocalAccessPoint attribute for the WTCRemoteTuxDom MBean is not a valid name for a LocalTDomain.

Action

Verify the WTCRemoteTuxDom MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180013

Error: The LocalTDomain ltdname is not known.

Description

Can not continue setting up the TDMExport object because the LocalTDomain is not valid.

Cause

The LocalAccessPoint attribute for the WTCExport MBean is not a valid name for a LocalTDomain.

Action

Verify the WTCExport MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180014

Error: Could not create a TDMExport exceptioninfo.

Description

The TDMExport constructor failed to create a new instance.

Cause

The ResourceName attribute definition for the WTCExport MBean is invalid or the LocalTDomain is not usable.

Action

Check the ResourceName attribute of the WTCExport MBean.

BEA-180015

Error: The LocalTDomain ltdname is not known.

Description

Can not continue setting up the TDMImport object because the LocalTDomain is not valid.

Cause

The LocalAccessPoint attribute for the WTCImport MBean is not a valid name for a LocalTDomain.

Action

Confirm the WTCImport MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180016

Error: The RemoteTDomain rtdname is not known.

Description

Can not continue setting up the TDMImport object because the RemoteTDomain is not valid.

Cause

The RemoteAccessPointList attribute for the WTCImport MBean does not contain a valid name for a RemoteTDomain.

Action

Verify that the WTCImport MBean definition has valid names, a comma separated list, defined in the RemoteAccessPointList Attribute.

BEA-180017

Error: Could not create a TDMImport exceptioninfo.

Description

The TDMImport constructor failed to create a new instance.

Cause

The ResourceName attribute definition for the WTCImport MBean is invalid. The LocalTDomain or the RemoteTDomains are not usable.

Action

Check the ResourceName attribute of the WTCImport MBean.

BEA-180018

Error: Missing passwordType Password or PasswordIV information.

Description

Cause

The Password or PasswordIV attribute is not set.

Action

Verify that the Password and PasswordIV attributes are valid.

BEA-180019

Error: The LocalTDomain ltdname is not known.

Description

Can not continue setting up the TDMPasswd object because the LocalTDomain is not valid.

Cause

The LocalAccessPoint attribute for the WTCPassword MBean is not a valid name for a LocalTDomain.

Action

Verify that the WTCPassword MBean definition has a valid name for the LocalAccessPoint Attribute.

BEA-180020

Error: The RemoteTDomain rtdname is not known.

Description

Can not continue setting up the TDMImport object because the RemoteTDomain is not valid.

Cause

The RemoteAccessPoint attribute for the WTCPassword MBean is not a valid name for a RemoteTDomain.

Action

Verify that the WTCPassword MBean definition has a valid name for the RemoteAccessPoint Attribute.

BEA-180021

Error: Could not create a TDMPasswd exceptioninfo.

Description

The TDMPasswd constructor failed to create a new instance.

Cause

The LocalTDomain or the RemoteTDomain is not usable.

Action

Check the LocalAccessPoint and RemoteAccessPoint attributes of the WTCPassword MBean.

BEA-180022

Error: Could not set up thefield table information for TDMResources: exceptioninfo.

Description

An unsuccessfule attempt was made to set up a FldTbls array using the WTCResources MBean.

Cause

The fully qualified name for any field table may be incorrect or it can not be found.

Action

Check the FldTblClass definitions of the WTCResources MBean and verify that the fully qualified name given is correct, that it is consistent with the current CLASSPATH usage, and that the system is able to access it.

BEA-180023

Error: 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.

Action

Correct the transaction manually if it became a heuristic hazard, or correct the resource manager problem.

BEA-180024

Error: Unable to reply to unknown transaction with exception caught: tpe.

Description

Failed to send a reply to remote Tuxedo domain for a transaction that WTC no longer knows about.

Cause

The connection to the remote Tuxedo domain already terminated, or an IOException occurred while writing to the network.

Action

If the TPException is TPEPROTO, then try to reboot the remote Tuxedo domain. If the TPException is TPESYSTEM, then check the network connection.

BEA-180025

Error: Unknown field type requested fieldtype.

Description

The field type being used is not one that is defined in the TypedFML Class.

Cause

TypedFML32 data is possibly being used instead of TypedFML.

Action

Verify the type of input data.

BEA-180026

Error: While trying to use FML data, caught this Ferror exception: exceptioninfo

Description

While trying to use FML data, caught this Ferror exception: exceptioninfo

Cause

The data was not created correctly.

Action

Verify the data passed into this method.

BEA-180027

Error: While trying to use FML data, caught an Unknown exception: exceptioninfo

Description

While trying to use FML data, caught an Unknown exception: exceptioninfo

Cause

The data was not created correctly.

Action

Verify the data passed into this method.

BEA-180028

Error: Unknown field type requested fieldtype.

Description

The field type being used is not one that is defined in the TypedFML32 Class.

Cause

Possibly TypedFML data is being used instead of TypedFML32.

Action

Verify the type of input data.

BEA-180029

Error: Caught this Ferror exception: exceptioninfo. Additional exception info found: exceptiondetail

Description

Caught an Ferror exception while processing TypedFML32 data.

Cause

The data was not created correctly.

Action

Verify the data passed into this method.

BEA-180030

Error: While trying to use FML32 data, caught an Unknown exception: exceptioninfo

Description

While trying to use FML32 data, caught an Unknown exception: exceptioninfo

Cause

The data was not created correctly.

Action

Verify the data passed into this method.

BEA-180031

Error: Xml argument is null.

Description

Xml argument is null.

Cause

Did not initialize argument passed in.

Action

Check the xml argument passed in.

BEA-180032

Error: The FldTbl[] input argument is null or an empty array.

Description

The FldTbl[] input argument is null or an empty array.

Cause

Did not initialize argument passed in.

Action

Check the FldTbl[] argument passed in.

BEA-180033

Error: TypedFML argument is null.

Description

TypedFML argument is null.

Cause

Did not initialize argument passed in.

Action

Check the TypedFML argument passed in.

BEA-180034

Error: Error occurred while searching xmlinput for the document root element.

Description

An error occured while searching for the document root element in the XML input string.

Cause

The input XML string was not formatted correctly.

Action

Check for other errors listed that should indicate what was unacceptable about the XMLb input.

BEA-180035

Error: TypedFML32 argument is null.

Description

TypedFML32 argument is null.

Cause

Did not initialize argument passed in.

Action

Check the TypedFML32 argument passed in.

BEA-180036

Error: XML input xmlinput caused SAX parser exception exceptioninfo

Description

XML input xmlinput caused SAX parser exception exceptioninfo

Cause

The DOM parser did not like the XML string that it received.

Action

Check the SAX exception info returned and the XML string entered.

BEA-180037

Error: XML input xmlinput caused IO exception exceptioninfo.

Description

XML input xmlinput caused IO exception exceptioninfo.

Cause

The XML string was not convertible to an InputSource() class.

Action

Check the IO exception info returned and the XML string entered.

BEA-180038

Error: XML input xmlinput caused an unknown exception exceptioninfo.

Description

XML input xmlinput caused an unknown exception exceptioninfo.

Cause

The XML string was not able to be parsed.

Action

Check the exception info returned and the XML string entered.

BEA-180039

Error: The DOM parser returned a null value for input xmlinput.

Description

The DOM parser returned a null value for input xmlinput.

Cause

The input may not be a valid XML string.

Action

Check the string passed to the parser.

BEA-180040

Error: Could not get a top document element from input xmlinput.

Description

Parser could not return the top element of the document tree that represents the start of the XML input.

Cause

The XML input does not have any elements defined.

Action

Verify that the input string has a proper definition for a root element.

BEA-180041

Error: Could not get a tag name for the root element in XML input xmlinput.

Description

Could not get a tag name for the root element in XML input xmlinput.

Cause

The XML input does not have a tag name for the root element.

Action

Verify that the root element has a proper definition.

BEA-180042

Error: Internal TypedFML data is null.

Description

Internal TypedFML data is null.

Cause

Did not initialize internal data using XMLtoFML() API.

Action

Use XMLtoFML to initialize internal data.

BEA-180043

Error: Xml element name is null.

Description

Xml element name is null.

Cause

The XML element information was not properly defined

Action

Check the XML element definition.

BEA-180044

Error: XML element value is null for the element name xmltagname.

Description

XML element value is null for the element name xmltagname.

Cause

The XML element information was not properly defined.

Action

Check the XML element definition.

BEA-180045

Error: Internal TypedFML32 data is null.

Description

Internal TypedFML32 data is null.

Cause

Did not initialize internal data using XMLtoFML32() API.

Action

Use XMLtoFML32 to initialize internal data.

BEA-180046

Debug:

Description

Uncatalogued debug message. Do not change.

Cause

Debugging. Do not change.

Action

No action required.

BEA-180047

Error: tBridge must have at least one redirect command.

Description

The tBridge must be given at least one redirect command; otherwise it has nothing to do.

Cause

Improper configuration of the tBridge.

Action

User must configure at least one redirect command in the WTC_CONFIG for the tBridge section.

BEA-180048

Error: tBridge cannot find the TuxedoConnectionFactory.

Description

The JNDI lookup for the TuxedoConnectionFactory has failed.

Cause

The WTC has not be properly configured.

Action

Review the WTC documentation and restart the WTC.

BEA-180049

Error: tBridge cannot locate the WLXT option for translation.

Description

The tBridge was told to use the WLXT translator. However, this option could not be located.

Cause

The WLXT package might not be loaded or in the proper CLASSPATH.

Action

Install the WLXT and properly configure the translator option.

BEA-180050

Error: tBridge internal FML/XML conversion failed.

Description

The internal tBridge FML/XML translator has failed to convert the buffer.

Cause

The syntax of the incoming message could not be understood.

Action

Correct the message syntax and retry.

BEA-180051

Warning: Unable to cancel ON_STARTUP connection retry.

Description

This message no longer used.

Cause

This message no longer used.

Action

This message no longer used.

BEA-180052

Error: Unable to cancel ON_STARTUP connection retry due to: exceptioninfo.

Description

Unable to cancel open connection retry object for ON_STARTUP connection policy.

Cause

Unable to delete timer service object for ON_STARTUP connection policy during connection termination.

Action

Contact BEA Customer Support.

BEA-180053

Error: Failure occurred during token creating token_token_type.

Description

An internal error occurred while trying to create security token.

Cause

Internal error.

Action

Contact BEA customer support to report this problem with token type information found in the log message.

BEA-180054

Error: Failure occurred while reading the received Domain security token_token_type.

Description

An internal error occurred while reading the received security token.

Cause

Internal error.

Action

Contact BEA customer support to report this problem with token type information found in the log message.

BEA-180055

Error: Received unexpected token type, error information(token_type, error_type, data)

Description

Received a token that WTC does not expect to receive or that contains incorrect information.

Cause

The cause can be that WTC communicates with a newer version of the TDomain protocol or unknown alien protocol, or a breach of security attempt is being detected.

Action

Verify who is trying to connect to this WTC and determine whether there is a security violation or need to upgrade WTC to newer version.

BEA-180056

Error: atntd(1) crypto error: exceptioninfo

Description

Encountered error during encryption.

Cause

Not enough free memory space to continue, or internal error.

Action

Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact BEA Customer Support.

BEA-180057

Error: 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.

Action

Correct the configuration and the password.

BEA-180058

Error: atntd(3) io error: exceptioninfo

Description

Encountered IO operation error while doing encryption.

Cause

Internal system error.

Action

Contact BEA Customer Support.

BEA-180059

Error: atntd(2) crypto error: exceptioninfo

Description

Encountered error during encryption.

Cause

Not enough free memory space to continue or internal error.

Action

Try to force garbage collection, and remove some services to reduce memory usage. If problem persists, contact BEA Customer Support.

BEA-180060

Error: Invalid type (type) or subtype (subtype) string for hint.

Description

Received an invalid user data buffer type or subtype.

Cause

Unsupported buffer type or subtype.

Action

Correct the application buffer type to use the supported buffer type or subtype.

BEA-180061

Error:

Description

Failed to do post receive processing on the user data.

Cause

It could be memory allocation failure, or the field ID for the FML, FML32 does not exist in the class file.

Action

Check the class file and system memory usage.

BEA-180062

Error: Received a buffer of unknown type: hintindex.

Description

This message no longer used.

Cause

This message no longer used.

Action

This message no longer used.

BEA-180063

Error: Invalid handler address length: length.

Description

The handler address length is not the same as expected.

Cause

The client did not talk to a valid listener.

Action

Check the listener address and correct the configuration.

BEA-180064

Error: Unable to decode WSRPCRQ due to exception: exceptioninfo.

Description

This message no longer used.

Cause

This message no longer used.

Action

This message no longer used.

BEA-180065

Error: Unable to decode WSINIT_RP due to exception: exceptioninfo.

Description

This message no longer used.

Cause

This message no longer used.

Action

This message no longer used.

BEA-180066

Error: Unable to decode initial integer descriminator. Caught exception: exceptioninfo

Description

This message no longer used.

Cause

This message no longer used.

Action

This message no longer used.

BEA-180067

Error: WSRPCRQ descrim descrim is invalid.

Description

Invalid WSRPCRQ discriminator.

Cause

Client is not talking to a valid handler.

Action

Check the configuration and correct the error.

BEA-180068

Error: Invalid WSRPCRQ type type.

Description

The type of discriminator is not supported.

Cause

Client is not talking to a valid handler.

Action

Check the configuration and correct it.

BEA-180069

Error: Unable to read type. Caught exception: exceptioninfo.

Description

Unable to read data in the buffer type type.

Cause

General IO exception.

Action

Please read the exception description to determine the actual cause and act accordingly.

BEA-180070

Warning: TypeFML32 got a pointer of unknown type type. Will replace with null.

Description

TypeFML32 got a pointer of unknown type type. Will replace with null.

Cause

Incorrectly written application with unknown data type.

Action

Correct the problem with the data type in the application.

BEA-180071

Warning: Invalid Typed FML32 field fieldno. Equals null.

Description

Invalid Typed FML32 field fieldno. Equals null.

Cause

Incorrectly constructed embedded FML32 buffer in the FML32 buffer.

Action

Check the source of the embedded FML32 buffer, and correct the problem.

BEA-180072

Debug: +++++ title(arraylength) +++++

Description

Marker to indicate start of debugging for TDumpByte.

Cause

Debugging. Do not change.

Action

No action required.

BEA-180073

Debug: +++++ END +++++

Description

Marker to indicate end of debugging for TDumpByte.

Cause

Debugging. Do not change.

Action

No action required.

BEA-180074

Error: tpinit buffer not received.

Description

tpinit buffer not received.

Cause

The server is likely talking to an invalid handler.

Action

Check the configuration and correct the problem.

BEA-180075

Error: Invalid receive size recvsize.

Description

The received transaction data is smaller than expected.

Cause

Remote Tuxedo Domain Gateway is not valid.

Action

Check the configuraiton of the remote Tuxedo domain and correct the error.

BEA-180076

Error: Unable to format password. Caught exception: exceptioninfo.

Description

Caught IO exception while formating password.

Cause

An I/O error occurred.

Action

Check for system memory usage and see if force garbage collection is possible. If problem persists, contact BEA Customer Support.

BEA-180077

Error: Unable to close domain socket. Caught exception: exceptioninfo.

Description

Caught IO exception while closing the connection to remote Tuxedo domain.

Cause

An I/O error occurred while closing the socket.

Action

Check your network and system environment. If problem persists, contact BEA Customer Support.

BEA-180078

Warning: Dropping OWS_AREPLY on ground.

Description

Could not find the handle for ACALL reply.

Cause

The ACALL request already timed out.

Action

This message is informational only.

BEA-180079

Error: rsession.run read_tfmh failed.

Description

Failed to properly receive message header.

Cause

The recieved message header is not properly formatted or failed to decompress the data.

Action

Check the configuration of the remote Tuxedo domain and correct any problem in the configuration. Make sure you are talking to a supported version of remote Tuxedo domain. Also, check the network for possible network dropping of the packet. If problem persists, contact BEA Customer Support.

BEA-180080

Error: rsession.run tmmsg.ws not provided.

Description

The received message header is missing the required WebLogic Server information.

Cause

Not talking to a valid remote Tuxedo domain.

Action

Check the remote Tuxedo domain configuration and correct the problem.

BEA-180081

Error: Unexpected close on rsession socket. Caught exception: exceptioninfo

Description

Caught I/O exception while processing the message header.

Cause

An I/O error occurred while reading the message header from input stream.

Action

Check system memory usage and force garbage collection. If problem persists, contact BEA Customer Support.

BEA-180082

Error: Unable to close wsh socket. Caught exception: exceptioninfo.

Description

Caught I/O exception and unable to close WSH socket by client.

Cause

An I/O error occurred.

Action

Check the network and system configuration.

BEA-180083

Error: Unknown TCM type received: tcmtype.

Description

Received a TCM with an unsupported buffer type tcmtype.

Cause

WTC is communicating with an unsupported Tuxedo version.

Action

Check the configuration and correct the error.

BEA-180084

Error: Unable to write TCM. Caught exception: exceptioninfo.

Description

Caught I/O exception while writing TCM to output data stream.

Cause

An I/O error occurred.

Action

Check the system memory usage and force garbage collection.

BEA-180085

Error: Unable to send unsolicited acknowlegement. Caught exception: exceptioninfo.

Description

Caught I/O exception while writing an unsolicited acknowledgement to data output staream.

Cause

An I/O error occurred.

Action

Check system memory usage.

BEA-180086

Info: Accepted Connection from remote domain domid.

Description

Connection to remote domain established.

Cause

Connection request was received from a remote domain.

Action

No action required.

BEA-180087

Info: Established a connection to a remote domain domid.

Description

Connection to a remote domain established.

Cause

Initiate the connection request to a remote domain.

Action

No action required.

BEA-180088

Error: Error occurred while building mtype message.

Description

Error encountered during build of outgoing message.

Cause

This is an internal error.

Action

Contact BEA Customer Support.

BEA-180089

Error: Error occurred while decoding mtype message.

Description

Error encountered during decoding of incoming message.

Cause

This is an internal error.

Action

Contact BEA Customer Support.

BEA-180090

Error: Remote domain domid rejected the connection request.

Description

Remote domain detected an authentication failure and rejected the connection request.

Cause

User configuration error.

Action

Check both side configurations to see whether a mismatch exists in the configuration, including the password.

BEA-180091

Error: Rejected remote domain domid connection request.

Description

Local domain detected an authentication failure and rejected the connection request.

Cause

User configuration error.

Action

Check both side configurations to see whether a mismatch exists in configuration, including the password.

BEA-180092

Error: Failed security validation with remote domain domid.

Description

Security validation failed.

Cause

User configuration error, unauthorized access.

Action

Check both side configurations to see if a mismatch exists in the configuration, including password.

BEA-180093

Error: Naming exception occurred during lookup of the admin name: exceptioninfo.

Description

A naming exception occurred during lookup of the admin name: exceptioninfo.

Cause

The specified name can not be resolved.

Action

Contact BEA Customer Support.

BEA-180094

Error: 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.

Action

Correct the JMS problem and restart the WTC tBridge.

BEA-180095

Error: The tBridge could not initialize the JMS sourceName queue.

Description

A failure was reported from JMS during the initialization of the sourceName queue. This fromto thread of tBridge cannot continue.

Cause

The sourceName queue can not exist in JMS or the JMS server may not be started.

Action

Correct the JMS problem and restart the WTC tBridge.

BEA-180096

Error: The tBridge could not initialize the wlsErrorDestination JMS queue.

Description

The tBridge received an error during initialization of the JMS wlsErrorDestination queue. The tBridge will continue, but this could result in the loss of message data.

Cause

The JMS wlsErrorDestination queue may not be properly configured in WebLogic Server.

Action

Correct the JMS problem and restart the WTC tBridge.

BEA-180097

Error: Due to a translation error, tBridge has redirected the message to the wlsErrorDestination.

Description

The tBridge encountered a translation error and has redirected the message to the wlsErrorDestination queue.

Cause

The cause of this error is a translation error detected from/to FML/XML.

Action

Correct the message structure and resend the message.

BEA-180098

Error: The tBridge failed to send the message to wlsErrorDestination.

Description

The tBridge failed to send the message that generated the error to the wlsErrorDestination. The message remains unacknowledged on the JMS input queue.

Cause

The JMS wlsErrorDestination could be full or paused.

Action

Recover the message from the sourceName JMS queue and resend.

BEA-180099

Error: The MinEncryptionBits is greater then MaxEncryptionBits in type domain id.

Description

The configured MinEncryptionBits is greater than MaxEncryptionBits.

Cause

User configuration error.

Action

Modify the BDMCONFIG and use the correct values for Min and Max Encryption Bits.

BEA-180100

Error: Configuration Error: detail

Description

Bad configuration information found.

Cause

User configuration error.

Action

Modify the BDMCONFIG and use the correct values for the corresponding error.

BEA-180101

Error: At least one local domain must be defined.

Description

No local domain is defined in this configuration.

Cause

User configuration error.

Action

Modify the BDMCONFIG and add at least one local domain.

BEA-180102

Error: Duplicated local domain ID ldomid found.

Description

Bad configuration information. Contains two local domains having the same ID.

Cause

User configuration error.

Action

Modify the BDMCONFIG and use the unique ID for the local domain.

BEA-180103

Error: There are two remote domain rdomid with same local domain ldomid.

Description

Bad configuration information found in the BDMCONFIG.

Cause

User configuration error.

Action

Modify the BDMCONFIG and remove the redundent entry or correct the configuration information.

BEA-180104

Error: Unsupported JMS message type.

Description

The tBridge only supportes the JMS TextMessage and BytesMessage. All other types are rejected and not redirected to the error destination.

Cause

The user has sent a JMS Stream or Mapped message type to the tBridge.

Action

Correct the JMS message type and resend.

BEA-180105

Warning: A message has been dropped.

Description

A message has been dropped by the WTC gateway. Other log messages should provide details on the reason the message was dropped.

Cause

The most common cause of this failure is that an unrecongized buffer type has been received by the WTC gateway.

Action

Modify the application to make sure that unknown buffer types are not sent to the WTC gateway.

BEA-180106

Error: 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.

Action

Contact BEA Customer Support.

BEA-180107

Warning: While attempting to recover transactions, the recover method failed.

Description

While attempting to recover transactions, the recover method failed.

Cause

The recover method on the WLS XA Resource threw an exception.

Action

Contact BEA Customer Support.

BEA-180108

Warning: WebLogic Server rollback had a failure: exception.

Description

While attempting to recover transactions, the rollback method failed.

Cause

The rollback method on the WLS XA Resource threw an exception.

Action

Contact BEA Customer Support.

BEA-180109

Error: Internal FML to XML conversion failed.

Description

The message from Tuxedo /Q has been received. However, the translation from FML into XML has failed. The transaction has been rolled back, and the message remains in the Tuxedo queue.

Cause

The FML buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.

Action

Verify that the field tables have been properly transfered as described in the WTC documentation.

BEA-180110

Error: Internal FML32 to XML conversion failed.

Description

The message from Tuxedo /Q has been received. However, the translation from FML32 to XML has failed. The transaction has been rolled back, and the message remains in the Tuxedo queue.

Cause

The FML32 buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.

Action

Verify the field tables have been properly transferred as described in the WTC documentation.

BEA-180111

Error: Internal FML to XML conversion failed.

Description

The message from the Tuxedo service has been received. However, the translation from FML to XML has failed. The original message has been redirected to the designated JMS error queue.

Cause

The FML buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.

Action

Verify the field tables have been properly transferred as described in the WTC documentation.

BEA-180112

Error: Internal FML32 to XML conversion failed.

Description

The message from the Tuxedo service has been received. However, the translation from FML32 to XML has failed. The original message has been redirected to the designated JMS error queue.

Cause

The FML32 buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.

Action

Verify the field tables have been properly transferred as described in the WTC documentation.

BEA-180113

Debug:

Description

The message is for debug tracing.

Cause

The message is for debug tracing.

Action

No action is required.

BEA-180114

Error: Could not set up VIEW information for TDMResources: exceptioninfo.

Description

An unsuccessfuld attempt was made to setup a VIEW table array for the WTCResources MBean.

Cause

The fully qualified name for any VIEW table may be incorrect or it can not be found.

Action

Check the ViewTblClass definitions of the WTCResources MBean and verify that the fully qualified name given is correct, that it is consistent with the current CLASSPATH usage, and that the system is able to access it.

BEA-180115

Error: The tBridge cannot parse the configuration MBeans: exceptionInfo.

Description

The startup configuration for tBridge contained in the WTCtBridgeGlobal and WTCtBridgeRedirect MBeans could not be understood.

Cause

The MBeans for tBridge contain invalid attributes.

Action

Correct the attribute definitions for the tBridge MBeans.

BEA-180116

Error: The field table type specified tbltype is incorrect.

Description

The FldTblClass type used is not one of the valid types, fml16 or fml32, allowed.

Cause

The WTCStartup.getFldTbls() method was called with an invalid argument.

Action

Verify that the Type argument for this is either "fml16" or "fml32".

BEA-180117

Error:

Description

Cause

Specified encoding name is not supported.

Action

Correct the encoding name and restart WebLogic Server.

BEA-180118

Error: Failed to find TPUSR file: fname.

Description

The configured TPUSR file fname does not exist.

Cause

The specified file TPUSR file does not exist.

Action

Correct the configuration by specifying the correct TPUSR file or create it before using it.

BEA-180119

Error:

Description

The configured TPUSR file fname is not a file.

Cause

Incorrect WTC TPUSR file configuration.

Action

Correct the WTC TPUSR file configuration.

BEA-180120

Error: The file fname is not readable.

Description

User does not have permission to read file fname.

Cause

User does not have the read permission to read the configured TPUSR file.

Action

Change the permissions of the TPUSR file.

BEA-180121

Error: Can not find file fname.

Description

The file fname does not exist.

Cause

The configured WTC TPUSR file does not exist.

Action

Correct the WTC TPUSR file configuration or create the file.

BEA-180122

Error: No permission to read the file fname.

Description

User does not have the permission to read the file fname.

Cause

User does not have the read permission to read the configured TPUSR file.

Action

Change the permissions of the TPUSR file.

BEA-180123

Error: File IO error for file fname, reason: detail.

Description

Encountered file IO error while reading file fname.

Cause

Corrupted or deleted file.

Action

Correct the file corruption, or use a new TPUSR file.

BEA-180124

Error:

Description

The configured cache size is not in a valid number format.

Cause

The configured cache size is not in a valid number format.

Action

Correct the configuration in WTC TpUsrFile.

BEA-180125

Error: LDAP Exception: e, h:p.

Description

An exception occurred while trying to connect to the LDAP server (h:p>.

Cause

The default WebLogic Server LDAP server is not available.

Action

Correct the WebLogic Server configuration with the default BEA WebLogic Server security manager.

BEA-180126

Info: LDAPException: e

Description

LDAP exception occurred while disconnecting from LDAP server.

Cause

The connection to LDAP server may be gone.

Action

Verify whether the WebLogic Server embedded LDAP server is still functioning.

BEA-180127

Error:

Description

The configured UID is not in valid number format.

Cause

The configured TUXEDO UID is not in valid number format.

Action

Correct the configuration in the WebLogic Server user description.

BEA-180128

Error: WebLogic Server user u record is missing Tuxedo UID information.

Description

The configured Tuxedo user u does not contain keyword/value pair for describing Tuxedo UID.

Cause

The configured WebLogic Server user does have the required keyword/value pair for Tuxedo UID.

Action

Add the proper keyword/value pair for UID to the WebLogic Server user description field.

BEA-180129

Error: The WebLogic Server user u record is missing Tuxedo GID information.

Description

The configured Tuxedo user u does not contain keyword/value pair for describing Tuxedo GID.

Cause

The configured WebLogic Server user does have the required keyword/value pair for Tuxedo GID.

Action

Add the proper keyword/value pair for GID to the WebLogic Server user description field.

BEA-180130

Error:

Description

The configured GID is not in valid number format.

Cause

The configured TUXEDO GID is not in valid number format.

Action

Correct the configuration in the WebLogic Server user description.

BEA-180131

Error: LDAP search exception: e

Description

Exception occurred during LDAP search operation.

Cause

The embedded LDAP server is not available.

Action

Make sure the default WebLogic Server embedded LDAP server is running.

BEA-180132

Error: Custom AppKey generator class c not found.

Description

The specified custom AppKey c can not be found.

Cause

The configured custom AppKey class full path name is incorrect.

Action

Make sure the configuration is correct and that the custom class exists.

BEA-180133

Error: AppKey plug-in initialization failed. Reason: e

Description

The configured AppKey generator plug-in failed during initialization. Reason: e

Cause

The most likely reason is that the user database is not available or the initialization parameter is incorrect.

Action

Make sure that the user database is available and the configuration is correct.

BEA-180134

Error: Create new AppKey class e instance failed.

Description

Create new AppKey class e instance failed.

Cause

Either the class is not accessible, there is no permission to create a new instance of this class, or the class is not good.

Action

Make sure the class is accessible with the correct permission. Also, the class must be based on the weblogic.wtc.jatmi.AppKey interface.

BEA-180135

Error: Was not able to set the attrname attribute on the srvrmbname WTCServerMBean.

Description

Got an InvalidAttributeValueException when trying to set the attrname attribute on the srvrmbname WTCServerMBean.

Cause

The names provided result in invalid MBean information.

Action

Check that the WTCServerMBean name listed is created and valid.

BEA-180136

Error: The attrname attribute on the mbname MBean is undefined but required.

Description

Was not able to get the attrname attribute value from the mbname MBean.

Cause

The attribute value is not defined but must be.

Action

Check that the MBean attribute is set correctly.

BEA-180137

Error: The attrname attribute on the mbname MBean is set incorrectly.

Description

The value of the attrname attribute from the mbname MBean is not valid.

Cause

The attribute was defined improperly.

Action

Check that the MBean attribute is set correctly.

BEA-180138

Error: The mbname MBean appears to contain previous defined import service info.

Description

The mbname MBean appears to be a duplicate of previous import service info.

Cause

The attributes defined on this MBean have already been used to defined and imported service.

Action

Check that the Resourcename,RemoteAccessPointList, and LocalAccePoint attributes aren't all duplicated in another Import MBean.

BEA-180139

Error: A mbtype type MBean is not defined but is required to be.

Description

A mbtype type MBean is not defined but is required to be.

Cause

An MBean was not defined but is needed.

Action

Check that an MBean type specified is defined in the configuration.

BEA-180140

Debug: Security: msg

Description

Debug message concerning the security of sent and received TGIOP messages.

Cause

Internal debug.

Action

None.