GP Messages 1400-1499

1431

ERROR: Memory allocation error

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to send or receive a network message.

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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1432

ERROR: Memory allocation error

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to send or receive a network message.

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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1433

ERROR: Memory allocation error: val

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to receive a network message.

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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1434

ERROR: Memory allocation error: string

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to receive a network message. string may provide further information about the 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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1435

ERROR: Could not expand multiple messages

Description

While processing network messages, an internal error occurred.

Action

Contact BEA Customer Support.

1436

ERROR: Memory allocation error: val

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to receive a network message. string may provide further information about the 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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1437

ERROR: Memory allocation error: val

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to receive a network message. string may provide further information about the 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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1438

WARN: _e_dl_load(val): dynloading code not yet ported to this platform

Description

The dynamic loading feature has not been ported to the current platform.

Action

Contact BEA Customer Support.

1440

ERROR: Invalid flags passed to _fpresend232

Description

Internal error during the message presend of an FML buffer containing embedded FML buffers or pointers to FML buffers.

Action

Contact BEA Customer Support.

1441

ERROR: Memory allocation failure resynchronizing FML32 buffer

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to prepare an FML32 for transport in _fpresend32.

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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1444

ERROR: Memory allocation failure in FML32 recursion check

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to prepare an FML32 for transport in _fpresend32.

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. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1445

ERROR: Recursion detected in an embedded FML/FML32 buffer

Description

An embedded FML buffer or an FML buffer referenced in a FLD_PTR field contains a reference to an FML buffer above it in the tree.

Action

Review the FML buffer being sent and eliminate any recursive references. For example, if FML buffer A contains a FLD_FML32 field into which FML buffer B has been copied and buffer B contain a FLD_PTR field which points to buffer A then buffer A contains a recursive reference that must be resolved before the buffer can be sent to another Tuxedo process.

1450

WARN: pif: Unable to realize PIF Registry plugin

Description

The framework was asked to realize/load a plug-in and an internal error occurred.

Action

This is an internal error with no associated user action. Check the userlog for additional information to determine the proper action to be taken.

1451

WARN: pif: Init of PIF Registry plugin failed (PIF_PROFILE='val'), error error

Description

An internal error erroroccurred while trying to initialize the Registry plugin with PIF_PROFILE val. The framework was not able to realize/load it.

Action

This is an internal error. Check the userlog for additional information and contact BEA Customer Support.

1452

WARN: pif: realize of interface 'val' (implId='ID') failed, error error

Description

An internal error erroroccurred while trying to realize interface val implId ID. The framework was not able to realize/load it.

Action

This is an internal error. Check the userlog for additional information and contact BEA Customer Support.

1456

ERROR: Failed to acquire a mutex in the encryption subsystem

Description

An internal error occurred in the encryption subsystem while trying to lock a mutex.

Action

Contact BEA Customer Support.

1457

ERROR: Failed to acquire a mutex in the encryption subsystem

Description

An internal error occurred in the encryption subsystem while trying to lock a mutex.

Action

Contact BEA Customer Support.

1458

ERROR: Failed to acquire a mutex in the encryption subsystem

Description

An internal error occurred in the encryption subsystem while trying to lock a mutex.

Action

Contact BEA Customer Support.

1459

ERROR: Failed to acquire a mutex in the encryption subsystem

Description

An internal error occurred in the encryption subsystem while trying to lock a mutex.

Action

Contact BEA Customer Support.

1460

ERROR: Unable to digest buffer (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to digest a buffer. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

_ec_sec_key_digest

1461

ERROR: Unable to encrypt digest (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to public key encrypt a digest. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

_ec_sec_key_encrypt_digest

1462

ERROR: Unable to decrypt digest (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to public key decrypt a digest. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

_ec_sec_key_decrypt_digest

1463

ERROR: Unable to encrypt session key (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to public key encrypt a session key. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

_ec_sec_key_encrypt_session_key

1464

ERROR: Unable to decrypt session key (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to public key decrypt a session key. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

_ec_sec_key_decrypt_session_key

1465

ERROR: Unable to DES encrypt bulk data (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to DES encrypt bulk data. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

tpseal, tpkey_open, tpexport

1466

ERROR: Unable to DES decrypt bulk data (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to DES decrypt bulk data. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

tpseal, tpkey_open, tpimport

1467

ERROR: Unable to DES3 encrypt bulk data (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to triple DES encrypt bulk data. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

tpseal, tpkey_open, tpexport

1468

ERROR: Unable to DES3 decrypt bulk data (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to triple DES decrypt bulk data. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

tpseal, tpkey_open, tpimport

1469

ERROR: Must use SHA1 hash algorithm with DSA signature algorithm

Description

DSA is not supported.

Action

Contact BEA Customer Support.

1470

ERROR: Unable to DSA encrypt digest (errorcode1/errorcode2)

Description

DSA is not supported.

Action

Contact BEA Customer Support.

1471

ERROR: Must use SHA1 hash algorithm with DSA signature algorithm

Description

DSA is not supported.

Action

Contact BEA Customer Support.

1472

ERROR: Unable to DSA decrypt digest (errorcode1/errorcode2)

Description

DSA is not supported.

Action

Contact BEA Customer Support.

1474

ERROR: Unable to RC2 encrypt bulk data (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to RC2 encrypt bulk data. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

tpseal, tpkey_open, tpexport

1476

ERROR: Unable to RC2 decrypt bulk data (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to RC2 decrypt bulk data. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

1477

ERROR: Unable to generate a DSA keypair (errorcode1/errorcode2)

Description

DSA is not supported.

Action

Contact BEA Customer Support.

1478

ERROR: Unable to decode RFC1113 encoded string (errorcode1/errorcode2)

Description

A fatal error occurred while attempting to decode an RFC1113 encoded string. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Make sure the input to tpimport is properly RFC1113 encoded. Check that your license file (${TUXDIR}/udataobj/lic.txt) has not been corrupted. Otherwise, contact BEA Customer Support.

See Also

tpimport

1479

ERROR: An error occurred in the encryption subsystem code (errorcode1/errorcode2)

Description

Unable to verify the signature on the license file. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Check that your license file (${TUXDIR}/udataobj/lic.txt) has not been corrupted. Also ensure that the last line of the license file is a blank line. Otherwise, contact BEA Customer Support.

1480

ERROR: Unable to encode RFC1113 encoded string (val/val)

Description

A fatal error occurred while attempting to RFC1113 encode a buffer. Save the values of errorcode1 and errorcode2 to give to technical support.

Action

Contact BEA Customer Support.

See Also

tpexport

1481

ERROR: tmroute failed, could not find routing criteria of val for buffer type val

Description

A routing_name was specified for a SERVICE entry in the UBBCONFIG file that does not appear in the ROUTING section, and the standard XML routing function is used (which requires a matching ROUTING entry).

Action

Correct and re-load the UBBCONFIG file or provide an application-specific routing function for XML typed buffers.

See Also

ubbconfig(5), typesw(5)

1482

ERROR: Routing field for 'val' null

Description

During data-dependent routing for a XML buffer, the specified routing_field value in the XML buffer was null for service.

Action

Make sure the routing field is correctly set for the XML buffer.

See Also

ubbconfig(5), typesw(5)

1483

ERROR: Unknown field type used for routing XML buffer

Description

During data-dependent routing of a XML typed buffer, an unknown field type was encountered for the routing field. This should not occur during normal system operation.

Action

Contact BEA Customer Support.

See Also

ubbconfig(5), typesw(5)

1484

ERROR: Cannot get routing data from XML buffer

Description

During data-dependent routing for a XML buffer, the specified routing_field value in the XML buffer was not found in the XML buffer. Either the routing field is not set correctly in the ROUTING section of the UBBCONFIG, or your XML buffer does not contain the routing data.

Action

Make sure the routing field is correctly set for the XML buffer, and check your XML buffer. See subsequent userlog messages from XML parser regarding to the problem with your XML buffer.

See Also

ubbconfig(5), typesw(5)

1485

ERROR: Routing field value for 'val' not valid

Description

While doing data-dependent routing on a XML typed buffer for the specified service, the routing field value did not match any of the ranges specified in the routing criteria and the criteria did not contain a wild-card pattern.

Action

Make sure the routing field value is valid. Correct the routing criteria in the RANGES value of the UBBCONFIG file.

See Also

ubbconfig(5), typesw(5)

1486

ERROR: Service val not available in group val

Description

While doing data-dependent routing on a XML typed buffer, the specified service is not offered in the specified group.

Action

Make sure that the routing criteria specified for the XML buffer type is correct, and ensure that service is advertised, but not suspended in group group.

1487

ERROR: No more valid characters in the buffer, XML_SAVE_WHITESPACES.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an error because there is no more valid characters left in the buffer.

Action

Check your XML document and system configuration.

1488

ERROR: No more valid characters in the buffer, XML_IGNORE_WHITESPACES.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an error because there is no more valid characters left in the buffer.

Action

Check your XML document and system configuration.

1489

ERROR: No more valid characters in the buffer, XML_IGNORE_WHITESPACES.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an error because there is no more valid characters left in the buffer.

Action

Check your XML document and system configuration.

1490

ERROR: No more valid characters in the buffer, XML_IGNORE_WHITESPACES.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an error because there is no more valid characters left in the buffer.

Action

Check your XML document and system configuration.

1491

ERROR: No more valid characters in the buffer, XML_IGNORE_WHITESPACES.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an error because there is no more valid characters left in the buffer.

Action

Check your XML document and system configuration.

1492

ERROR: No more valid characters in the buffer, XML_IGNORE_WHITESPACES.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an error because there is no more valid characters left in the buffer.

Action

Check your XML document and system configuration.

1493

ERROR: Internal error in the XML parser, wrong whitespace handling option val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error because of a wrong whitespace handling option, val.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1494

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error because of a wrong whitespace handling option, val.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1495

ERROR: Internal error in the XML parser, character code not found for character val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error because the character code not found for character val.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1496

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error because the character code not found for character val.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1497

ERROR: Internal error in the XML parser, character code not found for character val.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error because the character code not found for character val.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1498

INFO: Contact BEA Support.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error because the character code not found for character val.

Action

Check your XML document and system configuration. Contact BEA Customer Support.

1499

ERROR: Internal error in the XML parser, token val conversion failed.

Description

While parsing the XML typed buffer for data-dependent routing, the parser encountered an internal error when getting the character code of the token. The token conversion failed for token, token.

Action

Check your XML document and system configuration. Contact BEA Customer Support.