gateway-dbc-fx/gnpdev/sim/build/building/sim-classes/weblogic/wtc/WTCLogLocalizerDetail.properties

prefix=WL
messagedetail180000=WTC will now be initialized according to the MBean config info entered.
cause180000=All other initialization has completed and now this method is ready to begin reading its own configuration info.
action180000=No action required.
messagedetail180001=WTC finished initialization according to the MBean config info entered.
cause180001=All WTC configuration MBeans were parsed without any problems.
action180001=No action required.
messagedetail180002=Invalid attributes exception when trying to create sub-context.
cause180002=An attempt was made to add an attribute set that has been specified incompletely or incorrectly.
action180002=Internal error. Contact Oracle Customer Support.
messagedetail180003=Naming exception while creating sub-context.
cause180003=Specified name can not be resolved.
action180003=Internal error. Contact Oracle Customer Support.
messagedetail180004=Failed to bind Tuxedo or Corba connection factory to JNDI.
cause180004=The name used by the Tuxedo connection factory or Tuxedo CORBA connection factory already bonded to another object.
action180004=Do not use the same name as Tuxedo or Tuxedo CORBA connection factory.
messagedetail180005=Invalid attributes exception occurred when trying to create Tuxedo or Tuxedo CORBA connection factroy.
cause180005=An attempt was made to add an attribute set that has been specified incompletely or incorrectly.
action180005=Internal error. Contact Oracle Customer Support.
messagedetail180006=Naming exception occurred while binding Tuxedo and Tuxedo CORBA connection factory to the JNDI.
cause180006=Specified name can not be resolved.
action180006=Internal error. Contact Oracle Customer Support.
messagedetail180007=Unable to register the resource with transaction manager.
cause180007=WTC is not running with server transaction manager.
action180007=Contact Oracle Customer Support.
messagedetail180008=A transaction identifier exists for a non-existing remote Tuxedo domain.
cause180008=The remote Tuxedo domain involved in the transaction is no longer in the WTC configuration.
action180008=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.
messagedetail180009=The processing of the MBean configuration could not complete.
cause180009=The definition contains some input information that is not consistent with the usage model.
action180009=Check the MBean definition to see if the individual attributes are consistent with the rest of the MBean definitions.
messagedetail180010=The TDMLocalTDomain constructor failed to create a new instance.
cause180010=The AccessPoint attribute definition for the WTCLocalTuxDom MBean is invalid.
action180010=Check the AccessPoint attribute of the WTCLocalTuxDom MBean.
messagedetail180011=The TDMRemoteTDomain constructor failed to create a new instance.
cause180011=The AccessPoint attribute definition for the WTCRemoteTuxDom MBean is invalid.
action180011=Check the AccessPoint attribute of the WTCRemoteTuxDom MBean.
messagedetail180012=Can not continue setting up the TDMRemote object because the LocalTDomain is not valid.
cause180012=The LocalAccessPoint attribute for the WTCRemoteTuxDom MBean is not a valid name for a LocalTDomain.
action180012=Verify the WTCRemoteTuxDom MBean definition has a valid name for the LocalAccessPoint Attribute.
messagedetail180013=Can not continue setting up the TDMExport object because the LocalTDomain is not valid.
cause180013=The LocalAccessPoint attribute for the WTCExport MBean is not a valid name for a LocalTDomain.
action180013=Verify the WTCExport MBean definition has a valid name for the LocalAccessPoint Attribute.
messagedetail180014=The TDMExport constructor failed to create a new instance.
cause180014=The ResourceName attribute definition for the WTCExport MBean is invalid or the LocalTDomain is not usable.
action180014=Check the ResourceName attribute of the WTCExport MBean.
messagedetail180015=Can not continue setting up the TDMImport object because the LocalTDomain is not valid.
cause180015=The LocalAccessPoint attribute for the WTCImport MBean is not a valid name for a LocalTDomain.
action180015=Confirm the WTCImport MBean definition has a valid name for the LocalAccessPoint Attribute.
messagedetail180016=Can not continue setting up the TDMImport object because the RemoteTDomain is not valid.
cause180016=The RemoteAccessPointList attribute for the WTCImport MBean does not contain a valid name for a RemoteTDomain.
action180016=Verify that the WTCImport MBean definition has valid names, a comma separated list, defined in the RemoteAccessPointList Attribute.
messagedetail180017=The TDMImport constructor failed to create a new instance.
cause180017=The ResourceName attribute definition for the WTCImport MBean is invalid. The LocalTDomain or the RemoteTDomains are not usable.
action180017=Check the ResourceName attribute of the WTCImport MBean.
messagedetail180018={0} Password and IV are both needed to generate correct information.
cause180018=The Password or PasswordIV attribute is not set.
action180018=Verify that the Password and PasswordIV attributes are valid.
messagedetail180019=Can not continue setting up the TDMPasswd object because the LocalTDomain is not valid.
cause180019=The LocalAccessPoint attribute for the WTCPassword MBean is not a valid name for a LocalTDomain.
action180019=Verify that the WTCPassword MBean definition has a valid name for the LocalAccessPoint Attribute.
messagedetail180020=Can not continue setting up the TDMImport object because the RemoteTDomain is not valid.
cause180020=The RemoteAccessPoint attribute for the WTCPassword MBean is not a valid name for a RemoteTDomain.
action180020=Verify that the WTCPassword MBean definition has a valid name for the RemoteAccessPoint Attribute.
messagedetail180021=The TDMPasswd constructor failed to create a new instance.
cause180021=The LocalTDomain or the RemoteTDomain is not usable.
action180021=Check the LocalAccessPoint and RemoteAccessPoint attributes of the WTCPassword MBean.
messagedetail180022=An unsuccessful attempt was made to set up a FldTbls array using the WTCResources MBean.
cause180022=The fully qualified name for any field table may be incorrect or it can not be found.
action180022=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.
messagedetail180023=WTC failed to commit the transaction with status {0}.
cause180023=The transaction became a heuristic hazard, or the resource manager encountered an error.
action180023=Correct the transaction manually if it became a heuristic hazard, or correct the resource manager problem.
messagedetail180024=Failed to send a reply to remote Tuxedo domain for a transaction that WTC no longer knows about.
cause180024=The connection to the remote Tuxedo domain already terminated, or an IOException occurred while writing to the network.
action180024=If the TPException is TPEPROTO, then try to reboot the remote Tuxedo domain. If the TPException is TPESYSTEM, then check the network connection.
messagedetail180025=The field type being used is not one that is defined in the TypedFML Class.
cause180025=TypedFML32 data is possibly being used instead of TypedFML.
action180025=Verify the type of input data.
messagedetail180026=While trying to use FML data, caught this Ferror exception: {0}
cause180026=The data was not created correctly.
action180026=Verify the data passed into this method.
messagedetail180027=While trying to use FML data, caught an Unknown exception: {0}
cause180027=The data was not created correctly.
action180027=Verify the data passed into this method.
messagedetail180028=The field type being used is not one that is defined in the TypedFML32 Class.
cause180028=Possibly TypedFML data is being used instead of TypedFML32.
action180028=Verify the type of input data.
messagedetail180029=Caught an Ferror exception while processing TypedFML32 data.
cause180029=The data was not created correctly.
action180029=Verify the data passed into this method.
messagedetail180030=While trying to use FML32 data, caught an Unknown exception: {0}
cause180030=The data was not created correctly.
action180030=Verify the data passed into this method.
messagedetail180031=Xml argument is null.
cause180031=Did not initialize argument passed in.
action180031=Check the xml argument passed in.
messagedetail180032=The FldTbl[] input argument is null or an empty array.
cause180032=Did not initialize argument passed in.
action180032=Check the FldTbl[] argument passed in.
messagedetail180033=TypedFML argument is null.
cause180033=Did not initialize argument passed in.
action180033=Check the TypedFML argument passed in.
messagedetail180034=An error occurred while searching for the document root element in the XML input string.
cause180034=The input XML string was not formatted correctly.
action180034=Check for other errors listed that should indicate what was unacceptable about the XML input.
messagedetail180035=TypedFML32 argument is null.
cause180035=Did not initialize argument passed in.
action180035=Check the TypedFML32 argument passed in.
messagedetail180036=XML input {0} caused SAX parser exception {1}
cause180036=The DOM parser did not like the XML string that it received.
action180036=Check the SAX exception info returned and the XML string entered.
messagedetail180037=XML input {0} caused IO exception {1}.
cause180037=The XML string was not convertible to an InputSource() class.
action180037=Check the IO exception info returned and the XML string entered.
messagedetail180038=XML input {0} caused an unknown exception {1}.
cause180038=The XML string was not able to be parsed.
action180038=Check the exception info returned and the XML string entered.
messagedetail180039=The DOM parser returned a null value for input {0}.
cause180039=The input may not be a valid XML string.
action180039=Check the string passed to the parser.
messagedetail180040=Parser could not return the top element of the document tree that represents the start of the XML input.
cause180040=The XML input does not have any elements defined.
action180040=Verify that the input string has a proper definition for a root element.
messagedetail180041=Could not get a tag name for the root element in XML input {0}.
cause180041=The XML input does not have a tag name for the root element.
action180041=Verify that the root element has a proper definition.
messagedetail180042=Internal TypedFML data is null.
cause180042=Did not initialize internal data using XMLtoFML() API.
action180042=Use XMLtoFML to initialize internal data.
messagedetail180043=Xml element name is null.
cause180043=The XML element information was not properly defined
action180043=Check the XML element definition.
messagedetail180044=XML element value is null for the element name {0}.
cause180044=The XML element information was not properly defined.
action180044=Check the XML element definition.
messagedetail180045=Internal TypedFML32 data is null.
cause180045=Did not initialize internal data using XMLtoFML32() API.
action180045=Use XMLtoFML32 to initialize internal data.
messagedetail180046=Uncatalogued debug message. Do not change.
cause180046=Debugging. Do not change.
action180046=No action required.
messagedetail180047=The tBridge must be given at least one redirect command; otherwise it has nothing to do.
cause180047=Improper configuration of the tBridge.
action180047=User must configure at least one redirect command in the WTC_CONFIG for the tBridge section.
messagedetail180048=The JNDI lookup for the TuxedoConnectionFactory has failed.
cause180048=The WTC has not be properly configured.
action180048=Review the WTC documentation and restart the WTC.
messagedetail180049=The tBridge was told to use the WLXT translator. However, this option could not be located.
cause180049=The WLXT package might not be loaded or in the proper CLASSPATH.
action180049=Install the WLXT and properly configure the translator option.
messagedetail180050=The internal tBridge FML/XML translator has failed to convert the buffer.
cause180050=The syntax of the incoming message could not be understood.
action180050=Correct the message syntax and retry.
messagedetail180052=Unable to cancel open connection retry object for ON_STARTUP connection policy.
cause180052=Unable to delete timer service object for ON_STARTUP connection policy during connection termination.
action180052=Contact Oracle Customer Support.
messagedetail180053=An internal error occurred while trying to create security token.
cause180053=Internal error.
action180053=Contact Oracle Customer Support to report this problem with token type information found in the log message.
messagedetail180054=An internal error occurred while reading the received security token.
cause180054=Internal error.
action180054=Contact Oracle Customer Support to report this problem with token type information found in the log message.
messagedetail180055=Received a token that WTC does not expect to receive or that contains incorrect information.
cause180055=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.
action180055=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.
messagedetail180056=Encountered error during encryption.
cause180056=Not enough free memory space to continue, or internal error.
action180056=Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact Oracle Customer Support.
messagedetail180057=The challenge returned by remote Tuxedo domain is not valid.
cause180057=This is caused by an incorrect configuration and mismatched password.
action180057=Correct the configuration and the password.
messagedetail180058=Encountered IO operation error while doing encryption.
cause180058=Internal system error.
action180058=Contact Oracle Customer Support.
messagedetail180059=Encountered error during encryption.
cause180059=Not enough free memory space to continue or internal error.
action180059=Try to force garbage collection, and remove some services to reduce memory usage. If problem persists, contact Oracle Customer Support.
messagedetail180063=The handler address length is not the same as expected.
cause180063=The client did not talk to a valid listener.
action180063=Check the listener address and correct the configuration.
messagedetail180067=Invalid WSRPCRQ discriminator.
cause180067=Client is not talking to a valid handler.
action180067=Check the configuration and correct the error.
messagedetail180068=The type of discriminator is not supported.
cause180068=Client is not talking to a valid handler.
action180068=Check the configuration and correct it.
messagedetail180069=Unable to read data in the buffer type {0}.
cause180069=General IO exception.
action180069=Please read the exception description to determine the actual cause and act accordingly.
messagedetail180070=TypeFML32 got a pointer of unknown type {0}. Will replace with null.
cause180070=Incorrectly written application with unknown data type.
action180070=Correct the problem with the data type in the application.
messagedetail180071=Invalid Typed FML32 field {0}. Equals null.
cause180071=Incorrectly constructed embedded FML32 buffer in the FML32 buffer.
action180071=Check the source of the embedded FML32 buffer, and correct the problem.
messagedetail180072=Marker to indicate start of debugging for TDumpByte.
cause180072=Debugging. Do not change.
action180072=No action required.
messagedetail180073=Marker to indicate end of debugging for TDumpByte.
cause180073=Debugging. Do not change.
action180073=No action required.
messagedetail180074=tpinit buffer not received.
cause180074=The server is likely talking to an invalid handler.
action180074=Check the configuration and correct the problem.
messagedetail180075=The received transaction data is smaller than expected.
cause180075=Remote Tuxedo Domain Gateway is not valid.
action180075=Check the configuration of the remote Tuxedo domain and correct the error.
messagedetail180076=Caught IO exception while formating password.
cause180076=An I/O error occurred.
action180076=Check for system memory usage and see if force garbage collection is possible. If problem persists, contact Oracle Customer Support.
messagedetail180077=Caught IO exception while closing the connection to remote Tuxedo domain.
cause180077=An I/O error occurred while closing the socket.
action180077=Check your network and system environment. If problem persists, contact Oracle Customer Support.
messagedetail180078=Could not find the handle for ACALL reply.
cause180078=The ACALL request already timed out.
action180078=This message is informational only.
messagedetail180079=Failed to properly receive message header.
cause180079=The received message header is not properly formatted or failed to decompress the data.
action180079=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 Oracle Customer Support.
messagedetail180080=The received message header is missing the required WebLogic Server information.
cause180080=Not talking to a valid remote Tuxedo domain.
action180080=Check the remote Tuxedo domain configuration and correct the problem.
messagedetail180081=Caught I/O exception while processing the message header.
cause180081=An I/O error occurred while reading the message header from input stream.
action180081=Check system memory usage and force garbage collection. If problem persists, contact Oracle Customer Support.
messagedetail180082=Caught I/O exception and unable to close WSH socket by client.
cause180082=An I/O error occurred.
action180082=Check the network and system configuration.
messagedetail180083=Received a TCM with an unsupported buffer type {0}.
cause180083=WTC is communicating with an unsupported Tuxedo version.
action180083=Check the configuration and correct the error.
messagedetail180084=Caught I/O exception while writing TCM to output data stream.
cause180084=An I/O error occurred.
action180084=Check the system memory usage and force garbage collection.
messagedetail180085=Caught I/O exception while writing an unsolicited acknowledgment to data output staream.
cause180085=An I/O error occurred.
action180085=Check system memory usage.
messagedetail180086=Connection to remote domain established.
cause180086=Connection request was received from a remote domain.
action180086=No action required.
messagedetail180087=Connection to a remote domain established.
cause180087=Initiate the connection request to a remote domain.
action180087=No action required.
messagedetail180088=Error encountered during build of outgoing message.
cause180088=This is an internal error.
action180088=Contact Oracle Customer Support.
messagedetail180089=Error encountered during decoding of incoming message.
cause180089=This is an internal error.
action180089=Contact Oracle Customer Support.
messagedetail180090=Remote domain detected an authentication failure and rejected the connection request.
cause180090=User configuration error.
action180090=Check both side configurations to see whether a mismatch exists in the configuration, including the password.
messagedetail180091=Local domain detected an authentication failure and rejected the connection request.
cause180091=User configuration error.
action180091=Check both side configurations to see whether a mismatch exists in configuration, including the password.
messagedetail180092=Security validation failed.
cause180092=User configuration error, unauthorized access.
action180092=Check both side configurations to see if a mismatch exists in the configuration, including password.
messagedetail180093=A naming exception occurred during lookup of the admin name: {0}.
cause180093=The specified name can not be resolved.
action180093=Contact Oracle Customer Support.
messagedetail180094=The tBridge tried to locate and initialize the targetName queue, but an error was returned. The tBridge cannot continue.
cause180094=The JMS targetName queue does not exist or the JMS server is not running on the system.
action180094=Correct the JMS problem and restart the WTC tBridge.
messagedetail180095=A failure was reported from JMS during the initialization of the sourceName queue. This fromto thread of tBridge cannot continue.
cause180095=The sourceName queue can not exist in JMS or the JMS server may not be started.
action180095=Correct the JMS problem and restart the WTC tBridge.
messagedetail180096=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.
cause180096=The JMS wlsErrorDestination queue may not be properly configured in WebLogic Server.
action180096=Correct the JMS problem and restart the WTC tBridge.
messagedetail180097=The tBridge encountered a translation error and has redirected the message to the wlsErrorDestination queue.
cause180097=The cause of this error is a translation error detected from/to FML/XML.
action180097=Correct the message structure and resend the message.
messagedetail180098=The tBridge failed to send the message that generated the error to the wlsErrorDestination. The message remains unacknowledged on the JMS input queue.
cause180098=The JMS wlsErrorDestination could be full or paused.
action180098=Recover the message from the sourceName JMS queue and resend.
messagedetail180099=The configured MinEncryptionBits is greater than MaxEncryptionBits.
cause180099=User configuration error.
action180099=Use WebLogic Server console to modify WTC configuration so that it will use the correct values for Min and Max Encryption Bits.
messagedetail180100=Bad configuration information found.
cause180100=User configuration error.
action180100=Use WebLogic Server console to modify WTC configuration so that it will use the correct values for the corresponding error.
messagedetail180102=Bad configuration information. Contains two local domains having the same ID.
cause180102=User configuration error.
action180102=Use WebLogic Server console to modify WTC configuration to use the unique ID for the local domain.
messagedetail180103=Bad configuration information found in the WTC configuration.
cause180103=User configuration error.
action180103=Use WebLogic Server console to modify the WTC configuration to remove the redundant entry or correct the configuration information.
messagedetail180104=The tBridge only supporters the JMS TextMessage and BytesMessage. All other types are rejected and not redirected to the error destination.
cause180104=The user has sent a JMS Stream or Mapped message type to the tBridge.
action180104=Correct the JMS message type and resend.
messagedetail180105=A message has been dropped by the WTC gateway. Other log messages should provide details on the reason the message was dropped.
cause180105=The most common cause of this failure is that an unrecognized buffer type has been received by the WTC gateway.
action180105=Modify the application to make sure that unknown buffer types are not sent to the WTC gateway.
messagedetail180106=While attempting to recover transactions from Tuxedo into WebLogic Server, the system was unable to find the WebLogic Server transaction manager.
cause180106=A transaction manager could not be found.
action180106=Contact Oracle Customer Support.
messagedetail180107=While attempting to recover transactions, the recover method failed.
cause180107=The recover method on the WLS XA Resource threw an exception.
action180107=Contact Oracle Customer Support.
messagedetail180108=While attempting to recover transactions, the rollback method failed.
cause180108=The rollback method on the WLS XA Resource threw an exception.
action180108=Contact Oracle Customer Support.
messagedetail180109=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.
cause180109=The FML buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
action180109=Verify that the field tables have been properly transfered as described in the WTC documentation.
messagedetail180110=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.
cause180110=The FML32 buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
action180110=Verify the field tables have been properly transferred as described in the WTC documentation.
messagedetail180111=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.
cause180111=The FML buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
action180111=Verify the field tables have been properly transferred as described in the WTC documentation.
messagedetail180112=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.
cause180112=The FML32 buffer received from Tuxedo contained field buffer names that were not provided to WTC. Therefore, the name translation failed.
action180112=Verify the field tables have been properly transferred as described in the WTC documentation.
messagedetail180113=The message is for debug tracing.
cause180113=The message is for debug tracing.
action180113=No action is required.
messagedetail180115=The startup configuration for tBridge contained in the WTCtBridgeGlobal and WTCtBridgeRedirect MBeans could not be understood.
cause180115=The MBeans for tBridge contain invalid attributes.
action180115=Correct the attribute definitions for the tBridge MBeans.
messagedetail180116=The FldTblClass type used is not one of the valid types, fml16 or fml32, allowed.
cause180116=The WTCStartup.getFldTbls() method was called with an invalid argument.
action180116=Verify that the Type argument for this is either "fml16" or "fml32".
messagedetail180117=The encoding {0} is not supported. Java VM default encoding is used.
cause180117=Specified encoding name is not supported.
action180117=Correct the encoding name and restart WebLogic Server.
messagedetail180118=The configured TPUSR file {0} does not exist.
cause180118=The specified file TPUSR file does not exist.
action180118=Correct the configuration by specifying the correct TPUSR file or create it before using it.
messagedetail180119=The configured TPUSR file {0} is not a file.
cause180119=Incorrect WTC TPUSR file configuration.
action180119=Correct the WTC TPUSR file configuration.
messagedetail180120=User does not have permission to read file {0}.
cause180120=User does not have the read permission to read the configured TPUSR file.
action180120=Change the permissions of the TPUSR file.
messagedetail180121=The file {0} does not exist.
cause180121=The configured WTC TPUSR file does not exist.
action180121=Correct the WTC TPUSR file configuration or create the file.
messagedetail180122=User does not have the permission to read the file {0}.
cause180122=User does not have the read permission to read the configured TPUSR file.
action180122=Change the permissions of the TPUSR file.
messagedetail180123=Encountered file IO error while reading file {0}.
cause180123=Corrupted or deleted file.
action180123=Correct the file corruption, or use a new TPUSR file.
messagedetail180124=The configured cache size is not in a valid number format.
cause180124=The configured cache size is not in a valid number format.
action180124=Correct the configuration in WTC TpUsrFile.
messagedetail180132=The specified custom AppKey {0} can not be found.
cause180132=The configured custom AppKey class full path name is incorrect.
action180132=Make sure the configuration is correct and that the custom class exists.
messagedetail180133=The configured AppKey generator plug-in failed during initialization. Reason: {0}
cause180133=The most likely reason is that the user database is not available or the initialization parameter is incorrect.
action180133=Make sure that the user database is available and the configuration is correct.
messagedetail180134=Create new AppKey class {0} instance failed.
cause180134=Either the class is not accessible, there is no permission to create a new instance of this class, or the class is not good.
action180134=Make sure the class is accessible with the correct permission. Also, the class must be based on the weblogic.wtc.jatmi.AppKey interface.
messagedetail180136=Was not able to get the {0} attribute value from the {1} MBean.
cause180136=The attribute value is not defined but must be.
action180136=Check that the MBean attribute is set correctly.
messagedetail180137=The value of the {0} attribute from the {1} MBean is not valid.
cause180137=The attribute was defined improperly.
action180137=Check that the MBean attribute is set correctly.
messagedetail180138=The {0} MBean appears to be a duplicate of previous import service info.
cause180138=The attributes defined on this MBean have already been used to defined and imported service.
action180138=Check that the Resourcename,RemoteAccessPointList, and LocalAccessPoint attributes aren't all duplicated in another Import MBean.
messagedetail180139=A {0} type MBean is not defined but is required to be.
cause180139=An MBean was not defined but is needed.
action180139=Check that an MBean type specified is defined in the configuration.
messagedetail180140=Debug message concerning the security of sent and received TGIOP messages.
cause180140=Internal debug.
action180140=None.
messagedetail180141=The message header contains invalid magic number, close the connection.
cause180141=Either received invalid TDOMAIN PDU, or the remote domain gateway does not have network encoding enabled.
action180141=Make sure the locale access point is configured with the correct port number, and the remote gateway does not have the same MTYPE configured for this TDOMAIN session.
messagedetail180142=Local domain is referenced by another resource. It cannot be deleted.
cause180142=User configuration error.
action180142=Check for remote domains, imported or exported services or passwords that use this local domain.
messagedetail180143=Cannot find local domain with the given access point name.
cause180143=User configuration error.
action180143=Check access point name.
messagedetail180144=Cannot add remote domain. Duplicate access point name.
cause180144=User configuration error.
action180144=Check access points and access point ids for existing domains.
messagedetail180145=The remote domain is referenced by another resource or has an active connection. It cannot be deleted.
cause180145=User configuration error.
action180145=Shut down the connection to this remote domain. Check other resources that may reference this domain.
messagedetail180146=The specified remote domain cannot be found.
cause180146=User configuration error.
action180146=Check the access point name for the remote domain.
messagedetail180147=Cannot find the specified imported service.
cause180147=User configuration error.
action180147=Check the name of the imported service.
messagedetail180148=Cannot find specified exported service.
cause180148=User configuration error.
action180148=Check name of exported service.
messagedetail180149=Cannot find specified password entry.
cause180149=User configuration error.
action180149=Check local and remote access point names.
messagedetail180150=Cannot start an outbound connection when the connection policy specifies INCOMING_ONLY.
cause180150=User error.
action180150=Check the access point id for the remote domain.
messagedetail180151=Cannot modify resource. One of its associated domains has an active connection.
cause180151=There is an active connection that may use this resource.
action180151=Stop connections associated with this resource before attempting to delete.
messagedetail180152=Registration of notification listeners for the configured MBeans has failed.
cause180152=Internal system error.
action180152=Internal system error. Contact Oracle Customer Support.
messagedetail180153=There is no valid host internet address for WTC initiated outbound connection for the specified remote access point.
cause180153=configuration error.
action180153=Correct the WTC Remote Access Point's network address list.
messagedetail180154=There is no valid listening address configured for local access point.
cause180154=Internal system error.
action180154=Internal system error. Contact Oracle Customer Support.
messagedetail180155=No more valid network address to use to connect from the specified local access point to the remote access point.
cause180155=Either there is a configuration error or the remote access point is not available, and can not be accessed using the configured information.
action180155=Correct the configuration, or boot the remote access point.
messagedetail180156=Connect to network address failed, will try the next address in the list.
cause180156=Either a configuration error, or the remote access point is not available at the address specified.
action180156=This message is informational and it tells the user it will try next network address to connect.
messagedetail180157=Connect to network address failed, there is no more network address in the list for this remote access point to try.
cause180157=Either a configuration error, or the remote access point is not available at the address specified.
action180157=This message is warning, correct configuration or make the remote access point available.
messagedetail180158=No more valid network address to use to listen for the specified local access point.
cause180158=There is a configuration error.
action180158=Correct the configuration.
messagedetail180159=Failed to create network address listening endpoint, will try the next address in the list.
cause180159=Either a configuration error, or simply as it is intended.
action180159=This message is informational and it tells the user it will try next network address to create listening endpoint.
messagedetail180160=Create listening using the specified network address failed, there is no more network address in the list for this local access point to try.
cause180160=A configuration error.
action180160=Correct configuration.
messagedetail180161=The tBridge failed to find the imported service that represents the QSpace in Tuxedo domain.
cause180161=Incorrectly configured WTC Import.
action180161=Correct the configuration.
messagedetail180162=The tBridge failed to find the requested Tuxedo service in WTC import service configuration.
cause180162=The cause of this error is a configuration error.
action180162=Correct the configuration.
messagedetail180163=The tBridge received the reply with unsupported buffer type from Tuxedo server.
cause180163=Tuxedo server returned reply with unsupported buffer type.
action180163=Modify the Tuxedo server to return the reply with WTC supported buffer type.
messagedetail180164=The tBridge encountered a JMS problem while sending message to JMS.
cause180164=The JMS replyQ is configured incorrectly.
action180164=Correct the configuration of the JMS queue to be used for tBridge reply queue.
messagedetail180165=The TDomain session between specified local access point and remote access point became idle and exceeded the time allowed by the keep alive feature that is configured. And the keep alive feature exceeded the wait limit without receiving acknowledge so the connection is terminated.
cause180165=It is possible that there is a network outage.
action180165=Check the network connection between these two gateways whether it is connected.
messagedetail180166=The TDomain session between specified local access point and remote access point is configured with optional KeepAlive. However, it is determined that remote gateway does not support Application KeepAlive feature so it is disabled.
cause180166=The remote gateway does not support this Application Level KeepAlive feature.
action180166=Update the remote gateway to a version of TUXEDO that support TDomain Application Level KeepAlive.
messagedetail180167=The imported resource is configured for a TDomain session between specified local access point and remote access point does not exist.
cause180167=Incorrectly configured imported resource.
action180167=Correct the configuration for the imported service.
messagedetail180168=The WTCPasswordMbean did not contain valid passwords for the connection between the domains listed.
cause180168=Incorrectly configured domain passwords.
action180168=Encrypt correct local and remote passwords for the connection using the weblogic.wtc.gwt.genpasswd utility and use the results to configure a WTCPasswordMBean.
messagedetail180169=An error was encountered while closing the transaction branch.
cause180169=The transaction may have been marked ROLLBACK_ONLY
action180169=Inspect the application logic to find out the cause of the error.
messagedetail180170=An error was encountered while processing the View buffer.
cause180170=Refer to the exception details.
action180170=Refer to the exception details.
messagedetail180171=The SSL NULL ciphers are not enabled, but the WTC configuration requested it.
cause180171=The NULL cipher suites are disabled by SSL configuration.
action180171=User can ignore it since stronger encryption strength is allowed by WTC configuration, and also available by SSL. User can also choose to correct WTC configuration to use only 56 bits and stronger cipher suites or enable SSL NULL ciphers if that is desired.
messagedetail180172=The SSL NULL ciphers are not enabled, but the WTC configuration requires it.
cause180172=The NULL cipher suites are disabled by SSL configuration.
action180172=User must either enable the SSL NULL cipher suites explicitly, or changes WTC configuration to use stronger encryption cipher suites.
messagedetail180173=The SSL socket factory failed to get private key from key store.
cause180173=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.
action180173=Correct the key store or private key alias information in the configuration.
messagedetail180174=The configured private key store either does not exist or is corrupted.
cause180174=The private key store configured does not exist, or is corrupted.
action180174=Correct the private key store configuration information.
messagedetail180175=The configured trust certificate store either does not exist or is corrupted.
cause180175=The private key store configured does not exist, or corrupted.
action180175=Correct the private key store configuration information.
messagedetail180176=Could not retrieve trust certificate from configured trust store.
cause180176=The configured trust certificate is corrupted or an incorrect passphrase is configured.
action180176=Correct the trust certificate store configuration information.
messagedetail180177=Could not retrieve trust certificates from WebLogic Server configured trust store.
cause180177=The configured trust certificate is corrupted or an incorrect passphrase is configured.
action180177=Correct the trust certificate store configuration information.
messagedetail180178=The request minimum or maximum entryption strength is above the maximum supported LLE encryption strength, have to downgrade to use the maximum encryption strength supported by LLE and that is 128 bits.
cause180178=The configured encryption strength is not supported by Link Level Encryption.
action180178=Either change it to LLE supported strength or use SSL for connection privacy. LLE supports 0, 40, 56, and 128 bits encryption strength. SSL supports 0, 56, 128, and 256 bits encryption strength.
messagedetail180179=If SDP transport is configured for this access point, the configured value of UseSSL is ignored and the value off is used.
cause180179=When SDP is configured, SSL is not supported.
action180179=No action is required if SDP support is expected. Otherwise, update the configuration to disable SDP support.
messagedetail180180=When the access point is configured to support SDP, the current Java Runtime Environment (JRE) must contain com.oracle.net.Sdp in its runtime package.
cause180180=The current JRE does not support SDP.
action180180=Use the JRockit version of the JRE provided with this release of WebLogic Server.