Previous Next  

LIBTUX Messages 1100-1199


1100

ERROR: Cannot send a message to a site with an unknown release, release

Description

The BEA TUXEDO system is trying to convert a message to the message format of an unknown release: release. Interoperability allows a single application to have multiple (two) releases of the BEA TUXEDO system exist on different nodes and interoperate with one another. The conversion is done by either the sender, if it has the latest software, or the receiver.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

BEA TUXEDO Administrator's Guide

1104

ERROR: Memory allocation failure

Description

An attempt dynamically to allocate memory from the operating system using malloc() failed while converting Bulletin Board data to the BEA TUXEDO system Release 4.1 format.

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.

1108

ERROR: BBL not available on requested lmid (site)

Description

The calling process failed in tpbroadcast(3c) while trying to get the server table entry of the BBL on LMID site from the Bulletin Board. This is most likely due to the fact that the BBL on LMID site is not running.

Action

Boot the BBL on LMID site.

See Also

tpbroadcast(3c)

1109

ERROR: Could not retrieve BBL from specified lmid (site)

Description

The calling process failed in tpbroadcast(3c) while trying to get the server table entry of the BBL on LMID site from the Bulletin Board.

Action

Consult your BEA TUXEDO system Technical Support.

See Also

tpbroadcast(3c)

1114

ERROR: Unsolicited signal handler unable to get BB parameters

Description

The calling process failed to get from the Bulletin Board the signal to be used for signal-based notification. This error may have occurred while the client was attempting to join the application, using tpinit(3c), or while making an ATMI call prior to joining the application, or if the system the client is running on does not support reliable signals.

Action

Parse through the user log to see if there are other messages related to this failure. If so, refer to the appropriate system messages. Otherwise, consult your BEA TUXEDO system Technical Support.

See Also

tpinit(3c), ubbconfig(5)

1115

ERROR: Invalid USIGNAL parameter in BB

Description

The calling process retrieved an invalid signal number from the Bulletin Board. This signal was to be used for signal-based notification.

Action

Parse through the userlog to see if there are other messages related to this failure. If so, refer to the appropriate system messages. Otherwise, consult your BEA TUXEDO system Technical Support.

1117

ERROR: Unable to check for unsolicited messages, tperrno = tperrno

Description

The calling process failed while checking for an unsolicited message upon receipt of a signal indicating that an unsolicited message had arrived. tperrno is set to the TUXEDO System/T error code that was returned by the system after trying to get the unsolicited message.

Action

tperrno is most likely set to TPESYSTEM or TPEOS. In this case, parse through the userlog to find the exact nature of the failure as described in another message.

See Also

tpchkunsol(3c)

1118

ERROR: Unable to check for unsolicited messages, tperrno = tperrno

Description

The calling process failed while checking for unsolicited messages. tperrno is set to the BEA TUXEDO system error code that was returned by the system after failing to check for unsolicited messages.

Action

tperrno is most likely set to TPESYSTEM or TPEOS. In this case, parse through the userlog to find the exact nature of the failure as described in another message.

See Also

tpchkunsol(3c)

1119

ERROR: tpsetunsol() not called, dropping unsolicited message

Description

The calling process failed to set the method of handling unsolicited messages prior to receiving its first unsolicited message. The unsolicited message will therefore be dropped since the system does not know what to do with it.

Action

Make sure the calling process calls tpsetunsol(3c) as soon as it joins the application.

See Also

tpchkunsol(3c), tpsetunsol(3c)

1122

ERROR: No space in Bulletin Board

Description

The calling process failed to join the application due to the lack of space in the registry table portion of the Bulletin Board.

Action

If the calling process is an application client, the administrator will need to increase MAXACCESSERS in the RESOURCES section of the configuration file. If the calling process is a server, the administrator will need to increase MAXACCESSERS and/or MAXSERVERS in the RESOURCES section of the configuration file. Note that MAXACCESSERS specifies the maximum number of processes that can have access to a Bulletin Board on a particular machine at any one time. MAXSERVERS specifies the maximum number of servers to be accommodated by the entire application at any one time.

See Also

ubbconfig(5)

1187

ERROR: Invalid parameter passed to internal routine

Description

One of the internal routines to manage TUXEDO System/T data structures received an invalid parameter. This should not occur during normal system operation.

Action

Contact your BEA TUXEDO system Technical Support.

See Also

tmconfig(1)

1198

ERROR: Cannot detach: operating system error: errno = errno_val.

Description

The application is running with the TMPROTECTED SYSTEM_ACCESS value. Detaching from the bulletin board failed.

Action

Check the errno_val to determine why the detach failed.

1199

ERROR: Cannot re-attach: operating system error: errno = errno_val.

Description

The application is running with the TMPROTECTED SYSTEM_ACCESS value. The client or server was unable to re-attach to the bulletin board. This probably indicates that the application was shut down (abnormally) while the client or server was not attached.

Action

Check the errno_val to determine the reason for the failure. Check with the administrator to see if the application was shut down.

 

Back to Top Previous
Contact e-docsContact BEAwebmasterprivacy