1900
|
ERROR: Cannot join application in multi-context mode
|
|
|
Description
|
A /WS client called tpinit with the
TPMULTICONTEXTS flag set, but
the client had already joined the application without
this flag set and has not done an intervening tpterm.
|
|
Action
|
Ensure that all calls to tpinit are done with the
TPMULTICONTEXTS flag set or do a
tpterm before the tpinit.
tpinit will fail with TPEPROTO.
|
|
See Also
|
tpinit(3), tpterm(3)
|
1901
|
ERROR: Failed to create a new context in multi-context mode
|
|
|
Description
|
The /WS client tried to create a new context and failed.
This indicates that either a mutex lock failed or a dynamic
memory allocation failed (usually the latter).
|
|
Action
|
Ensure that 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.
|
|
|
|
1902
|
ERROR: Failed to set context to newly created context
|
|
|
Description
|
A /WS client failed to set the context that was created in
tpinit.
|
|
Action
|
This should not occur. Contact BEA Customer Support.
|
|
|
|
1903
|
ERROR: Cannot join application in single-context mode
|
|
|
Description
|
A /WS client called tpinit without the
TPMULTICONTEXTS flag but tpinit
has already been called with that flag and there has
not been an intervening call to tpterm.
|
|
Action
|
Ensure that all calls to tpinit are done without the
TPMULTICONTEXTS flag set or do a
tpterm before the tpinit.
tpinit will fail with TPEPROTO.
|
|
See Also
|
tpinit(3), tpterm(3)
|
1904
|
INFO: Switched to dip-in based notification
|
|
|
Description
|
A /WS client program did not specify a notification
method and the default notification method for notification
is THREAD.
However, the platform does not support threads so the
notification method will be downgraded to DIPIN.
|
|
Action
|
No action required.
|
|
See Also
|
tpinit(3), ubbconfig(5)
|
1906
|
ERROR: Unable to append unsolicited recipient information
|
|
|
Description
|
While attempting an unsolicited message notification, the client was unable
to attach routing information to the buffer.
|
|
Action
|
Contact BEA Customer Support.
|
|
See Also
|
tpnotify, tpbroadcast, tpsetunsol,
tpchkunsol
|
1907
|
ERROR: Improper workstation message
|
|
|
Description
|
While attempting an unsolicited message notification, the client found
a malformed message.
|
|
Action
|
Contact BEA Customer Support.
|
|
See Also
|
tpnotify, tpbroadcast, tpsetunsol,
tpchkunsol
|
1908
|
ERROR: Improper workstation message
|
|
|
Description
|
A message received in receipt of an unsolicited message was malformed.
|
|
Action
|
Contact BEA Customer Support.
|
|
See Also
|
tpnotify, tpbroadcast, tpsetunsol,
tpchkunsol
|
1909
|
ERROR: Unable to reset internal buffer
|
|
|
Description
|
An internal buffer used by the workstation client is corrupted.
|
|
Action
|
Contact BEA Customer Support.
|
|
|
|
1910
|
ERROR: Memory allocation failure
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system using malloc failed.
|
|
Action
|
Ensure that 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.
|
|
|
|
1911
|
ERROR: Memory allocation failure
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system using malloc failed.
|
|
Action
|
Ensure that 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.
|
|
|
|
1912
|
ERROR: Unable to retrieve a stored message reply
|
|
|
Description
|
While receiving a reply message, a /WS client was unable to
process the stored message replies.
Currently, this can only happen if a mutex lock fails.
|
|
Action
|
Contact BEA Customer Support.
|
|
|
|
1913
|
ERROR: Unable to save an unsolicited message
|
|
|
Description
|
While getting an in-coming message, a /WS client was
unable to store the message.
This can occur if a mutex lock or memory allocation fails.
|
|
Action
|
Check the log for related messages.
|
|
|
|
1915
|
ERROR: Unable to save a message reply
|
|
|
Description
|
While receiving an in-coming message, a /WS client was
unable to store the message.
This can occur if a mutex lock or memory allocation fails.
|
|
Action
|
Check the log for related messages.
|
|
|
|
1917
|
ERROR: tpsetunsol() not called, dropping unsolicited message.
|
|
|
Description
|
An unsolicited message was received in a /WS client that
did not previously call tpsetunsol.
The message will be dropped.
|
|
Action
|
Call tpsetunsol in the /WS client to receive
unsolicited messages.
|
|
See Also
|
tpsetunsol(3)
|
1918
|
ERROR: tpcommit() error due to failed attempt to lock mutex
|
|
|
Description
|
In a /WS client, tpcommit failed because
a mutex lock failed. tperrno will
be set to TPESYSTEM
|
|
Action
|
Contact BEA Customer Support.
|
|
See Also
|
tpcommit(3)
|
1919
|
ERROR: tpabort() error due to failed attempt to lock mutex
|
|
|
Description
|
In a /WS client, tpabort failed because
a mutex lock failed. tperrno will
be set to TPESYSTEM
|
|
Action
|
Contact BEA Customer Support.
|
|
See Also
|
tpabort(3)
|
1920
|
ERROR: Failed to acquire mutex
|
|
|
Description
|
In a /WS client, receiving a message failed because
a mutex lock failed. tperrno will
be set to TPESYSTEM
|
|
Action
|
Contact BEA Customer Support.
|
|
|
|
1921
|
ERROR: tpsuspend() error due to failed attempt to lock mutex
|
|
|
Description
|
An internal error occurred in locking a mutex.
|
|
Action
|
Contact BEA Customer Support.
|
|
|
|
1922
|
ERROR: tpresume() error due to failed attempt to lock mutex
|
|
|
Description
|
An internal error occurred in locking a mutex.
|
|
Action
|
Contact BEA Customer Support.
|
|
|
|
1923
|
ERROR: tpbegin() error due to failed attempt to lock mutex
|
|
|
Description
|
An internal error occurred in locking a mutex.
|
|
Action
|
Contact BEA Customer Support.
|
|
|
|
1924
|
ERROR: tpacall() context terminated by another thread in this process
|
|
|
Description
|
A tpacall() call made within a BEA Tuxedo system 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
tpacall() call returns failure and this message is written to
the userlog. The thread invoking tpacall() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1925
|
ERROR: tpgetrply() context terminated by another thread in this process
|
|
|
Description
|
A tpgetrply() call made within a BEA Tuxedo system 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
tpgetrply() call returns failure and this message is written to
the userlog. The thread invoking tpgetrply() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1926
|
ERROR: context terminated by another thread in this process
|
|
|
Description
|
An ATMI call made within a BEA Tuxedo system 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, this
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 tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1927
|
ERROR: tpcall() context terminated by another thread in this process
|
|
|
Description
|
A tpcall() call made within a BEA Tuxedo system 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
tpcall() call returns failure and this message is written to
the userlog. The thread invoking tpcall() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1928
|
ERROR: tpconnect() context terminated by another thread in this process
|
|
|
Description
|
A tpconnect() call made within a BEA Tuxedo system 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
tpconnect() call returns failure and this message is written to
the userlog. The thread invoking tpconnect() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1929
|
ERROR: tpdiscon() context terminated by another thread in this process
|
|
|
Description
|
A tpdiscon() call made within a BEA Tuxedo system 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
tpdiscon() call returns failure and this message is written to
the userlog. The thread invoking tpdiscon() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1930
|
ERROR: tprecv() context terminated by another thread in this process
|
|
|
Description
|
A tprecv() call made within a BEA Tuxedo system 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
tprecv() call returns failure and this message is written to
the userlog. The thread invoking tprecv() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1931
|
ERROR: tpsend() context terminated by another thread in this process
|
|
|
Description
|
A tpsend() call made within a BEA Tuxedo system 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
tpsend() call returns failure and this message is written to
the userlog. The thread invoking tpsend() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1932
|
ERROR: tpnotify() context terminated by another thread in this process
|
|
|
Description
|
A tpnotify() call made within a BEA Tuxedo system 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
tpnotify() call returns failure and this message is written to
the userlog. The thread invoking tpnotify() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1933
|
ERROR: tpbroadcast() context terminated by another thread in this process
|
|
|
Description
|
A tpbroadcast() call made within a BEA Tuxedo system 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
tpbroadcast() call returns failure and this message is written to
the userlog. The thread invoking tpbroadcast() is placed in an
invalid context and must issue tpsetctxt() or tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
|
|
|
1934
|
ERROR: context terminated by another thread in this process
|
|
|
Description
|
An ATMI call made within a BEA Tuxedo system 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, this
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 tpterm()
before it can again invoke most ATMI verbs.
|
|
Action
|
A thread which receives this message must call tpsetctxt()
or tpterm() 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.
|
