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 1500-1599

1509	ERROR: failed to get shared memory, errno = errno_number
	Description	A server attempted to create the shared memory used for the ACL cache and failed.
	Action	Check the configuration of shared memory on the system where the failure occurred. Increase the parameters to allow for more shared memory. The requirements can be reduced by setting MAXACLGROUPS and MAXACLCACHE lower.
	See Also	ubbconfig(5), TM_MIB(5)
1510	ERROR: failed to attach to shared memory, errno = errno_number
	Description	A server attempted to attach to the shared memory used for the ACL cache and failed.
	Action	Check the configuration of shared memory on the system where the failure occurred. Increase the parameters to allow for more shared memory. The requirements can be reduced by setting MAXACLGROUPS and MAXACLCACHE lower.
	See Also	ubbconfig(5), TM_MIB(5)
1511	WARN: [Semaphore appears stuck - currently held by pid]
	Description	While trying to lock a portion of the queue space (using a user-level semaphore), the process is unable to get the lock for a long period.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	ubbconfig(5), TM_MIB(5)
1512	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while performing ACL check.
	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.
1513	WARN: Unable to cleanup security files.
	Description	When the security files are updated, modified and deleted entries are not immediately deleted. Occasionally, these entries are cleaned up and one of these attempts failed.
	Action	No action required. The files will be cleaned up at a later time. This warning usually occurs when a cleanup was attempted when update activity was heavy.
1514	ERROR: Out of ACL cache entries.
	Description	When checking an access control list, the ACL cache ran out of entries. A permissions violation will be returned to the application.
	Action	Change the application configuration to allow for more entries in the cache (MAXACLCACHE which is set on a per-machine basis).
	See Also	ubbconfig(5), TM_MIB(5)
1515	WARN: Access control violation - user uid on LMID tried to access type name
	Description	A client attempted to access a service, event, or queue for which it was not granted access via an access control list. The user identifier (configured in the user or principal file), the machine, entity type, and entity name are printed.
	Action	No action required. The access fails with an error and an event is generated. Further action may be required on the part of the security administrator.
	See Also	ubbconfig(5), TM_MIB(5)
1516	INFO: .SysACLPerm: User uid on LMID tried to access type name
	Description	This is the event that is generated when a client has attempted to access a service, event, or queue for which it was not granted access via an access control list. The user identifier (configured in the user or principal file), the machine, entity type, and entity name are printed.
	Action	No action required. The access fails with an error and an event is generated. Further action may be required on the part of the security administrator.
	See Also	ubbconfig(5), TM_MIB(5)
1517	INFO: .SysMachineState: LMID state change to INACTIVE
	Description	The specified machine changed to a new state of INACTIVE. A complete listing of the current parameters are sent along in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
1518	INFO: .SysServerState: servername, group srvgrp, id srvid state change to state
	Description	This message indicates that the server specified above changed to a new state. A complete listing of the server attributes are sent in the posted buffer.
	Action	This is an informational message.
	See Also	EVENT_MIB(5), TM_MIB(5)
1519	ERROR: TUXCONFIG value (val) is longer than the allowed length of len
	Description	The value specified in the TUXCONFIG environment variable, val, is longer than the allowed size of len characters.
	Action	Correct the value of your environment variable.
	See Also	ubbconfig(5)
1520	ERROR: .SysTransactionHeuristicCommit: Transaction gtrid in group grpno
	Description	This message indicates that the database in the group specified above performed a heuristic commit on the transaction indicated in the message.
	Action	Check to make sure that the coordinator of the transaction is still up and running.
	See Also	EVENT_MIB(5), TM_MIB(5)
1521	ERROR: .SysTransactionHeuristicAbort: Transaction gtrid in group grpno
	Description	This message indicates that the database in the group specified above performed a heuristic abort on the transaction indicated in the message.
	Action	Check to make sure that the coordinator of the transaction is still up and running.
	See Also	EVENT_MIB(5), TM_MIB(5)
1523	ERROR: Unable to get APPDIR environment variable.
	Description	While reading the ACL information, the program was unable to get the APPDIR environment variable.
	Action	Normally, this variable is automatically set for both clients and servers based on the application configuration. Call BEA TUXEDO System Technical Support. Support.
1524	WARN: Cannot set high priority for 'sub'
	Description	On the Windows NT platform, the program was unable to set the priority class to HIGH_PRIORITY.
	Action	No action required.
1530	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system failed while trying to send a transaction 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.
1531	ERROR: Type switch buffer uninitialization routine failure
	Description	While receiving a message and freeing up a buffer, the buffer uninitialization function, _tmuninitbuf(), returned an error.
	Action	Check the buffer type switch to see that it is correctly set up (that the right uninitialization function is associated with the correct buffer type). If an application-defined buffer type, check the uninitialization function to see that it is coded correctly.
	See Also	buffer(3c), typesw(5)
1532	ERROR: Type switch buffer uninitialization routine failure
	Description	While freeing up a buffer in tpreturn(), the buffer uninitialization function, _tmuninitbuf(), returned an error.
	Action	Check the buffer type switch to see that it is correctly set up (that the right uninitialization function is associated with the correct buffer type). If an application-defined buffer type, check the uninitialization function to see that it is coded correctly.
	See Also	buffer(3c), typesw(5)
1533	ERROR: Type switch buffer uninitialization routine failure
	Description	While freeing up a buffer in tpreturn(), the buffer uninitialization function, _tmuninitbuf(), returned an error.
	Action	Check the buffer type switch to see that it is correctly set up (that the right uninitialization function is associated with the correct buffer type). If an application-defined buffer type, check the uninitialization function to see that it is coded correctly.
	See Also	buffer(3c), typesw(5)
1534	ERROR: Type switch buffer uninitialization routine failure
	Description	While freeing up a buffer in tpforward(), the buffer uninitialization function, _tmuninitbuf(), returned an error.
	Action	Check the buffer type switch to see that it is correctly set up (that the right uninitialization function is associated with the correct buffer type). If an application-defined buffer type, check the uninitialization function to see that it is coded correctly.
	See Also	buffer(3c), typesw(5)
1535	ERROR: Invalid Group-id to open RM
	Description	tpopen() or txopen() was called in a client that is not associated with a resource manager server group.
	Action	Don't call tpopen() or txopen() from the client, or configure the client to be associated with a group using tpinit().
	See Also	tpinit(3c)
1536	ERROR: Invalid Group-id to close RM
	Description	tpclose() or txclose() was called in a client that is not associated with a resource manager server group.
	Action	Do not call tpclose() or txclose() from the client, or configure the client to be associated with a group using tpinit().
	See Also	tpinit(3c)
1537	ERROR: tpclose called with ongoing transaction
	Description	tpclose() was called while within a global transaction (that is, tpbegin() or txbegin() was called).
	Action	The transaction must be completed via tpcommit() or tpabort() before calling tpclose().
	See Also	tpabort(3c), tpbegin(3c), tpclose(3c), tpcommit(3c)
1538	WARN: Could not lock Bulletin Board
	Description	The program was unable to get access to the BEA TUXEDO Bulletin Board (BB) within a reasonable amount of processing, due to race conditions with other processes trying to lock the BB. The associated operation will fail.
	Action	This should not occur often, if at all. It occurs during a high level of concurrent access by many processes. Re-try the operation.
1539	ERROR: Error getting Group Environment filename
	Description	While booting a server, the associated group entry could not be found so any group environment file will not be processed.
	Action	This indicates a problem in opening or reading the application configuration. Look for other messages in the event log indicating the problem.
	See Also	ubbconfig(5)
1540	ERROR: Error putting ENVFILE filename into environment
	Description	In the process of booting a server or starting a client, the ENVFILE specified in the GROUPS section of the configuration could not be accessed. The server will still be booted or the client will be started but the environment will not be modified.
	Action	Check the group environment file to see that it exists in the correct directory with the right name and with read permission. It may be necessary to shutdown the client or server and re-start it with the correct environment.
	See Also	ubbconfig(5)
1541	WARN: Invalid server pool option -p argument
	Description	The given argument is in an invalid format.
	Action	The format for the -p option is: -p[L][low-water][,[terminate_time]][: [high_water][,create_time]] Reformat argument to comply with the format for -p.
	See Also	servopts(5)
1542	ERROR: The -p option is valid only for SHM mode with load balancing
	Description	In order to use the server pool option -p, the application must be SHM mode and must have load balancing turned on.
	Action	Remove the -p option from the CLOPT for the affected server. Make sure the application is running in SHM mode. Remember that SHM mode applications should have no NETWORK section in the UBBCONFIG file and should have MODEL set to SHM. Turn load balancing on in the application by specifying LDBAL to Y in the RESOURCES section of the UBBCONFIG file.
	See Also	servopts(5)
1543	ERROR: The -p option is not valid for conversational servers
	Description	In order to use the server pool option -p, the server must not be conversational.
	Action	Remove the -p option from the CLOPT for the affected server. Make sure the server is not conversational by specifying CONV=N in the SERVERS section of the UBBCONFIG file for the affected server.
	See Also	servopts(5)
1544	ERROR: The -p option is valid only for MSSQ servers
	Description	In order to use the server pool option -p, the server must be in an MSSQ set where MAX is greater than 1.
	Action	Remove the -p option from the CLOPT for the affected server. Make sure the server is in an MSSQ set by supplying a RQADDR for the server in the SERVERS section of the UBBCONFIG file. Make sure that the value of MAX in the SERVERS section of the UBBCONFIG is greater than 1 for the affected server.
	See Also	servopts(5)
1545	ERROR: Invalid -p values lw,tt:hw,ct
	Description	One of the values lw, tt, hw, or ct is incorrect.
	Action	The format for the -p option is: -p[L][low-water][,[terminate_time]][: [high_water][,create_time]] Reformat argument to comply with the format for -p.
	See Also	servopts(5)
1546	ERROR: Cannot lock Bulletin Board
	Description	While testing the server pool, an error occurred while attempting to lock the bulletin board.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	servopts(5)
1547	ERROR: Fatal error receiving requests, shutting server down
	Description	The system detected a fatal error during the reception on incoming service requests.
	Action	This message is supplied when the server has found a condition which does not allow the server to continue operation. The most common causes are lack of memory and corrupted memory, but other conditions could also cause this behavior. The server will shut itself down. If you believe that your system has enough memory and that the memory in the server has not been corrupted, contact your BEA TUXEDO system Technical Support.
1548	ERROR: Unable to send unsolicited message to process (pid)
	Description	While sending an unsolicited message to process pid, an error occurred.
	Action	The most common cause of this error message is that the recipient of the unsolicited message has died. Check to see if pid is still running, and if it is, contact your BEA TUXEDO system Technical Support.
1549	ERROR: Invalid USIGNAL parameter in Bulletin Board
	Description	While sending an unsolicited message, an invalid value of USIGNAL was found.
	Action	If the NOTIFY option in the RESOURCES section of the UBBCONFIG file is SIGNAL, then USIGNAL must be SIGUSR1 or SIGUSR2. Other values are not recognized by the BEA TUXEDO system. Contact your BEA TUXEDO system Technical Support.
1550	ERROR: Unable to send signal to process, pid = pid
	Description	NOTIFY was set to SIGNAL, but while sending an unsolicited message to the process with process id pid, we could not properly signal the process.
	Action	Contact your BEA TUXEDO system Technical Support.
1551	ERROR: Cannot find DBBL
	Description	While sending an unsolicited message to a process on a remote machine, the system encountered an error while attempting to find the DBBL.
	Action	This may be a temporary failure, or a failure caused by a partitioned application. If the application is partitioned, then unsolicited messages may not work properly. If your application is not partitioned, contact your BEA TUXEDO system Technical Support.
1552	ERROR: Cannot perform operation, DBBL is migrating
	Description	While sending an unsolicited message to a process on a remote machine, the system discovered that the DBBL was migrating.
	Action	During master migration, unsolicited messages may not be sent. Retry the operation when the DBBL is not migrating.
1553	ERROR: Unable to find WSH (pid)
	Description	While sending an unsolicited message to a workstation client, the system could not find the corresponding workstation handler.
	Action	Unsolicited messages to workstation clients pass through the workstation handler. An error occurs if the workstation handler for a given client cannot be found. Contact your BEA TUXEDO system Technical Support.
1554	ERROR: WSH (pid) should not be ignoring unsolicited messages
	Description	While sending an unsolicited message to a workstation client, the system found that the workstation handler was in an invalid state.
	Action	Contact your BEA TUXEDO system Technical Support.
1555	ERROR: Unsolicited message encoding/decoding failed (routine)
	Description	While encoding or decoding an unsolicited message, an error occurred.
	Action	The value in routine will give the name of the function which failed during the encoding and decoding procedure. Contact your BEA TUXEDO system Technical Support with the values from routine.
1556	ERROR: Cannot receive TPACK because MSSQ is specified but REPLYQ is N
	Description	In order to receive acknowledgment of delivery of an unsolicited message from a server in an MSSQ set, the REPLYQ parameter of that server must be set to Y.
	Action	Change the value of REPLYQ for the affected server to Y in the SERVERS section of the UBBCONFIG file. Do not use the TPACK flag for tpnotify(3c) if you cannot specify REPLYQ Y in an MSSQ set.
1557	ERROR: Memory allocation failure reason
	Description	While attempting to encode or decode an unsolicited message the system ran out of memory.
	Action	Check the memory on the affected system. If it seems that there should be enough memory for this operation, contact your BEA TUXEDO system Technical Support.
1558	ERROR: Cannot create call descriptor for unsolicited message, tperrno=tperrno
	Description	While generating a descriptor handle for an unsolicited message, an error occurred with tperrno tperrno.
	Action	Check the memory on the affected system. If it seems that there should be enough memory for this operation, contact your BEA TUXEDO system Technical Support.
1559	ERROR: Failed to receive ACK for unsolicited message, tperrno=tperrno
	Description	While waiting for acknowledgment of receipt of an unsolicited message, an error occurred with tperrno tperrno.
	Action	The recipient of the unsolicited message may or may not have received the unsolicited message. Examine tperrno for more information on the cause of the failure.
1560	ERROR: Failed to cancel unsolicited message call descriptor, tperrno=tperrno
	Description	If an error occurs while getting an acknowledgment from tpnotify, the system attempts to tpcancel the request. If the tpcancel fails, then this message will appear.
	Action	The recipient of the unsolicited message may or may not have received the unsolicited message. Examine tperrno for more information on the cause of the failure. Contact your BEA TUXEDO system Technical Support.
1561	ERROR: Failed to send ACK to notifier, tperrno=tperrno
	Description	The process which received an acknowledged notification event was unable to return the acknowledgment.
	Action	Examine tperrno for more information on the cause of the failure. Contact your BEA TUXEDO system Technical Support.
1562	WARN: Unable to open MACHINE ENVFILE envfile for reading
	Description	The as400 machine could not open envfile for reading.
	Action	Make sure envfile exists and that the process has sufficient permission for reading the file.
1564	ERROR: Unable to determine license level
	Description	An error occurred while retrieving the current license attributes.
	Action	Check the log for prior messages indicating the cause of the problem. Normally, it means that the product has not been licensed properly.
1565	ERROR: Application attempted to start a transaction but transactions are not licensed
	Description	You do not have a license to use TUXEDO System/T transactions.
	Action	Purchase a license for TUXEDO System/T transactions.
1566	ERROR: Unable to set type switch index
	Description	An attempt to check a buffer type or subtype failed during a call to tpalloc() because the type or subtype is not in the buffer type switch.
	Action	Check that the type and/or subtype is listed in the file tmtypesw.c.
1572	ERROR: Bad conversational sequence number
	Description	Conversations are sequenced in order to provide protection. One of the conversational messages arrived out of order. The conversation has been disconnected, and if a transaction was active, it has been set to the ABORTONLY state.
	Action	Look at the userlog to determine whether or not the BRIDGE has given up sending any messages to a message queue. If it has, the operating system may need to be tuned to properly handle a high volume of messages. This problem may also be alleviated by using compression. This error may also occur when the BRIDGE is failing over to a new network link or failing back to an high priority link.
1576	INFO: Command line domainid identification disabled
	Description	The -C option of the server command line has been disabled.
	Action	Contact your BEA TUXEDO system Technical Support.
1577	ERROR: Service service not available in group group
	Description	This error is occurring in the _froute32 function for FML32. The service to which this buffer has been routed does not exist in the group.
	Action	Ensure that the routing criteria in the UBBCONFIG file is correct.