Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
6600 |
ERROR: Invalid TMMONITOR appfields setting | |
|
Description |
An invalid "appfields" is given in TMMONITOR's required fields section. |
Action |
Make sure the FML32 fields used in "appfields" are correct and no spelling error. Also make sure $TUXDIR/udataobj is added in the environment variable FLDTBLDIR32 and "tpadm" is added in the environment variable FIELDTBLS32. | |
6601 |
ERROR: Invalid TMMONITOR svcfields setting | |
|
Description |
An invalid "svcfields" is given in TMMONITOR's required fields section. |
Action |
Make sure the FML32 fields used in "svcfields" are correct and no spelling error. Also make sure $TUXDIR/udataobj is added in the environment variable FLDTBLDIR32 and "tpadm" is added in the environment variable FIELDTBLS32. | |
6602 |
ERROR: Unknown TMMONITOR required fields category key | |
|
Description |
TSAM framework failed to parse TMMONITOR specification due to an unknown required fields key word is given. |
Action |
Check ULOG, make sure the required fields key is correct. | |
6603 |
ERROR: Invalid TMMONITOR policy expression | |
|
Description |
An invalid policy expression is given in TMMONITOR's monitoring policy section. |
Action |
The policy format in TMMONITOR is "policykeyword=policyvalue", such as "appratio=3". Make sure the settings is consistent with this style. | |
6604 |
ERROR: The TMMONITOR policy appratio and appinterval can not be set concurrently | |
|
Description |
The ratio and interval policy can not be used together in TMMONITOR for one kind monitoring category. |
Action |
Do not use "appratio" and "appinterval" in one TMMONITOR specification. | |
6605 |
ERROR: Invalid TMMONITOR appratio value | |
|
Description |
TSAM framework failed to parse "appratio" policy due to an invalid value is given. |
Action |
Check the value of "appratio", the allowed range is an integer of [0,65535]. | |
6606 |
ERROR: Invalid TMMONITOR appinterval value | |
|
Description |
TSAM framework failed to parse "appinterval" policy due to an invalid value is given. |
Action |
Check the value of "appinterval", the allowed range is an integer of [0,65535]. | |
6607 |
ERROR: The TMMONITOR policy svcratio and svcinterval can not be set concurrently | |
|
Description |
The ratio and interval policy can not be used together in TMMONITOR for one kind monitoring category. |
Action |
Do not use "svcratio" and "svcinterval" in one TMMONITOR specification. | |
6608 |
ERROR: Invalid TMMONITOR svcratio value | |
|
Description |
TSAM framework failed to parse "svcratio" policy due to an invalid value is given. |
Action |
Check the value of "svcratio", the allowed range is an integer of [0,65535]. | |
6609 |
ERROR: Invalid TMMONITOR svcinterval value | |
|
Description |
TSAM framework failed to parse "svcinterval" policy due to an invalid value is given. |
Action |
Check the value of "svcinterval", the allowed range is an integer of [0,65535]. | |
6610 |
ERROR: Invalid TMMONITOR sysinterval value | |
|
Description |
TSAM framework failed to parse "sysinterval" policy due to an invalid value is given. |
Action |
Check the value of "sysinterval", the allowed range is an integer of [30,65535]. | |
6611 |
ERROR: Invalid TMMONITOR tranratio value | |
|
Description |
TSAM framework failed to parse "tranratio" policy due to an invalid value is given. |
Action |
Check the value of "tranratio", the allowed range is an integer of [0,65535]. | |
6612 |
ERROR: Invalid TMMONITOR appnolog value | |
|
Description |
TSAM framework failed to parse "appnolog" policy due to an invalid value is given. |
Action |
Check the value of "appnolog", the allowed value is 1. | |
6613 |
ERROR: Unknown TMMONITOR monitoring policy: key | |
|
Description |
TSAM framework failed to parse TMMONITOR specification due to an unknown policy key word is given. |
Action |
Check ULOG, make sure the policy spelling is correct. | |
6614 |
WARN: Duplicate TMMONITOR monitoring category key | |
|
Description |
Multiple monitoring categories are given for one monitoring category. |
Action |
Remove the duplicated monitoring category key words. | |
6615 |
ERROR: Unknown TMMONITOR monitoring category: key | |
|
Description |
TSAM framework failed to parse TMMONITOR specification due to an unknown monitoring category key word is given. |
Action |
Check ULOG, make sure the monitoring category spelling is correct. | |
6616 |
ERROR: TMMONITOR specification parsing was failed,specification | |
|
Description |
TSAM framework failed to parse TMMONITOR specification. |
Action |
Check ULOG for the detail error information before this message. | |
6617 |
INFO:TMMONITOR (specification) was parsed successfully | |
|
Description |
TSAM framework parsed TMMONITOR successfully. |
Action |
None. | |
6618 |
ERROR: Tuxedo supported correlation ID buffer length must >= value | |
|
Description |
TSAM framework failed to generate the correlation ID in call path monitoring. |
Action |
For the custom plug-in, make sure the buffer lenth is greater than 256 to get a new correlation ID from TSAM framework. | |
6619 |
ERROR: TMMONITOR failed to operate on META_TCM buffer | |
|
Description |
TSAM framework failed to operate on the message header for call path monitored message. |
Action |
Contact BEA Customer Support. | |
6620 |
ERROR: TMMONITOR failed to operate on plug-in buffer | |
|
Description |
TSAM framework failed to operate on the performance metrics buffer prepared for plug-in. |
Action |
Contact BEA Customer Support. | |
6621 |
ERROR: TMMONITOR failed to get the correlation ID from plug-in | |
|
Description |
TSAM framework failed to get correlation ID from plug-in for call path monitoring. |
Action |
If TSAM default plug-in is used, contact BEA Customer Support. If the custom plug-in is used, make sure the correlation ID is passed back to TSAM framework in the MONITORCTL structure. | |
See Also |
TSAM Plug-in programming guide. | |
6622 |
ERROR: TMMONITOR failed to parse the monitoring policy passed back from plug-in | |
|
Description |
The monitoring policy passed back from plug-in is invalid. |
Action |
Contact BEA Customer Support. | |
6623 |
ERROR: TMMONITOR failed to invoke the monitoring plug-in | |
|
Description |
TSAM framework failed to invoke the monitoring plug-in at monitoring points. |
Action |
Contact BEA Customer Support. | |
6624 |
ERROR: TMMONITOR failed to parse the required fields passed back from plug-in | |
|
Description |
The required fields passed back from plug-in are invalid. |
Action |
Contact BEA Customer Support. | |
6625 |
ERROR: Unknown TMMONITOR error | |
|
Description |
TSAM encounters unkown errors. |
Action |
Contact BEA Customer Support. | |
6626 |
ERROR: TMMONITOR system monitor hash table memory allocation failed | |
|
Description |
TSAM framework failed to allocate memory for internal hash table. |
Action |
Contact BEA Customer Support. | |
6627 |
ERROR: Invalid TMMONITOR appdecode value | |
|
Description |
TSAM framework failed to parse "appdecode" policy due to an invalid value is given. |
Action |
Check the value of "appdecode", the allowed value is 1. | |
6628 |
ERROR: Could not read from SSL connection, err = code | |
|
Description |
An error 'code' occurred while reading from the SSL connection. |
Action |
Contact BEA Customer Support. | |
6629 |
ERROR: Could not write to SSL connection, err = code | |
|
Description |
An error 'code' occurred while trying to write to the SSL connection. This may occur due to errors in the SSL handshake or transport errors on the socket. |
Action |
Check the ULOG for more information about the error. | |
6630 |
ERROR: Memory allocation failure | |
|
Description |
Failed to allocate memory to hold a queued message data structure. |
Action |
Check whether the system has enough memory installed and configured. | |
6631 |
ERROR: Could not create SSL context on connect | |
|
Description |
The creation of SSL context failed. |
Action |
The ULOG may give more information about the error. | |
6632 |
ERROR: Could not set SSL protocol to client side, err = code | |
|
Description |
Error occurred while trying to set the SSL protocol due to error 'code'. |
Action |
Contact BEA Customer Support. | |
6633 |
ERROR: Could not create SSL context on accept | |
|
Description |
Failed to create SSL context. |
Action |
Check the ULOG for more information about the error. Contact BEA Customer Support. | |
6634 |
ERROR: Could not set SSL protocol to server side, err = code | |
|
Description |
Failed to set the SSL protocl to SSL server side due to the error 'code'. |
Action |
Check the ULOG for more information about the error. | |
6635 |
ERROR: Could not set SSL mutual authentication, err = code | |
|
Description |
Encountered the error 'code' during SSL initialization. SSL reported this error while trying to enable mutual authentication. |
Action |
Contact BEA Customer Support. | |
6636 |
ERROR: Could not read from SSL connection, err = code | |
|
Description |
Encountered error during read from SSL connection due to error 'code'. |
Action |
Contact BEA Customer Support. | |
6637 |
ERROR: Could not write to SSL connection, err = code | |
|
Description |
Unable to read from the SSL connection, received error 'code'. |
Action |
Contact BEA Customer Support. | |
6638 |
ERROR: Could not load SSL library libname, err = code | |
|
Description |
Failed to load SSL library libname dynamically, receive error 'code'. |
Action |
Check the TUXEDO installation. If the installation is fine but problem persists, contact BEA Customer Support. | |
6639 |
ERROR: Could not get SSL library init rtn, err = code | |
|
Description |
The process received the error 'val' while trying to read the SSL library initialization function from the SSL library. This error indicates an installation problem. |
Action |
Check the TUXEDO installation. If the installation is fine but problem persists contact BEA Customer Support. | |
6640 |
ERROR: Could not initialize SSL library, err = code | |
|
Description |
Failed to initialize SSL library with error 'code'. |
Action |
Contact BEA Customer Support. | |
6641 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6642 |
ERROR: Could not initialize SSL context, err = code | |
|
Description |
The process received the error 'var>val' while initializing the SSL context. |
Action |
Check the ULOG for more information indicating the nature of the failure. | |
6643 |
ERROR: Could not set SSL protocol version, err = code | |
|
Description |
The process received error 'code while trying to set the SSL protocl version. |
Action |
Contact BEA Customer Support. | |
6644 |
ERROR: No SSL cipher suites | |
|
Description |
The process could not find the SSL cipher suites supported by TUXEDO. |
Action |
Verify TUXEDO installation. Contact BEA Customer Support. | |
6645 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6646 |
ERROR: Could not set cipher suites, err = code | |
|
Description |
The process received the error 'code while initializing SSL. SSL reported this error while trying to set the supported SSL cipher suites list. |
Action |
Contact BEA Customer Support. | |
6647 |
ERROR: Could not set SSL callback, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the cipher callback function. |
Action |
Contact BEA Customer Support. | |
6648 |
ERROR: Could not set SSL callback, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the certificate verification callback function. |
Action |
Contact BEA Customer Support. | |
6649 |
ERROR: Could not set SSL non blocking IO, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while setting the SSL connection not to block. |
Action |
Contact BEA Customer Support. | |
6650 |
ERROR: Could not set SSL callback, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the SSL read callback function. |
Action |
Contact BEA Customer Support. | |
6651 |
ERROR: Could not set SSL callback, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the write callback function. |
Action |
Contact BEA Customer Support. | |
6652 |
ERROR: Could not create random seed, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while initializing the random seed. |
Action |
Contact BEA Customer Support. | |
6653 |
ERROR: Could not set cryptographic strength, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the strength of the cryptographic function. |
Action |
Contact BEA Customer Support. | |
6654 |
ERROR: Could not delete SSL context, err = code | |
|
Description |
The process received the unexpected error 'code' while deleting the SSL context. |
Action |
Contact BEA Customer Support. | |
6655 |
ERROR: Could not close private key, err = code | |
|
Description |
The process received the error 'code' while trying to close the private key. |
Action |
This error indicates an internal problem . Contact BEA Customer Support. | |
6656 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6657 |
ERROR: Could not copy SSL context, err = code | |
|
Description |
The process received the error 'code' while trying to copy the SSL context. This could occur because of memory allocation errors, incorrect certificate rules files, or a certificate lookup failure. |
Action |
Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device. Also verify that the certificate files are intact and correct. | |
6658 |
ERROR: Could not set SSL callback info, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the cipher negotiation callback function. |
Action |
Contact BEA Customer Support. | |
6659 |
ERROR: Could not set SSL callback info, err = code | |
|
Description |
The process received the error 'code' while initializing SSL. SSL reported this error while trying to set the certificate reference callback function. |
Action |
Contact BEA Customer Support. | |
6660 |
ERROR: Could not get admin key, err = code | |
|
Description |
The process encountered the error 'code' when attempting to get the admin key. |
Action |
Contact BEA Customer Support. | |
6661 |
ERROR: Could not initiate decryption of admin key, errno = code | |
|
Description |
The process could not initialize the decryption of the administration key because of the error 'code'. |
Action |
Contact BEA Customer Support. | |
6662 |
ERROR: Could not decrypt admin key, errno = code | |
|
Description |
The process received an error 'code' while attempting to decrypt a received admin key. |
Action |
Contact BEA Customer Support. | |
6663 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6664 |
ERROR: Could not initialize public key infrastructure, err = code | |
|
Description |
The process received the error 'code' while trying to initialize the public key infrastructure of SSL. |
Action |
Verify the TUXEDO installation. Contact BEA Customer Support. | |
6665 |
ERROR: Could not open private key, err = code | |
|
Description |
The process received the error 'code' while trying to open the private key. |
Action |
Verify the name and directory in which the private key is stored. | |
6666 |
ERROR: Key has been tampered | |
|
Description |
During initialization of the process, the SSL subsystem detected that a private key has been tampered with. |
Action |
Contact your certificate authority or BEA Customer Support. | |
6667 |
ERROR: Trust relationship of this key is invalid | |
|
Description |
During initialization of the process, the SSL subsystem detected that a trust relationship for a private key is no longer valid. |
Action |
Contact your certificate authority or BEA Customer Support. | |
6668 |
ERROR: Principal is known to be untrusted | |
|
Description |
During initialization of the process, the SSL subsystem detected a known untrusted principal. This occurred while opening a private key. |
Action |
Contact your certificate authority or BEA Customer Support. | |
6669 |
ERROR: Unrecognized critical extension | |
|
Description |
During initialization of the process, the SSL subsystem detected an unrecognized critical extension of SSL. This occurred while opening a private key. |
Action |
Contact your certificate authority or BEA Customer Support. | |
6670 |
ERROR: Key is valid, but expired | |
|
Description |
During initialization of the process, the SSL subsystem detected an expired private key. This occurred while opening a private key. |
Action |
Contact your certificate authority or BEA Customer Support. | |
6671 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6672 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6673 |
ERROR: Could not get private key certificate info, err = code | |
|
Description |
The process received the error 'code' while trying to get information from the private key certificate. |
Action |
Contact your certificate authority or BEA Customer Support. | |
6674 |
ERROR: Could not add SSL certificate, err = code | |
|
Description |
The process received the error 'code' while adding the SSL certificate to the current context. |
Action |
Contact BEA Customer Support. | |
6675 |
ERROR: Could not get private key info, err = code | |
|
Description |
The process received the error 'code' while trying to get information from the private key. |
Action |
Contact your certificate authorith or BEA Customer Support. | |
6676 |
ERROR: Could not set SSL private key, err = code | |
|
Description |
The process received the error 'code' while trying to register the SSL private key for the user's local identity. |
Action |
Contact BEA Customer Support. | |
6677 |
ERROR: Memory allocation failure, size = val | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6678 |
ERROR: Cannot not send SSL message, err = code | |
|
Description |
The process received the error 'code' while attempting to send a message. This may occur due to network errors. |
Action |
Verify that the remote process has not exited and its host is still reachable. | |
6679 |
ERROR: Unknown SSL cipher | |
|
Description |
The process received an error that the SSL cipher is unknown. The cipher was negotiated between client and server, but it does not match any ciphers supported by the installed TUXEDO SSL subsystem. |
Action |
Verify TUXEDO installation and contact BEA Customer Support. | |
6680 |
ERROR: Could not get SSL cipher suite info, err = code | |
|
Description |
The process received the error 'code' while sttempting to look up the negotiated cipher. The cipher was negotiated between the client and the server. |
Action |
Contact BEA Customer Support. | |
6681 |
ERROR: Negotiated cipher val is not exportable | |
|
Description |
The cipher 'val' that was negotiated cannot be exported. |
Action |
Verify the TUXEDO SSL installation. Contact BEA Customer Support. | |
6682 |
ERROR: Negotiated cipher strength exceeds maximum allowed | |
|
Description |
The negotiated cipher exceeds the maximum strength allowed. |
Action |
Change the maximum strength setting in UBBCONIFG or DMCONFIG. | |
See Also |
the | |
6683 |
ERROR: negotiated cipher strength is too low | |
|
Description |
The negotiated cipher strength is less than the minimum strength required. |
Action |
Change the minimum encryption strength setting. | |
See Also |
the | |
6684 |
ERROR: Cipher suite is not supported | |
|
Description |
The negotiated cipher suite is not supported by the SSL package. |
Action |
Contact BEA Customer Support. | |
6685 |
ERROR: Cannot get SSL peer certificate chain length, err = val | |
|
Description |
The process received the error 'val' while trying to get the number of certificates in the SSL peer certificate chain. |
Action |
Contact your certificate authority or BEA Customer Support. | |
6686 |
ERROR: Cannot get SSL peer certificate, err = code | |
|
Description |
The process received the error 'code' while attempting to validate the client that is connecting to it. The server side was unable to get the client side certificate. |
Action |
Verify that the client side has authenticated itself. | |
6687 |
ERROR: SSL connection peer certificate not present | |
|
Description |
The peer certificate for this SSL connection was missing. |
Action |
Verify that the client has authenticate itself. | |
6688 |
ERROR: Cannot get peer certificate email extension, err = code | |
|
Description |
The process received the error 'code' while trying to get the user's email extension from the peer certificate. This occurred duing the certificate authentication. |
Action |
Add the email extension to the certificate. | |
6689 |
ERROR: Peer certificate email extension is too long | |
|
Description |
The user's email extension, extracted from the peer certificate, is longer than the supported length. |
Action |
Shorten the user's email extension in the certificate. | |
6690 |
ERROR: SSL certificate chain not present in SSL Handshake | |
|
Description |
During an SSL Handshake operation, the process was not presented with an SSL certificate chain by teh remote client side program. |
Action |
Ensure that your application is configured so that remote sites will properly present their certificates to the local TUXEDO application. Contact your certificate authority or BEA Customer Support. | |
6691 |
ERROR: SSL certificate not present in SSL Handshake | |
|
Description |
During an SSL Handshake operation, the process detected that an SSL certificate was missing from the certificate chain that was presented to it by the remote application. |
Action |
Examine the user log for a prior message indicating a more exact cause of the error. Ensure that all certificates in the certificate chain are accessible to the application. Contact your certificate authority or BEA Customer Support. | |
6692 |
ERROR: failed to extract version from SSL CA certificate | |
|
Description |
An error occurred when trying to determine the version of an X.509 certificate for a Certificate Authority. |
Action |
Ensure that the certificate for the Certificate Authorities in your certificate are valid certificates. Contact your certificate authority or BEA Customer Support. | |
6693 |
ERROR: SSL CA certificate contains no BasicConstraints extension | |
|
Description |
A certificate for a Certificate Authority was found to contain no BasicConstraints extension as is required for X.509 version 3 certificates. |
Action |
Ensure the certificates for the Certificate Authorities in your certificate chain are valid and properly conforming. Contact your certificate authority or BEA Customer Support. | |
6694 |
ERROR: failed to retrieve BasicConstraints from SSL CA certificate | |
|
Description |
An error occurred when trying to retrieve the BasicConstraints information from an X.509 certificate for a Certificate Authority. |
Action |
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid certificates. Contact your Certificate Authority or BEA Customer Support. | |
6695 |
ERROR: the BasicConstraints extension in an SSL CA certificate is not marked as critical | |
|
Description |
The BasicConstraints extension in a certificate for a Certificate Authority was not marked as a critical extension, as is required for X.509 version 3 certificates. |
Action |
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid and properly conforming. Contact your Certificate Authority or BEA Customer Support. | |
6696 |
ERROR: failed to parse BasicConstraints extension in an SSL CA certificate | |
|
Description |
An error occurred when trying to parse BasicConstraints information from an X.509 certificate for a Certificate Authority. |
Action |
Ensure that the certificates for the Certificate Authorities in your certificate chain are valid. Contact your Certificate Authority or BEA Customer Support. | |
6697 |
ERROR: the BasicConstraints extension in an SSL CA certificate is not marked as a CA | |
|
Description |
The BasicConstraints extension in a certificate for a Certificate Authority was not marked to indicate that the certificate does in fact belong to a Certificate Authority. |
Action |
Ensure that the certificate for the Certificate Authorities in your certificate chain are valid and properly conforming. Contact your Certificate Authority or BEA Customer Support. | |
6698 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to allocate memory dynamically from the operating system using |
Action |
Make sure the operation system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Also increate the space on the swap device. | |
See Also |
See the For UNIX system, see the For Microsoft Windows systems, see the Microsoft Visuall C++ online help. | |
6699 |
WARN: Peer validation failed on server at svr_name | |
|
Description |
The common name OID contains in the server peer certificate did not match the hostname in the object reference. The hostname in the object reference has the value 'svr_name'. |
Action |
None. If you wish to eliminate the warning, modify the server peer certificate to contain the correct hostname in the common name OID. |