![]() |
![]() |
|
|
1 |
ERROR: Exception in Server::initialize(): exception id. Reason = reason | |
|
Description |
Either application code raised an exception in |
Action |
Notify the programmer. | |
2 |
WARN: Exception in Server::release(): exception id. Reason = reason | |
|
Description |
Either application code raised an exception in |
Action |
Notify the programmer. | |
5 |
WARN: TP::deactivateEnable() called in illegal context. Called in Server::initialize() or Server::release(). | |
|
Description |
The application called |
Action |
Notify the programmer. Call to | |
6 |
WARN: TP::deactivateEnable() called illegally - object has transaction activation policy. | |
|
Description |
The application called |
Action |
Notify the programmer. | |
7 |
ERROR: Invoking request - interface not advertised: interfaceName. | |
|
Description |
The object reference invoked by a client is for an interface that is unknown to the system. Possible reasons are:
|
Action |
Check the status of the interface. It may be suspended. If you cannot find the interface in the system, notify the programmer. | |
8 |
WARN: Application didn't catch TobjS exception. TP Framework throwing CORBA::BAD_OPERATION. | |
|
Description |
The system caught an exception defined in the TobjS idl module after invoking a method of a CORBA object. This warning indicates that either:
|
Action |
Notify the programmer. | |
9 |
WARN: Application called TP::deactivateEnable() illegally and didn't catch TobjS exception. | |
|
Description |
The system caught a The possible reasons are:
|
Action |
Notify the programmer. | |
11 |
ERROR: Non-transactional invocation on CORBA object infected with a transaction | |
|
Description |
An invocation was made without an active transaction on an object that is participating in a global transaction. This error can occur if a client sends a request to a CORBA object that is participating in a transaction started for another client. It can also occur if a call is made immediately after a transaction has been marked for rollback only. There is a small delay while the transaction-termination processing is completed by the transaction manager when the transaction is still active. This error is generally detected in a |
Action |
If many such messages are seen, notify the programmer. If loop processing is being done, | |
21 |
ERROR: Illegal recursive call on CORBA Object. Interface = interfaceName, OID = object ID | |
|
Description |
A recursive call was made on a CORBA object. This error occurs if, for example, a client calls object A, which calls object B, which uses an object reference to object A to invoke a method of object A. The second call to object A causes this error message to be printed to the user log and a |
Action |
Notify the programmer. | |
22 |
ERROR: Activating object - application raised TobjS::OutOfMemory. Interface = interfaceName, OID = object ID. | |
|
Description |
The system caught |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
23 |
ERROR: Activating object - application raised TobjS::CreateServantFailed. Reason = reason. Interface = interfaceName, OID = object ID | |
|
Description |
The application raised |
Action |
Application dependent. Notify your company's technical support or the application programmer. | |
24 |
ERROR: Activating object - application raised TobjS::ActivateObjectFailed. Reason = servicename. Interface = interfaceName, OID = object ID | |
|
Description |
The system caught |
Action |
Application dependent. Notify your company's technical support or the application programmer. | |
25 |
ERROR: Activating object - CORBA Exception not handled by application. Exception ID = exception ID. Interface = InterfaceName, OID = object ID | |
|
Description |
The system caught a CORBA exception raised by either |
Action |
Application dependent. Notify your company's technical support or the application programmer. | |
26 |
ERROR: Activating object - Unknown exception not handled by application. Interface = InterfaceName, OID = object ID | |
|
Description |
The system caught an unknown exception raised by either |
Action |
Application dependent. Notify your company's technical support or the application programmer. | |
27 |
ERROR: De-activating object - application raised TobjS::DeactivateObjectFailed. Reason = reason. Interface = interfaceName, OID = object ID | |
|
Description |
The system caught a |
Action |
Application dependent. Notify your company's technical support or the application programmer. | |
28 |
ERROR: De-activating object - CORBA Exception not handled by application. Exception ID = exception ID. Interface = InterfaceName, OID = object ID | |
|
Description |
The system caught a CORBA exception raised in |
Action |
Application dependent. Notify your company's technical support or the application programmer. | |
29 |
ERROR: De-activating object - Unknown exception not handled by application. Interface = InterfaceName, OID = object ID | |
|
Description |
The system caught an unknown exception raised in |
Action |
Application dependent. Notify your company's technical support or the application programmer. | |
30 |
ERROR: Exception in thread_initialize(): ID. Reason = Reason | |
|
Description |
This is probably an application or system resource problem. |
Action |
Check the application code and the operating system configuration to ensure that enough resources are configured. Save the value of Reason and contact BEA Customer Support for additional help, if necessary. | |
31 |
WARN: Exception in thread_release(): ID. Reason = Reason | |
|
Description |
This is probably an application problem. |
Action |
Check the application code. Save the value of Reason and contact BEA Customer Support for additional help, if necessary. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|