[Top] [Prev] [Next] [Bottom]

11. LIBTUX Messages 1400-1499

1401	WARN: tpforward tpacall failure errcode
	Description	A service routine's `tmforward()` request failed because an underlying `tpacall()` failed. The error code from `tpacall()` is displayed as part of this message. This userlog message is issued because control will not return to the service routine. Instead, the process invoking the service routine will receive a TPESVCFAIL return code.
Action	Diagnose this problem based on the error return code shown in the userlog message. One likely cause is that the service being forwarded to is not available.
See Also	`tpacall`(3c), `tpforward`(3c)
1406	ERROR: Memory allocation failure within interoperability processing
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while doing interoperability processing.
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.
See Also	`malloc`(3) in UNIX System reference manuals
1407	WARN: TMDEBUG regular expression invalid. Ignoring regular expression.
	Description	A system debugging enabled binary is being used, and the debugging value provided via the environment contains an invalid regular expression.
Action	Contact your BEA TUXEDO system Technical Support.
1409	ERROR: Suspended client attempting to generate new request
	Description	A suspended client attempted to inject new work into the domain. Clients are suspended by the application administrator using either the /AdminGUI or /AdminAPI.
Action	Contact your application administrator to determine why the client was suspended and when they might expect to be unsuspended.
See Also	Administering the BEA TUXEDO System, BEA TUXEDO Administrator's Guide to the Web-Based GUI, `tpacall`(3c), `tpcall`(3c), `MIB`(5), `TM_MIB`(5)
1410	ERROR: Suspended client attempting to generate new request
	Description	A suspended client attempted to inject new work into the domain. Clients are suspended by the application administrator using either the /AdminGUI or /AdminAPI.
Action	Contact your application administrator to determine why the client was suspended and when they might expect to be unsuspended.
See Also	Administering the BEA TUXEDO System, BEA TUXEDO Administrator's Guide to the Web-Based GUI, `tpacall`(3c), `tpcall`(3c), `MIB`(5), `TM_MIB`(5)
1411	ERROR: Suspended client attempting to generate new conversation
	Description	A suspended client attempted to start a new conversation. Clients are suspended by the application administrator using either the /AdminGUI or /AdminAPI.
Action	Contact your application administrator to determine why the client was suspended and when they might expect to be unsuspended.
See Also	Administering the BEA TUXEDO System, BEA TUXEDO Administrator's Guide to the Web-Based GUI, `tpconnect`(3c), `MIB`(5), `TM_MIB`(5)
1412	ERROR: Suspended client attempting to start new transaction
	Description	A suspended client attempted to start a new transaction. Clients are suspended by the application administrator using either the /AdminGUI or /AdminAPI.
Action	Contact your application administrator to determine why the client was suspended and when they might expect to be unsuspended.
See Also	Administering the BEA TUXEDO System, BEA TUXEDO Administrator's Guide to the Web-based GUI, `tpbegin`(3c), `MIB`(5), `TM_MIB`(5)
1413	WARN: Client aborting processing
	Description	The client generating the userlog message has been administratively set to a state of DEAD. This has been detected within the BEA TUXEDO system libraries invoked by the client, and the client is abortively terminating processing via a call to `abort()`.
Action	Contact your application administrator to see why the client was abortively terminated.
See Also	Administering the BEA TUXEDO System, `MIB`(5), `TM_MIB`(5)
1414	WARN: Client aborting processing
	Description	The client generating the userlog message has been administratively set to a state of DEAD. This has been detected within the BEA TUXEDO system libraries invoked by the client, and the client is abortively terminating processing via a call to `tpabort()`.
Action	Contact your application administrator to see why the client was abortively terminated.
See Also	Administering the BEA TUXEDO System, `MIB`(5), `TM_MIB`(5)
1415	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while performing server initialization.
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.
See Also	`malloc`(3c) in UNIX System reference manuals
1416	ERROR: Server group active on primary location
	Description	A server attempted to boot on the backup site for its server group while servers in the group were active on the group's primary site.
Action	Restart the server on the primary site.
See Also	Administering the BEA TUXEDO System, `tmboot`(1)
1417	ERROR: Application initialization failure
	Description	An application initialization failure occurred in the `tpsvrinit`(3c) processing for a dynamically spawned conversational server.
Action	Examine application specific code to determine the cause of the error.
See Also	BEA TUXEDO Programmer's Guide, `tpopen`(3c), `tpsvrinit`(3c)
1418	ERROR: invalid server group information given
	Description	Server group deletion was invoked with invalid server group information.
Action	Contact your BEA TUXEDO system Technical Support.
1419	ERROR: Cannot advertise service names beginning with '.'
	Description	An application server attempted to advertise a reserved service name (that is, one beginning with the character '.') during server initialization.
Action	Modify the configuration file entry and/or the `tpsvrinit`(3c) processing for the server to avoid attempts to advertise reserved service names.
See Also	Administering the BEA TUXEDO System, BEA TUXEDO Programmer's Guide, `tpadvertise`(3c), `tpsvrinit`(3c), `ubbconfig`(5)
1420	ERROR: Cannot advertise service names beginning with '.'
	Description	An application server attempted to advertise a reserved service name (that is, one beginning with the character '.') during server initialization.
Action	Modify the configuration file entry and/or the `tpsvrinit`(3c) processing for the server to avoid attempts to advertise reserved service names.
See Also	Administering the BEA TUXEDO System, BEA TUXEDO Programmer's Guide, `tpadvertise`(3c), `tpsvrinit`(3c), `ubbconfig`(5)
1421	ERROR: Out of order routing table found
	Description	The configuration file routing table was in an inconsistent state and could not be processed.
Action	Remove your BEA TUXEDO system configuration file, reconfigure the application, and reboot.
See Also	Administering the BEA TUXEDO System, `tmboot`(1), `tmconfig`(1)
1422	WARN: Cannot compute field name fldname view offset for criteria crit type typ subtype subtyp
	Description	The system could not map the field name fldname to a corresponding view offset while processing routing criteria crit for buffer type typ and subtype subtyp. The indicated criteria entry is added to the bulletin board; however, routing using this criterion will not succeed from this site due to the field name mapping problem.
Action	Check the environment file for the site in question to ensure that the appropriate environment variables (that is, `FIELDTBLS`, `FLDTBLDIR`, `VIEWDIR`, and `VIEWFILES`) are set correctly.
See Also	Administering the BEA TUXEDO System, `compilation`(5), `ubbconfig`(5)
1423	WARN: Cannot route on unknown buffer type typ
	Description	A ROUTING section entry was specified in the `ubbconfig`(5) file that referenced an unsupported buffer type for preconfigured ROUTING entries. The entry in question is ignored by the system and processing continues.
Action	Correct the entry to use one of the supported types or remove the entry from the configuration file altogether.
See Also	Administering the BEA TUXEDO System, `ubbconfig`(5)
1424	*ERROR: Routing field fld* type mismatch for routing criteria crit, type typsepsubtyp, ignored**
	Description	The routing field fld had a different data type in routing criteria entry crit for buffer type typ and subtype subtyp than it did for an earlier buffer type in the same routing entry.
Action	Split the routing specification for the two buffer types into separate entries, each with routing rules appropriate for the data type of the field in that buffer type. Alternatively, the buffer types themselves may be changed to bring the data types into alignment. This would typically mean modifying an FML field or a VIEW specification.
See Also	Administering the BEA TUXEDO System, BEA TUXEDO FML Programmer's Guide, `tmloadcf`(1), `ubbconfig`(5)
1425	*WARN: Duplicate routing criteria crit* type typ combination ignored**
	Description	A routing criteria crit, buffer type combination typ was specified more than once in the ROUTING section of the `ubbconfig`(5) file.
Action	Correct the configuration file to remove the duplicate entry, and rerun `tmloadcf`(1).
See Also	Administering the BEA TUXEDO System, `tmloadcf`(1), `ubbconfig`(5)
1426	ERROR: Insufficient routing table space to create entry for criteria crit type typ
	Description	The indicated routing criteria type combination (crit/typ) could not be created due to table size restrictions in the bulletin board.
Action	Increase the sizes of the bulletin board tables and reboot the application. These parameters include `MAXDRT`, `MAXRFT`, and `MAXRTDATA`.
See Also	Administering the BEA TUXEDO System, `tmloadcf`(1), `ubbconfig`(5)
1427	ERROR: System error(tperrmsg) creating routing table for criteria crit type typ
	Description	The BEA TUXEDO system error indicated by tperrmsg occurred while attempting to create a new routing criteria table entry for crit/typ.
Action	Contact your BEA TUXEDO system Technical Support.
1428	ERROR: Cannot map field name fld to field identifier for criteria crit type typ
	Description	The indicated ROUTING section entry could not be added to the bulletin board because the specified field name fld could not be mapped to a field identifier.
Action	Check the environment file for the site in question to ensure that the environment variables `FIELDTBLS` and `FLDTBLDIR` are set correctly for the application. Also check that the field name is specified correctly in the `ubbconfig`(5) file.
See Also	Administering the BEA TUXEDO System, `tmloadcf`(1), `compilation`(5), `ubbconfig`(5)
1429	ERROR: Cannot compute field name fldname view offset for criteria crit type typ subtype subtyp
	Description	The system could not map the field name fldname to a corresponding view offset while processing routing criteria crit for buffer type typ and subtype subtyp. The indicated routing criterion is ignored and processing continues.
Action	Check the environment file for the site in question to ensure that the appropriate environment variables (that is, `FIELDTBLS`, `FLDTBLDIR`, `VIEWDIR`, and `VIEWFILES`) are set correctly.
See Also	Administering the BEA TUXEDO System, `compilation`(5), `ubbconfig`(5)
1430	*WARN: Ignoring routing entry crit, invalid buffer type specified*
	Description	Routing criteria crit is ignored by the system due to invalid buffer types being specified.
Action	ROUTING section entries must use only system supported buffer types as defined in `ubbconfig`. Correct the configuration file to conform to this restriction, rerun `tmloadcf`(1), and reboot the system (`tmboot`(1)).
See Also	Administering the BEA TUXEDO System, `tmboot`(1), `tmloadcf`(1), `ubbconfig`(5)
1431	WARN: Cannot compute field name fldname view offset for criteria crit type typ subtype subtyp
	Description	The system could not map the field name fldname to a corresponding view offset while processing routing criteria crit for buffer type typ and subtype subtyp. The indicated criterion entry is added to the bulletin board; however, routing using this criterion will not succeed from this site due to the field name mapping problem.
Action	Check the environment file for the site in question to ensure that the appropriate environment variables (that is, `FIELDTBLS`, `FLDTBLDIR`, `VIEWDIR`, and `VIEWFILES`) are set correctly.
See Also	Administering the BEA TUXEDO System, `compilation`(5), `ubbconfig`(5)
1432	ERROR: Corrupted routing range table found
	Description	The configuration file routing table was in an inconsistent state and could not be processed.
Action	Remove your BEA TUXEDO system configuration file, reconfigure the application, and reboot.
See Also	Administering the BEA TUXEDO System, `tmboot`(1), `tmconfig`(1)
1433	WARN: Invalid trace category; trace point ignored
	Description	The category (for example, atmi) associated with a trace point is not a known category. The trace point was therefore ignored.
Action	No action required.
See Also	`tmtrace`(5)
1434	ERROR: Invalid trace specification; ignored
	Description	A syntactically incorrect trace specification was supplied as the value of the TMTRACE environment variable. The trace specification was ignored.
Action	Provide a legal string for the trace specification.
See Also	`tmtrace`(5)
1435	WARN: Invalid regular expression in trace specification (receiver); ignored
	Description	A syntactically incorrect regular expression was supplied as part of the receiver-spec in the trace specification string. The regular expression was ignored; consequently, all trace points that passed the filter were emitted to the receiver.
Action	Provide a legal regular expression in the receiver-spec.
See Also	`tmtrace`(5)
1438	WARN: Trigger failed - system(status)
	Description	The execution of the trigger that was executed for a particular trace point failed. The trigger was specified in the trace specification.
Action	No action required.
See Also	`tmtrace`(5)
1439	WARN: Invalid regular expression in trace specification (trigger); ignored
	Description	A syntactically incorrect regular expression was supplied as part of the trigger-spec in the trace specification string. The regular expression was ignored; consequently, the trigger was executed for all trace points that passed the filter.
Action	Provide a legal regular expression in the trigger-spec.
See Also	`tmtrace`(5)
1440	ERROR: Invalid trace trigger; ignored
	Description	The action (for example, `dye`) specified in the `trigger-spec` of a trace specification is not a known action. The trigger was therefore not executed for a trace point that passed the filter.
Action	Provide a valid trigger action in the trace specification.
See Also	`tmtrace`(5)
1441	ERROR: tpcommit message failure, check GTT
	Description	This message is issued when the system encounters an error trying to receive the reply to a request sent to a TMS to complete a transaction. The message is typically issued when a system-level failure occurs.
Action	See the userlog for more information about this transaction's completion and about any communication error that may have occurred. Also, use `tmadmin`'s `printtrans` command to find out more information about the transaction, and use the `printnet` command to see the status of all machine connections in the network. This command will report any network partitions.
See Also	`tmadmin`(1)
1461	*ERROR: Could not advertise servicename. Specify all functions at buildserver time.*
	Description	All functions that can handle service name associations must be specified at buildserver time. This can be done using the `-s`:functionname option to `buildserver`. For example, in order to allow services to be associated with the function `foo` dynamically, the `buildserver` line would include the `-s:foo` option.
Action	Add all functions that can be dynamically associated with a service name to the `buildserver` command line. If there are many functions of this variety, the `-s` @filename option allows the developer to specify a file which `buildserver` will parse. Each line of this file is considered to be an argument to the `-s` option. This file can be commented by using a '#' character in the first character position on a line. On the SunOS 4.1.3 platform, set the CFLAGS=-PIC when running the `buildserver` command.
1463	ERROR: Error parsing -s option.
	Description	The `CLOPT` option specified in `ubbconfig`(5) had a syntax error in the `-s` option.
Action	See the `servopts`(5) and `ubbconfig`(5) manual pages for a description of the -`s` option in the `CLOPT` line. Then change the `CLOPT` line for this server to conform to the proper syntax. Run `tmloadcf`(1) on the new `ubbconfig`, and reboot the affected server.
1465	*INFO: Duplicate advertisement of service servicename* (func functionname) ignored.**
	Description	The given association between servicename and functionname has already been advertised. Duplicates are ignored.
Action	In order to eliminate this message, remove the duplicate service advertisement from either the `buildserver` command line or the `CLOPT` line for this server in the `ubbconfig`(5) file.
1466	*WARN: Overriding service servicename* (func functionname) mapping given at buildserver time.**
	Description	An association between a servicename and a functionname given at buildserver time has been overridden by the `CLOPT` line in the `ubbconfig`(5) file.
Action	The `CLOPT` line overrides associations made at buildserver time. If you wish to preserve the association made at buildserver time, then it will be necessary to remove the offending association in the `CLOPT` line of this server.
1467	WARN: Skipping recursive export file.
	Description	The `-s` @filename option can be used with the `CLOPT` line in the `ubbconfig`(5) file. However, the arguments within the file specified by filename cannot specify another file to open and parse. This practice is known as file recursion. File recursion is not supported by `buildserver`(1).
Action	Remove any lines from filename which begin with the @ character.
1468	*WARN: Could not open file filename.*
	Description	The file specified on the `CLOPT` line of this server in the `ubbconfig`(5) file via the `-s` @filename option does not exist.
Action	Make sure that the given filename exists. One useful trick is to specify filename as a full path name, rather than a relative path name.
1469	ERROR: Error while parsing file filename.
	Description	The server was parsing the given filename. While parsing the file given via the `-s` @filename option of the `CLOPT`, the server encountered a syntax error.
Action	Edit the file specified by the `-s` @filename option. Make sure that each line is a valid argument to the `-s` option. The file may be commented if the first character of the comment line is "#". Blank lines are also acceptable. If the file is syntactically correct, then contact BEA TUXEDO system Technical Support.
1470	*WARN: Function functionname* not specified at buildserver time. servicename will not be advertised.**
	Description	All functions that can handle service name associations must be specified at buildserver time. This can be done using the `-s` :functionname option to `buildserver`. For example, in order to allow services to be associated with the function `foo` dynamically, the `buildserver` line would include the `-s :foo` option.
Action	Add all functions that can be dynamically associated with a service name to the `buildserver` command line. If there are many functions of this variety, the `-s` @filename option allows the developer to specify a file which buildserver will parse. Each line of this file is considered to be an argument to the `-s` option. This file can be commented by using a '#' character in the first character position on a line. On the SunOS 4.1.3 platform, set the `CFLAGS=-PIC` when running the `buildserver` command.
1471	ERROR: Memory allocation failure.
	Description	While attempting to create a table for service advertisements, the system ran out of memory.
Action	Check the memory of the system. If it appears that there should be enough memory to run this server, then contact the BEA TUXEDO system Technical Support.
1472	*WARN: Function name must be <= number* characters in length; functionname will be truncated**
	Description	Function names are restricted in length. If a given function name is longer than this maximum length, then that function name will be truncated.
Action	Shorten the length of the function name.
1473	*WARN: Service name must be <= number* characters in length; servicename will be truncated**
	Description	Service names are restricted in length. If a given service name is longer than this maximum length, then that service name will be truncated.
Action	Shorten the length of the service name.
1475	*ERROR: .SysServerCleaning: servername, group srvgrp, id srvid* server cleaning**
	Description	This message indicates that the server specified above died abnormally and the BBL cleaned up the slot allocated by the server.
Action	Debug the server and fix the problem before it is restarted again.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1476	*ERROR: .SysServerRestarting: servername, group srvgrp, id srvid* server restarting**
	Description	This message indicates that the server specified above died abnormally; and since this has been marked as a restartable server, it has been restarted. This message is also printed during normal migration of the DBBL from the master to the backup.
Action	BEA TUXEDO application servers should not ordinarily die abnormally. This error is most likely due to an application-specific problem. Debug the server and resolve the problem before restarting the server again. If it occurs for the DBBL during migration, it can be ignored.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1477	*ERROR: .SysServerDied: servername, group srvgrp, id srvid* server died**
	Description	This message indicates that the server specified above died abnormally and the BBL detected this condition in its periodic scan of the BB.
Action	Debug the server and fix the problem before it is restarted again.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1478	*ERROR: .SysServerInit: servername, group srvgrp, id srvid* server initialization failure**
	Description	This message indicates that the server specified above failed in `tpsvrinit()` and therefore could not be booted.
Action	Fix the problem and then reboot the server. The problem can be due to a BEA TUXEDO resource limit or an application-specific problem.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1479	*ERROR: .SysServerTpexit: servername, group srvgrp, id srvid* server requested TPEXIT**
	Description	This message indicates that the server specified above received a request, and the service routine code did a `tpreturn(TPEXIT)` while the server was executing application-specific code.
Action	This is an informational message.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1480	*ERROR: .SysServerMaxgen: servername, group srvgrp, id srvid* server exceeded MAXGEN LIMIT**
	Description	This message indicates that the server specified above died abnormally; and since this has been marked as a restartable server, it has been restarted `MAXGEN`-1 times in the specified GRACE period.
Action	BEA TUXEDO application servers should not ordinarily die abnormally. This error is most likely due to an application-specific problem. Debug the server and resolve the problem before restarting the server again.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1481	*WARN: .SysClientDied: User usrname* on LMID client died**
	Description	This message indicates that the client specified above exited the application without doing a `tpterm()`. A complete listing of the current attributes of the client are sent in the posted buffer. In the normal way, the clients should do a `tpterm()` before exiting the application.
Action	This is an informational message.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1482	INFO: .SysClientState: User usrname on LMID state change to state
	Description	This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer.
Action	This is an informational message.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1483	INFO: .SysClientState: User usrname on LMID state change to state
	Description	This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer.
Action	This is an informational message.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1484	*WARN: .SysClientSecurity: User usrname* on LMID authentication failure**
	Description	This message indicates that the client specified above failed security validation when trying to join the application. A complete listing of the current attributes of the client are sent in the posted buffer.
Action	Check to make sure that this is not some hacker trying to gain access to your application data.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1485	*ERROR: .SysNetworkDropped: LMID1->LMID2* connection dropped**
	Description	This message indicates that the network link between the two machines specified was dropped abnormally. A complete listing of the current parameters are sent along in the posted buffer.
Action	This can happen either because the BRIDGE on either machine died or one of the machines crashed.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1486	*ERROR: .SysNetworkFailure: LMID1->LMID2* connection failure**
	Description	This message indicates that the BRIDGE process on LMID1 could not make a network connection to the BRIDGE process on LMID2. A complete listing of the current parameters are sent along in the posted buffer.
Action	This can happen either because the BRIDGE on the remote machine died or the remote machine itself crashed.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1488	*WARN: .SysMachineFullMaxconv: LMID* capacity limit**
	Description	This message indicates that the given LMID reached the capacity limit on the number of concurrent conversations. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.
Action	Increase the value of MAXCONV for the particular machine such that this event is not generated.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1489	*WARN: .SysMachineFullMaxgtt: LMID* capacity limit**
	Description	This message indicates that the given LMID reached the capacity limit on the number of concurrent transactions. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.
Action	Increase the value of MAXGTT for the particular machine such that this event is not generated.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1490	*WARN: .SysMachineFullMaxwsclients: LMID* capacity limit**
	Description	This message indicates that the given LMID reached the capacity limit on the number of workstation clients. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.
Action	Increase the value of MAXWSCLIENTS for the particular machine such that this event is not generated.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1491	*WARN: .SysMachineFullMaxaccessers: LMID* capacity limit**
	Description	This message indicates that the given LMID reached the capacity limit on the number of accessers. A complete listing of the current parameters for the given LMID are sent along in the posted buffer.
Action	Increase the MAXACCESSERS for the particular machine or, if the hardware/software limits have been reached for the maximum number of users on the machine, move additional users to other machines.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1492	*ERROR: .SysMachinePartitioned: LMID* is partitioned**
	Description	This message indicates that the DBBL partitioned the stated machine either because the BBL on the machine is slow or the network link between the master and the machine is broken.
Action	This can be caused due to various reasons, the first one being that the entire network is bogged down due to heavy traffic. The second is that the BBL or BRIDGE on the non-master is either dead or slow. The third is that the BRIDGE process on the non-master is extremely busy. The software is capable of unpartitioning the machine if things stabilize.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1494	*INFO: .SysNetworkFlow: LMID1->LMID2* flow control**
	Description	While sending a message on the network, flow control has been detected. Machine parameters for both machines are sent along in the posted buffer.
Action	This is usually caused by heavy network traffic. No action required.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1495	*INFO: .SysMachineUnpartitioned: LMID* is unpartitioned**
	Description	A machine that was partitioned (see message 1492) is again available to service requests.
Action	No action required.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1496	*WARN: .SysMachineSlow: machine* slow responding to DBBL**
	Description	The BBL on machine sends an "I'm OK" message to the DBBL every time it performs a sanity check of its machine. This check occurs every "SANITYSCAN * SCANUNIT" seconds, as specified in the RESOURCES section. Similarly, every `BBLQUERY` * `SCANUNIT` seconds, the DBBL performs a sanity check of all BBLs. If an "I'm OK" message has not been received from machine during the previous "BBLQUERY * SCANUNIT" seconds, the DBBL prints this warning message. Then an explicit sanity check is done over the network. If this check also fails, machine will be considered partitioned.
Action	This message indicates that there may be network congestion or an overload on machine. There is a risk that machine will become partitioned. Check for networking problems between the two machines, or any cause of slow network response. Check for a CPU overload on machine that prevents the BBL process from running. Check for a CPU overload on the master machine that prevents the DBBL from processing messages in its queue. Adjust the BBLQUERY parameter so that it is larger than the SANITYSCAN parameter. A difference of ten seconds or more should prevent spurious warnings under most circumstances.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1497	*WARN: .SysMachineMsgq: LMID* message queue blocking**
	Description	This message indicates that the server posting a message encountered a blocking condition while putting a message on the message queue. A complete listing of the machine parameters are sent along in the posted buffer.
Action	Configure larger message queues and/or distribute the load equally on all the machines.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1498	*WARN: .SysMachineBroadcast: LMID* broadcast delivery failure**
	Description	This message indicates that `tpbroadcast()` failed for at least one accesser on LMID of the application. A complete listing of the machine parameters is sent along in the posted buffer.
Action	Since the broadcast messages are sent in no-blocking mode, it is possible that the process doing the broadcasting encountered a blocking condition and dropped a message. Configure larger message queues and/or load-balance clients/servers such that excessive load is not put on some machines.
See Also	`EVENT_MIB`(5), `TM_MIB`(5)
1499	ERROR: Unable to update security version number.
	Description	While updating one of the administrative security files, the version number could not be updated. This will cause a potential inconsistency between multiple active machines in the application.
Action	Attempt to update the security information (users, groups, ACLs) again. If the message persists, shut down and re-boot the application, which will re-propagate the security files.
See Also	`MIB`(5), `TM_MIB`(5)

[Top] [Prev] [Next] [Bottom]