LIBTUX Messages 6100-6199
|
|
6101
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
doing security 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 and/or swap space on the machine.
6102
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
doing security 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 and/or swap space on the machine.
6103
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
doing security 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 and/or swap space on the machine.
6105
ERROR: Badly formed unsolicited message
Description
While attempting to process an unsolicited notification message, the system was unable to process the message.
Action
Please contact BEA Customer Support.
6106
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
processing an unsolicited message reply.
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.
6107
ERROR: Invalid buffer passed to tpnotify
Description
A buffer was passed to tpnotify that the system
is not able to process.
A typed buffer must be passed to tpnotify.
Action
Use tpalloc to allocate a typed buffer
to pass to tpnotify.
See Also
tpalloc(3), tpnotify(3)
6108
ERROR: Badly formed unsolicited message
Description
While attempting to process an unsolicited notification message, the system was unable to process the message.
Action
Please contact BEA Customer Support.
6109
ERROR: Badly formed unsolicited message
Description
While attempting to process an unsolicited notification message, the system was unable to process the message.
Action
Please contact BEA Customer Support.
6110
ERROR: Invalid buffer passed to tpbroadcast
Description
A buffer was passed to tpbroadcast that the system
is not able to process.
A typed buffer must be passed to tpbroadcast.
Action
Use tpalloc to allocate a typed buffer
to pass to tpbroadcast.
See Also
tpalloc(3), tpbroadcast(3)
6111
ERROR: Invalid internal reply buffer, ACK not sent
Description
While attempting to process an unsolicited notification message, the system was unable to process the message.
Action
Please contact BEA Customer Support.
6112
ERROR: Invalid unsolicited message
Description
While attempting to process an unsolicited notification message, the system was unable to process the message.
Action
Please contact BEA Customer Support.
6113
ERROR: Invalid unsolicited message
Description
While attempting to process an unsolicited notification message, the system was unable to process the message.
Action
Please contact BEA Customer Support.
6114
ERROR: Unable to initialize local cache in tpnotify
Description
An internal error occurred in initialization for using unsolicited notification messages.
Action
Please contact BEA Customer Support.
6115
ERROR: Unable to lock mutex in tpnotify
Description
An internal error occurred in locking a mutex.
Action
Please contact BEA Customer Support.
6116
ERROR: Unable to unlock mutex in tpnotify
Description
An internal error occurred in unlocking a mutex.
Action
Please contact BEA Customer Support.
6117
ERROR: Unable to lock mutex in tpnotify
Description
An internal error occurred in locking a mutex.
Action
Please contact BEA Customer Support.
6118
ERROR: Unable to unlock mutex in tpnotify
Description
An internal error occurred in unlocking a mutex.
Action
Please contact BEA Customer Support.
6119
ERROR: Unable to initialize local cache in tpbroadcast
Description
An internal error occurred in initialization for using unsolicited notification messages.
Action
Please contact BEA Customer Support.
6120
ERROR: Unable to lock mutex in tpbroadcast
Description
An internal error occurred in locking a mutex.
Action
Please contact BEA Customer Support.
6121
ERROR: Unable to unlock mutex in tpbroadcast
Description
An internal error occurred in unlocking a mutex.
Action
Please contact BEA Customer Support.
6122
ERROR: Unable to lock mutex in tpbroadcast
Description
An internal error occurred in locking a mutex.
Action
Please contact BEA Customer Support.
6123
ERROR: Unable to unlock mutex in tpbroadcast
Description
An internal error occurred in unlocking a mutex.
Action
Please contact BEA Customer Support.
6124
WARN: Context val terminated by another thread in this process
Description
An ATMI call made within a BEA Tuxedo context detected that the application
association in which it was invoked had already been terminated by another
thread in the process which had invoked tpterm()
for that application association. As a result, the ATMI call returns
failure and this message is written to the userlog. The thread invoking
this ATMI call is placed in an invalid context and must issue
tpsetctxt() or
tpinit() before it can again invoke most ATMI verbs.
Action
A thread which receives this message must call
tpsetctxt() or tpinit()
before it can again issue most ATMI calls. At a more fundamental level,
this message generally indicates that application threads are not
synchronizing with each other as well as they should. Except in
extreme error circumstances, an application should not be designed
so that one thread is calling tpterm()
while other threads are still active within that context.
6125
ERROR: Failed to set context to newly created context, tperrno=val
Description
A newly created service dispatch thread created a context to process requests, but was unable to set its current context to the newly created context. As a result, the newly created thread will exit.
Action
Please contact BEA Customer Support.
6126
INFO: New server dispatched thread starting
Description
This message indicates that a new server dispatched thread is being started. This can occur either when the server is booted or during the server's operation if additional server threads are needed and have been configured.
Action
No action required.
6127
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while invoking server dispatch thread initialization code.
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.
6128
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
invoking server dispatch thread initialization code.
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.
6130
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
invoking server dispatch thread initialization code.
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.
6131
ERROR: Cannot set server group/id
Description
A newly created server dispatch thread was unable to set the internal variables which hold its group ID and server ID.
Action
Please contact BEA Customer Support.
6132
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
converting bulletin board data between the current format and the R6.4 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.
6133
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed
during unsolicited message 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 and swap space on the machine.
6134
ERROR: Tuxedo typed buffer routine failed
Description
An attempt to free a message while processing an unsolicited notification failed for a reason other than problems allocating memory.
Action
Review messages occurring earlier in the log for indications of what caused the failure.
6135
ERROR: tpsetunsol() not called, dropping unsolicited message
Description
An unsolicited message was received in a client program that
did not previously call tpsetunsol.
The message will be dropped.
Action
Call tpsetunsol in the client to receive
unsolicited messages.
See Also
tpsetunsol(3)
6136
ERROR: Failed to send ACK to notifier, tperrno=tperrno_val
Description
A notification was received by a client for which the originator wanted a reply acknowledgement. The client program was unable to send the ACK; the associated error is printed as tperrno_val.
Action
The originator will not receive the ACK (it may be that the originator went away). Check the log for related messages.
See Also
tpnotify(3)
6137
ERROR: A lockout has occurred because of license violation
Description
DBBL/BBL lockout occurs because the system has determined that the total number of active users exceeded 110% of Tuxedo licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL/BBL scan cycle.
Action
Upgrade your BEA Tuxedo license with larger number of users to avoid future system lockouts. Please contact your BEA Tuxedo System Administrator.
6138
WARN: Server not built for multithreading; will operate in single context mode
Description
A MAXDISPATCHTHREADS value greater than 1 was specified in
the TUXCONFIG file for a server not built with the
buildserver(1) -t option.
The buildserver(1) -t option is required for
multithreaded servers to prevent an administrator from accidentally
changing the configuration parameters to indicate multithreading for a
server which was not coded with multithreading in mind.
Action
Provided that the server in question is coded in a thread-safe manner,
shut the server down, rebuild the server using the -t
option, and reboot it.
See Also
buildserver(1), ubbconfig(5)
6139
WARN: Failure changing job attributes. Using default attributes
Description
The job attributes for the server could not be set according to the Job Description specified on the -d option. The default job attributes will be used.
Action
Check the job log for the server to determine the cause of the failure.
6140
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system failed. The failure occurred while attempting to change job attributes.
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 swap space on the machine.
6141
ERROR: Failure reading job description. Exception ID - val
Description
The job was unable to read the Job Description specified. The Job Description contains the job attributes to be set.
Action
Determine the cause of the error using the AS/400 Exception ID displayed in the message text. Also, check the job log for the failing job for more information.
6142
ERROR: Unable to change job attributes: val
Description
The job attributes for the failing job could not be set. The message text contains the failing OS/400 command.
Action
Check the job log to determine the cause of the failure.
6143
ERROR: TUXDIR environment variable not set
Description
The TUXDIR environment variable was not set. The error was detected while attempting to read the AS/400 Job Description for the job.
Action
Set the TUXDIR environment variable and retry the operation.
6144
INFO: Cannot open file val
Description
The Job Description file AS400_JD could not be opened.
Action
Check to see that the file AS400_JD exists in the directory udataobj.
6145
ERROR: Cannot find Job Description for val in file val
Description
An error occurred while attempting to find the Job Description for the named Tuxedo system process.
Action
Ensure that an entry exists in the AS400_JD file for the Tuxedo process named in the message.
6146
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while
converting bulletin board data between the current format and the R6.4 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.
6161
ERROR: unable to lock mutex (val/val)
Description
An internal error occurred in locking a mutex.
Action
Please contact BEA Customer Support.
6162
ERROR: unable to unlock mutex (val/val)
Description
An internal error occurred in locking a mutex.
Action
Please contact BEA Customer Support.
6163
ERROR: The -p option is not valid for multithreaded servers
Description
The buildserver(1) -t option indicates that
a server is built to support multithreading, and the
servopts(5) -p run-time option indicates
server spawning and decay are to be used for this server.
These two features may not be used together.
Action
If the administrator decides to make the server multithreaded without
the use of process-based spawning and decay, the administrator must
modify the CLOPT for this server in the TUXCONFIG file.
If the administrator decides to make this server single-threaded and
maintain the use of process-based spawning and decay, the administrator
must reexecute buildserver(1) for this server
without the -t option.
See Also
servopts(5), buildserver(1)
6164
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed in tpexport.
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 swap space on the machine.
6165
ERROR: Unable to convert exported buffer to string format
Description
tpexport was unable to convert an exported binary buffer
to RFC1113 format.
Action
Please contact BEA Customer Support.
See Also
tpexport
6166
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed
in tpimport.
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 swap space on the machine.
6167
ERROR: Unable to convert from string to binary format
Description
tpimport was unable to convert an exported string buffer
in RFC1113 format to its binary representation.
Action
Please contact BEA Customer Support.
See Also
tpimport
6168
ERROR: Unable to export buffer. Error code=errorcode
Description
The system was unable to sign or encrypt a buffer. The error code returned was errorcode. Save the value of errorcode to give to BEA Customer Support.
Action
Check the userlog for other error messages that may help diagnose the problem. Otherwise, contact BEA Customer Support.
See Also
tpkey_open, tpsign, tpseal,
tpexport, tpimport
6169
ERROR: Unable to decrypt buffer. Error code=val
Description
The system was unable to decrypt or verify the signature of a buffer. The error code returned was errorcode. Save the value of errorcode to give to BEA Customer Support.
Action
Check the userlog for other error messages that may help diagnose the problem. Otherwise, contact BEA Customer Support.
See Also
tpkey_open, tpsign, tpseal,
tpexport, tpimport
6170
ERROR: Not licensed for encryption
Description
tpseal was attempted without a proper encryption license.
Action
Install a proper public key encryption license. If you believe you have a valid license for public key encryption, contact BEA Customer Support.
See Also
tpkey_open, tpsign, tpseal,
tpexport, tpimport
6171
ERROR: Not licensed for digital signature
Description
tpsign was attempted without a proper signature license.
Action
Install a proper signature license. If you believe you have a valid license for public key signatures, contact BEA Customer Support.
See Also
tpkey_open, tpsign, tpseal,
tpexport, tpimport
6172
WARN: Service service-name has policy SIGNATURE_REQUIRED=signature-policy and ENCRYPTION_REQUIRED=encryption-policy but the input buffer was neither signed nor sealed
Description
A message arrived at service service-name that violated the policy constraints of the application. The service service-name has a signature policy of signature-policy and an encryption policy of encryption-policy.
Action
Determine why a message arrived for service-name that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes up to the *GROUP level, again looks up to the *MACHINE level and finally the *RESOURCE level. If any of those policies is Y, then the policy for service-name is Y.
See Also
ubbconfig, MIB, TM_MIB
6173
ERROR: Invalid public key context
Description
While attempting to dispatch a service with an encryption or signature policy, an invalid buffer was detected.
Action
Please contact BEA Customer Support.
6174
WARN: Service service-name requires a signature but the input buffer is not signed
Description
A message arrived at service service-name that violated the policy constraints of the application. The service service-name has a signature policy of Y.
Action
Determine why a message arrived for service-name that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes up to the *GROUP level, again looks up to the *MACHINE level and finally the *RESOURCE level. If any of those policies is Y, then the policy for service-name is Y.
See Also
ubbconfig, MIB, TM_MIB
6175
WARN: Service service-name requires encryption but the input buffer is not encrypted
Description
A message arrived at service service-name that violated the policy constraints of the application. The service service-name has an encryption policy of Y.
Action
Determine why a message arrived for service-name that violates the policy, or change the policy. Remember that policy determination starts at the *SERVICE level, goes up to the *GROUP level, again looks up to the *MACHINE level and finally the *RESOURCE level. If any of those policies is Y, then the policy for service-name is Y.
See Also
ubbconfig, MIB, TM_MIB
6176
WARN: Unable to audit policy enforcement event
Description
An attempt to audit an encryption or signature policy failure while dispatching a service failed.
Action
Please contact BEA Customer Support.
See Also
ubbconfig, MIB, TM_MIB
6177
ERROR: Signature verification failure
Description
The signature on a message was invalid. The message was tampered with.
Action
There may be a security violation. The message was garbled in transit, or was maliciously modified by an attacker. Review the security of the system.
6178
WARN: Signature expired, revoked or not trusted
Description
The signature on a buffer has expired, or the principal associated with a signature has been revoked or is not trusted.
Action
Determine why the signature has failed. The parameters SIGNATURE_AHEAD and SIGNATURE_BEHIND may need to be adjusted if a message might sit on a message queue or a disk based queue for a long period of a time. If the message came from an untrusted or revoked user, take step to disallow the user from sending messages. Review the security of the system.
6179
WARN: Unable to audit signature failure
Description
The system was unable to audit a security failure.
Action
Ensure that the auditing plugin is properly registered in the registry. Ensure that
the registry is in a consistent state with the epifregedt
command. If you believe the auditing plugin is registered properly and is
not returning an error, please contact BEA Customer Support.
See Also
epifregedt
6180
ERROR: Problem with the license file
Description
An error occurred while retrieving the current license attributes from the license file. Normally, it means that the product has not been licensed properly.
Action
Install a valid Tuxedo license file in $TUXDIR/udataobj.
6181
ERROR: Problem with the license file
Description
An error occurred while retrieving the current license attributes from the license file. Normally, it means that either the product has not been licensed properly or the license has been expired.
Action
Install a valid Tuxedo license file in $TUXDIR/udataobj.
6182
ERROR: Problem with the license file
Description
An error occurred while retrieving the current license serial number and expiration date attributes from the license file. Normally, it means that the product has not been licensed properly.
Action
Install a valid Tuxedo license file in $TUXDIR/udataobj.
6183
ERROR: Invalid switch index index
Description
An internal routine encountered an invalid state.
Action
Contact your BEA Tuxedo System technical support with the value index from the message.
6184
ERROR: Invalid return flags from _tmpresend2. Must have exactly one of TMUSEIPTR or TMUSEOPTR set. Returned flags are 0xflags
Description
The buffer type switch function _tmpresend2 has output flags. Exactly one of
the bits TMUSEIPTR and TMUSEOPTR must be set upon successful return
from this function. However, flags were set on output.
Action
Change the _tmpresend2 function to return only one of the TMUSEIPTR or
TMUSEOPTR flags.
See Also
buffer(3i)
6185
ERROR: Unable to pre-process buffer before tranmission. Error code(errorcode1/errorcode2)
Description
The system was unable to preprocess a buffer heading for an interoperating site. The error codes errorcode1 and errorcode2 may assist technical support diagnose the problem.
Action
Contact BEA Customer Support.
6187
WARN: AUDIT_POSTOP SECURITY FAILURE: who = val, operation_name = val, operation_target = val
Description
This message is generated by the default auditing security plugin. It is called when a security violation occurs. This is a normal message when either authentication or authorization fails.
Action
Check the userlog for other messages which may indicate the source of the security violation, or check any security logs from your security provider. If the authentication or authorization failures are not warranted, check your security configuration and security provider.
6188
ERROR: Attempt to send encrypted buffer to interoperating site
Description
An attempt has been made to send a buffer that would have been encrypted to a site older than Tuxedo 7.1.
Action
No buffer is marked for encryption can be sent to a site older than 7.1. Upgrade the software on the remote system to handle encrypted buffers, or remove encryption from this buffer.
See Also
tpseal, tpkey_open
6189
ERROR: Attempt to send encrypted buffer to interoperating site
Description
An attempt has been made to send a buffer that would have been encrypted to a site with a version of the BEA Tuxedo system older than Release 7.1.
Action
No buffer is marked for encryption can be sent to a site older than Release 7.1. Upgrade the software on the remote system to handle encrypted buffers, or remove encryption from this buffer.
See Also
tpseal, tpkey_open
6190
ERROR: Signature verification fails to interoperating site
Description
Buffers signed with an explicit call to tpsign or with
an auto-sign key are verified by the Tuxedo system
before being sent to older sites. However, a message failed its signature
verification.
Action
The signature may have expired, or it may have been tampered with. Check the security of the system, and investigate any failure audit points.
See Also
tpsign, tpkey_open
6191
ERROR: Attempt to send encrypted buffer to interoperating site
Description
Buffers encrypted with an explicit call to tpseal or with
an auto-encrypt key cannot be sent to a site with a version of the BEA Tuxedo system older than Release 7.1.
Action
Do not configure services in older domains that might have an encrypted buffer sent to them.
See Also
tpseal, tpkey_open
6192
ERROR: Attempt to send encrypted buffer to interoperating site
Description
Buffers encrypted with an explicit call to tpseal or with
an auto-encrypt key cannot be sent to a site with a version of the BEA Tuxedo system older than Release 7.1.
Action
Do not configure services in older domains that might have an encrypted buffer sent to them.
See Also
tpseal, tpkey_open
6193
ERROR: Signature verification fails to interoperating site
Description
Buffers signed with an explicit call to tpsign or with
an auto-sign key are verified by the Tuxedo system
before being sent to older sites. However, a message failed its signature
verification.
Action
The signature may have expired, or it may be tampered. Check the security of the system, and investigate any failure audit points.
See Also
tpsign, tpkey_open
6194
ERROR: Attempt to send encrypted buffer to interoperating site
Description
Buffers encrypted with an explicit call to tpseal or with
an auto-encrypt key cannot be sent to a site with a version of the BEA Tuxedo system older than Release 7.1.
Action
Do not configure services in older domains that might have an encrypted buffer sent to them.
See Also
tpseal, tpkey_open
6195
ERROR: Attempt to send encrypted buffer to interoperating site
Description
Buffers encrypted with an explicit call to tpseal or with
an auto-encrypt key cannot be sent to a site with a version of the BEA Tuxedo system older than Release 7.1.
Action
Do not configure services in older domains that might have an encrypted buffer sent to them.
See Also
tpseal, tpkey_open
6196
ERROR: Signature verification fails to interoperating site
Description
Buffers signed with an explicit call to tpsign or with
an auto-sign key are verified by the Tuxedo system
before being sent to older sites. However, a message failed its signature
verification.
Action
The signature may have expired, or it may be tampered. Check the security of the system, and investigate any failure audit points.
See Also
tpsign, tpkey_open
6197
ERROR: Attempt to send encrypted buffer to interoperating site
Description
Buffers encrypted with an explicit call to tpseal or with
an auto-encrypt key cannot be sent to a site with a version of the BEA Tuxedo system older than Release 7.1.
Action
Do not configure services in older domains that might have an encrypted buffer sent to them.
See Also
tpseal, tpkey_open
6198
ERROR: Invalid buffer passed to workstation encode/decode routine
Description
An invalid buffer was passed by the system into an internal encoding routine.
Action
Contact BEA Customer Support.
6199
ERROR: Could not find sufficient information to decode/encode message
Description
An invalid buffer was passed by the system into an internal encoding routine.
Action
Contact BEA Customer Support.
 |
 |
 |