401
ERROR: service request service_name handled by DBBL failed, msg
Description
An administrative service request handled by the DBBL failed with a non-fatal error. These requests include tmadmin requests, tmboot and tmshutdown requests.
DBBL
tmadmin
tmboot
tmshutdown
Action
The service requests failed with tperrno and Uunixerr, if any. Take proper action according to the tperrno and/or Uunixerr, or contact your BEA TUXEDO system Technical Support.
tperrno
Uunixerr
See Also
tmadmin(1), tmboot(1), tmshutdown(1)
402
INFO: The temporary DBBL is exiting system
A temporary DBBL was brought up to clean up the partitioned BBLs. This temporary DBBL is currently exiting the system.
No action required.
tmshutdown(1)
403
INFO: The DBBL is exiting system
The DBBL is currently exiting the system. All other processes have been shut down already.
404
WARN: Memory allocation failure
An attempt dynamically to allocate memory from the operating system using malloc() failed while the DBBL was checking the status of all BBLs, marking unreachable BBLs and then cleaning up.
malloc()
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.
406
WARN: SIGTERM was ignored while shutting down the DBBL
SIGTERM was received and ignored while shutting down the DBBL.
SIGTERM
See tmshutdown command for shutdown procedures.
407
ERROR: Unable to add group group_name to TMGCTL table- no space
BEA TUXEDO system attempted to add the specified group in the transaction management data table, but the space allocated for the number of groups was exceeded.
Please modify your configuration and increase the number of server groups that are to be used. Then reload the TUXCONFIG file and reboot your application. If you need more than the allowable maximum number of server groups, contact your BEA TUXEDO system Technical Support.
TUXCONFIG
BEA TUXEDO Administrator's Guide, tmloadcf(1), tmboot(1), ubbconfig(5)
tmloadcf
ubbconfig
408
ERROR: Unable to add group group_name to TMGTT table- no space
BEA TUXEDO system was in the process of recovering transactions while performing a tpsvrinit(). BEA TUXEDO system attempted to add the specified group to the global transaction table, but the space allocated for the number of groups was exceeded.
tpsvrinit()
Contact your BEA TUXEDO system Technical Support.
409
ERROR: xa_recover() returned count for group groupname
BEA TUXEDO system was in the process of recovering transactions while performing a tpsvrinit(). The resource manager returned an error when xa_recover() was called to find pre-committed global transactions.
xa_recover()
Check the error mechanism for the associated resource manager to find the nature of the error.
410
WARN: tpsvrinit() changing state of group groupname from TMGHCOMMIT to TMGABORTED
BEA TUXEDO system was in the process of recovering transactions while performing a tpsvrinit(). While the transaction coordinator was restarting, messages about groups may have been lost; as such the coordinator may have an incomplete list of groups unless the transaction was logged. Since this is a case of the coordinator restarting, the transaction must not have been logged, so the particular transaction must be aborted.
Please repeat the transaction.
411
ERROR: tpsvrinit() found transaction state state_val
BEA TUXEDO system was in the process of recovering transactions while performing a tpsvrinit(). The transaction state was not one of the valid states.
412
ERROR: tpsvrinit() unable to locate entry for TMS in the Bulletin Board
BEA TUXEDO system was in the process of recovering transactions while performing a tpsvrinit(). The function was unable to locate an entry for the first TMS in a group in the Bulletin Board.
TMS
413
ERROR: tpsvrinit() unable to update entry for TMS in the Bulletin Board
BEA TUXEDO system was in the process of recovering transactions while performing a tpsvrinit(). The function was unable to update an entry for the first TMS in a group in the Bulletin Board.
414
ERROR: TMS() got request for invalid Global Transaction ID
BEA TUXEDO system server TMS was given an invalid global transaction identifier, and therefore could not complete the necessary operation.
415
ERROR: Invalid service identifier requested while processing transactions
An invalid service identifier identifier was specified for processing, and therefore could not complete the necessary operation.
416
ERROR: service svcname sent to non-coordinator
The TMS was unable to execute the service svcname because the service was sent to a non-coordinator for the transaction.
417
ERROR: TMS_MANAGE found transaction state stateval
While processing transactions, an invalid state was reached.
418
ERROR: Unable to add message groups to transaction
While processing transactions, the BEA TUXEDO system attempted to add message groups to the transaction. The operation was unsuccessful.
419
WARN: Commit found no participants
While processing a commit request, the TMS found no participants. The transaction will be deleted.
420
WARN: Commit coordinator gone
BEA TUXEDO system was processing transactions. In a transaction, the first Resource Manager group is the transaction coordinator, so it must be the first at its site. However, it is possible that the site went down and came back up before the arrival of a TMS_MANAGE message.
421
ERROR: Invalid transaction state state
BEA TUXEDO system was committing a transaction. During a one-phase commit step, the transaction state was invalid.
422
ERROR: XA_RETRY not supported for one-phase commit
BEA TUXEDO system was committing a transaction. During a one-phase commit, the XA return code was XA_RETRY, which is not supported for one-phase commit.
XA
XA_RETRY
Check the error reporting mechanism for the associated resource manager.
423
WARN: One-phase commit- xa_commit returned error_val
BEA TUXEDO system was committing a transaction. During a one-phase commit, the XA return code was not XA_OK, XA_HEURCOM, XA_RETRY, XAER_RMFAIL, XA_HEURHAZ, XA_HEURRB, XA_HEURMIX, or XAER_RMERR.
XA_OK
XA_HEURCOM
XAER_RMFAIL
XA_HEURHAZ
XA_HEURRB
XA_HEURMIX
XAER_RMERR
424
ERROR: Commit found invalid state - group group state state
425
ERROR: Precommit found an invalid transaction state state
BEA TUXEDO system was precommitting a transaction. The transaction state was not one of the states expected.
426
ERROR: Precommit found invalid state group group state state
BEA TUXEDO system was precommitting a transaction. The transaction state for the indicated group was not as expected.
427
ERROR: Precommit transaction state state after xa_precom failure
BEA TUXEDO system was precommitting a transaction. The transaction state after xa_precom failure was not as expected.
428
ERROR: Precommit transaction state state after xa_precom
BEA TUXEDO system was precommitting a transaction. The transaction state after xa_precom was not as expected.
429
ERROR: Rollback found invalid transaction state state
BEA TUXEDO system was rolling back a transaction. The transaction state was not as expected.
430
ERROR: Completion found invalid transaction state state
BEA TUXEDO system was completing a transaction. The transaction state was not as expected.
431
ERROR: Received a rollback request for a decided transaction
BEA TUXEDO system received a rollback request for a decided transaction.
432
ERROR: Group group at coordinator site received rollback request in ready state
BEA TUXEDO system received a request to rollback a transaction that is already in "ready" state.
433
ERROR: Rollback - xa_abort returned error for group group
BEA TUXEDO system was rolling back a transaction. The resource manager returned an error when xa_abort was called. The XA return code was not XA_OK, XA_HEURRB, or XAER_NOTA.
xa_abort
XAER_NOTA
434
WARN: Rollback changing group group from heuristic commit to rolled back
BEA TUXEDO system was rolling back a transaction. The transaction state of the group was changed from heuristic commit to rolled back.
435
ERROR: Rollback found invalid state - group group in state state
BEA TUXEDO system was rolling back a transaction. The transaction state of the group was not one of the expected states.
436
WARN: Heuristic rollback of transaction
BEA TUXEDO system received a request to heuristically rollback a global transaction. This request was generated via tmadmin aborttrans.
tmadmin aborttrans
437
BEA TUXEDO system received a request to heuristically rollback a transaction for this group only. This request was generated via tmadmin aborttrans.
438
WARN: Heuristic rollback not allowed for decided transaction
A request was received to heuristically rollback a transaction that is already in decided state. This request was generated via tmadmin aborttrans.
439
WARN: Heuristic rollback not allowed for ready transaction at coordinator site
BEA TUXEDO system received a request to heuristically rollback a transaction that is in ready state. The request was generated by the tmadmin aborttrans command.
The request will be ignored. No action required.
440
WARN: Transaction heuristically rolled back for group groupname
BEA TUXEDO system heuristically rolled back a transaction based on a request from the tmadmin aborttrans command.
441
ERROR: Rollback xa_abort returned error
BEA TUXEDO system was rolling back a transaction. The xa_rollback() function returned an error that was not one of the expected values.
xa_rollback()
442
ERROR: Timeout found invalid state state
BEA TUXEDO system was processing a timeout request for a transaction and found an unexpected state, state.
443
ERROR: tms_timeout group group xa_abort returned error
BEA TUXEDO system was processing a timeout request for a transaction. The resource manager returned an error from xa_abort.
444
WARN: Heuristic commit for group group
This informative message indicates that the transaction has been heuristically committed as a result of a tmadmin committrans command.
tmadmin committrans
445
ERROR: Heuristic commit xa_commit for group group returned error
While heuristically committing a transaction, the resource manager returned an error condition from xa_commit().
xa_commit()
446
ERROR: Commit found transaction state state
While committing a transaction, an unexpected transaction state was found.
447
ERROR: xa_commit returned error for group group
While committing a transaction, the resource manager returned an error from xa_commit.
xa_commit
448
ERROR: Commit found invalid state for group group state state
While committing a transaction, an invalid state was found for the specified group.
449
ERROR: Ready indication for missing group group
While committing a transaction, a ready indication was received for a group that is not part of the transaction. The indication will be ignored.
450
ERROR: Ready found invalid state for group group state state
While committing a transaction, a ready indication was received for a group that is in an invalid state. The indication will be ignored.
451
ERROR: Ready indication found transaction state state
While committing a transaction, a ready indication was received for a transaction that is in an unexpected state.
452
ERROR: Status request transaction state state group group state state
While processing a status request for a transaction, unexpected states were found for the transaction and the specified group.
453
ERROR: Transaction log commit failed
While committing a transaction, updating the transaction log failed.
Check the userlog for earlier messages indicating the nature of the failure.
454
ERROR: Status request found transaction state state
While processing a status request, an invalid transaction state was found.
455
ERROR: tpsvrdone can't find group group
The TMS was being shut down. A group entry was to be cleaned up, but no information on that group was found.
456
ERROR: tpsvrdone can't get queue entry
The TMS was being shut down. A group entry was to be cleaned up, but BEA TUXEDO system was unable to get information on the Queue Table.
457
INFO: TMS tpsvrdone complete
The TMS shutdown was completed safely.
458
ERROR: Memory allocation failure
The distinguished TMS was about to be shut down. However, BEA TUXEDO system was unable to allocate required memory. The memory allocated was to have been used to step through server information on all the TMSs to ensure that the distinguished TMS could shut down properly. In this case, since memory could not be allocated, it is not possible to determine the state of each TMS, so BEA TUXEDO system allows the shutdown to proceed anyway.
459
ERROR: Invalid sendlist error
The TMS encountered an error while trying to send a message. This condition should never arise.
460
ERROR: TMS send - failed to set priority for TMS request
The TMS was managing a transaction and had attempted to set the priority of a TMS request, and that function failed.
461
ERROR: tms_send tpacall service code
The TMS was managing a transaction and had attempted to send a message to a TMS service via a tpacall(), and that call failed. The numeric value displayed in the message identifies the service that was used.
tpacall()
A possible cause for this error may be that the TMS process has terminated for some reason. Please check and ensure that all TMS processes are running. If further assistance is needed, please contact the BEA TUXEDO system Administrator.
462
WARN: Can't send reply to committer
The TMS was managing a transaction and had attempted to send a reply to the committer of the transaction. The call failed.
Please examine the userlog for additional messages included prior to this one. If further assistance is needed, contact your BEA TUXEDO system Technical Support.
463
ERROR: could not contact BBL to abort old transactions
The TMS was in the process of aborting old transactions and was unable to contact the BBL process to get information about the transactions.
BBL
464
ERROR: could not contact DBBL to abort old transactions
The TMS was in the process of aborting old transactions and was unable to contact the DBBL process to get information about the transactions.
Please ensure that the DBBL process is running. Contact your BEA TUXEDO system Technical Support.
465
ERROR: Failed to abort old transactions
The TMS was in the process of aborting old transactions and was unable to do so. An underlying system call had failed, in all probability a request/response call to the BRIDGE process.
BRIDGE
468
An attempt dynamically to allocate memory from the operating system using malloc() failed while allocating a message. The BEA TUXEDO system boot process for non-master nodes involves running a bootstrap-Bridge process, called the BSBRIDGE. The BSBRIDGE starts the BBL on that node, and the BBL starts the real BRIDGE, which then shuts down the BSBRIDGE. The BRIDGE does this by sending a message to the BSBRIDGE. The code that allocated the space for that message failed.
BSBRIDGE
469
ERROR: Can't send shutdown message to the BSBRIDGE
Please refer to the description for Message 468 above. The send of the shutdown message to the BSBRIDGE failed. This could be caused by full message queues on the system.
470
An attempt dynamically to allocate memory from the operating system using malloc() failed while the BRIDGE process was creating an internal buffer for an identification message. Failure to send this message will not prevent the BRIDGE process from running. However, the network connection being established cannot be used bi-directionally, so some system resources will be wasted.
471
WARN: Error sending message OB_IDENT process
The BRIDGE process could not send an OB_IDENT identification message over a newly created connection. This failure will not prevent the BRIDGE process from running. However, the network connection being established cannot be used bi-directionally, so some system resources will be wasted.
OB_IDENT
It is likely that further errors will occur over this connection. Try to reestablish the link using tmadmin 's reconnect command. If this fails, shut down and reboot the BEA TUXEDO system on this machine.
reconnect
473
ERROR: Could not find DBBL
The BSBRIDGE (bootstrap bridge) process could not contact the DBBL on the master or backup machine during its initialization.
The
Check the master machine's network addresses in the NETWORK section of the configuration file. Check for and resolve any networking problems.
476
An attempt dynamically to allocate memory from the operating system using malloc() failed while attempting to contact the DBBL.
480
An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to allocate a buffer for receiving a message in the BRIDGE.
malloc(3) in UNIX System reference manuals
malloc
481
An attempt dynamically to allocate memory from the operating system using realloc() failed while allocating a larger buffer for receiving a message.
realloc()
482
ERROR: Received message with unknown release number rel_val
The message received by the BRIDGE was not one from the current release or the previous one but from release rel_val.
Verify that the releases of the BEA TUXEDO system software installed are valid. Contact your BEA TUXEDO system Technical Support.
483
ERROR: Shutting down bridge, serious message receive error
The bridge is shutting down due to a system error.
Re-try the desired operation and if the problem persists, contact your BEA TUXEDO system Technical Support.
484
ERROR: BRIDGE process detected corrupted message
The bridge or bootstrap bridge process detected a message with a corrupted header. This could be caused by problems in the networking software or in BEA TUXEDO system itself.
Contact your BEA TUXEDO system Technical Support for assistance.
485
BEA TUXEDO system received an error return while attempting to allocate memory from the operating system. The amount of memory required by BEA TUXEDO system is influenced by the parameters in the UBBCONFIG file. The number of processes running on a machine and the options given to those processes also have a large effect on memory usage.
UBBCONFIG
Attempt to decrease the amount of memory required by BEA TUXEDO system, or add more physical memory to the machine.
BEA TUXEDO Administrator's Guide
486
ERROR: Message encoding error
BEA TUXEDO system encountered an error while attempting to encode a negative acknowledgment message being sent from the bridge or bootstrap bridge process.
490
ERROR: tprealloc() failed
An attempt dynamically to allocate memory from the operating system using tprealloc() failed while the system was processing a BRIDGE op-code in attempting to print BRIDGE statistics.
tprealloc()
491
An attempt dynamically to allocate memory from the operating system using tprealloc() failed while the system was processing a BRIDGE op-code.
492
493
INFO: Waiting for orderly release to exit
BEA TUXEDO system was processing a server shutdown. This message is an indication of that action.
494
INFO: BRIDGE exiting system
495
INFO: Alarm forcing shutdown after 30 second wait
BEA TUXEDO system was processing a BRIDGE shutdown. This message indicates that a forced shutdown of the BRIDGE was initiated, most likely because a previous network connection disconnect failed.
Please examine the userlog for further information. If necessary, contact your BEA TUXEDO system Technical Support.
496
INFO: Rejecting EXIT Message not sent from local BBL or BRIDGE
BEA TUXEDO system was processing a BRIDGE shutdown. The BSBRIDGE process received an EXIT message from a process other than the local BRIDGE or BBL process, not from a process on a remote machine.
This message is informative in nature. BEA TUXEDO system processing will continue. However, the userlog may yield additional information that would help explain why this message was written to the userlog.
497
INFO: Rejecting EXIT Message not sent from local BBL
BEA TUXEDO system was processing a BRIDGE shutdown. The BRIDGE process received an EXIT message from a process other than the local BBL process, not from a process on a remote machine.
498
499