BEA Tuxedo 7.1 System Messages LIBTUX Catalog 5000-5099


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| Messages \| Catalog List \| Previous \| Next

LIBTUX Messages 5000-5099

5001

ERROR: No space in Bulletin Board for additional AOM entries

Description

An attempt to allocate a free entry in the Bulletin Board for the Active Object Map has failed. The Bulletin Board is full.

Action

Re-configure the application to increase the size of the table by setting the MAXOBJECTS parameter in the RESOURCES section.

See Also

ubbconfig(5)

5003

ERROR: Failed to initialize AOM

Description

The system was unable to initialize the Active Object Map.

Action

Normally, there is a message in the log that provides more detail on the initialization failure. If not, contact BEA Customer Support.

5004

WARN: USEM[val] owned by val, but not locked

Description

Either the machine does not have the proper atomic increment for the user-level semaphore, or there are too many signals coming to the process too quickly.

Action

Please contact BEA Customer Support.

5005

WARN: USEM[val] lock appears stuck: held by pid=val

Description

The process has held the lock on the Bulletin Board for a longer than normal period of time. The process could still be alive, but incorrectly holding the user-level semaphore.

Action

Check the status of the process that is holding the lock. It might be hung, or it is holding the lock for too long a period of time while doing work.

5006

ERROR: Unable to reset semaphore for sem val, errno val

Description

The BEA Tuxedo system was in the process of cleaning up a registry slot for a process. While cleaning the registry, the semaphore used for that process had to be reset. The semaphore operation semctl failed.

Action

Please contact BEA Customer Support.

5007

ERROR: Memory allocation failure.

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while processing the host name associated with a Tuxedo context.

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 and/or swap space on the machine.

5008

ERROR: Memory allocation failure.

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to processing an incoming 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 and/or swap space on the machine.

5009

ERROR: MAXOBJECTS is 0: No methods allowed.

Description

An operation related to object methods was executed but no objects are configured.

Action

Re-configure the application to increase the size of the table by setting the MAXOBJECTS parameter in the RESOURCES section.

See Also

ubbconfig

5010

ERROR: Received unrecognized message type - sending failure reply

Description

The server received an invalid service request message. It will be ignored and a failure reply will be sent to the requestor.

Action

Please contact BEA Customer Support.

5011

ERROR: One way method was not executed

Description

An attempt to execute a one way method failed. No notification will go back to the client.

Action

No action is needed.

5012

ERROR: Memory allocation failure.

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to process an out-going 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 and/or swap space on the machine.

5013

ERROR: Memory allocation failure.

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to process a 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 and/or swap space on the machine.

5014

ERROR: Memory allocation failure.

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to process a 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 and/or swap space on the machine.

5015

ERROR: Memory allocation failure

Description

An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to process a 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 and/or swap space on the machine.

5019

ERROR: [Unable to open the *INTERFACES section table]

Description

A BEA Tuxedo system internal function was used to retrieve interface information from the interfaces table, but the open failed.

Action

Please contact BEA Customer Support.

5020

ERROR: [Unable to read information from the *INTERFACES section table]

Description

A BEA Tuxedo system internal function was unable to read the INTERFACES section of the TUXCONFIG file.

Action

Please contact BEA Customer Support.

5021

WARN: Could not lock USEM[val]

Description

The BRIDGE was unable to lock the Bulletin Board. Other processing will continue.

Action

No action required.

5022

ERROR: Old M3 request received by new server process

Description

Method requests received by an M3 server that were routed via the Active Object Map (that is, not stateless) must be processed by same process to which the routing function sent the request. The original server died and this is a restarted server is rejecting an old enqueued message.

Action

No action required.

5001	ERROR: No space in Bulletin Board for additional AOM entries
	Description	An attempt to allocate a free entry in the Bulletin Board for the Active Object Map has failed. The Bulletin Board is full.
	Action	Re-configure the application to increase the size of the table by setting the `MAXOBJECTS` parameter in the `RESOURCES` section.
	See Also	`ubbconfig`(5)
5003	ERROR: Failed to initialize AOM
	Description	The system was unable to initialize the Active Object Map.
	Action	Normally, there is a message in the log that provides more detail on the initialization failure. If not, contact BEA Customer Support.

5004	*WARN: USEM[val] owned by val, but not locked*
	Description	Either the machine does not have the proper atomic increment for the user-level semaphore, or there are too many signals coming to the process too quickly.
	Action	Please contact BEA Customer Support.

5005	WARN: USEM[val] lock appears stuck: held by pid=val
	Description	The process has held the lock on the Bulletin Board for a longer than normal period of time. The process could still be alive, but incorrectly holding the user-level semaphore.
	Action	Check the status of the process that is holding the lock. It might be hung, or it is holding the lock for too long a period of time while doing work.

5006	ERROR: Unable to reset semaphore for sem val, errno val
	Description	The BEA Tuxedo system was in the process of cleaning up a registry slot for a process. While cleaning the registry, the semaphore used for that process had to be reset. The semaphore operation `semctl` failed.
	Action	Please contact BEA Customer Support.

5007	ERROR: Memory allocation failure.
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while processing the host name associated with a Tuxedo context.
	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 and/or swap space on the machine.

5008	ERROR: Memory allocation failure.
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while trying to processing an incoming 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 and/or swap space on the machine.

5009	ERROR: MAXOBJECTS is 0: No methods allowed.
	Description	An operation related to object methods was executed but no objects are configured.
	Action	Re-configure the application to increase the size of the table by setting the `MAXOBJECTS` parameter in the `RESOURCES` section.
	See Also	`ubbconfig`
5010	ERROR: Received unrecognized message type - sending failure reply
	Description	The server received an invalid service request message. It will be ignored and a failure reply will be sent to the requestor.
	Action	Please contact BEA Customer Support.

5011	ERROR: One way method was not executed
	Description	An attempt to execute a one way method failed. No notification will go back to the client.
	Action	No action is needed.

5012	ERROR: Memory allocation failure.
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while trying to process an out-going 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 and/or swap space on the machine.

5013	ERROR: Memory allocation failure.
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while trying to process a 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 and/or swap space on the machine.

5014	ERROR: Memory allocation failure.
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while trying to process a 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 and/or swap space on the machine.

5015	ERROR: Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using `malloc()` failed while trying to process a 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 and/or swap space on the machine.

5019	*ERROR: [Unable to open the INTERFACES section table]**
	Description	A BEA Tuxedo system internal function was used to retrieve interface information from the interfaces table, but the open failed.
	Action	Please contact BEA Customer Support.

5020	*ERROR: [Unable to read information from the INTERFACES section table]**
	Description	A BEA Tuxedo system internal function was unable to read the `INTERFACES` section of the `TUXCONFIG` file.
	Action	Please contact BEA Customer Support.

5021	*WARN: Could not lock USEM[val]*
	Description	The `BRIDGE` was unable to lock the Bulletin Board. Other processing will continue.
	Action	No action required.

5022	ERROR: Old M3 request received by new server process
	Description	Method requests received by an M3 server that were routed via the Active Object Map (that is, not stateless) must be processed by same process to which the routing function sent the request. The original server died and this is a restarted server is rejecting an old enqueued message.
	Action	No action required.