![]() |
![]() |
|
|
1000 |
"ERROR : internal error : val" | |
|
Description |
An internal error occurred. |
Action |
Execution was interrupted by an internal error. Make note of the exact location and nature of error printed as part of the message. Contact BEA Customer Support. | |
1001 |
"ERROR : out of memory : val" | |
|
Description |
An attempt to dynamically allocate memory failed. The location of the failure and object for which memory allocation failed may be printed as part of the message. |
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. | |
1002 |
"ERROR : unexpected CORBA::SystemException : val" | |
|
Description |
An unexpected |
Action |
Execution was interrupted by an unexpected | |
1003 |
"ERROR : unexpected CORBA::Exception : val" | |
|
Description |
An unexpected |
Action |
Execution was interrupted by an unexpected | |
1004 |
"ERROR : unexpected exception : val" | |
|
Description |
An unexpected exception was encountered. |
Action |
Execution was interrupted by an unexpected exception. Make note of the location and kind of the unexpected exception printed as part of the message and contact BEA Customer Support. | |
1020 |
"syntax error. syntax = val" | |
|
Description |
The syntax specified to start this server process was incorrect. |
Action |
Reconfigure the Notification Service using the proper syntax, and reboot the failed server. | |
1021 |
"INFO : val has successfully started." | |
|
Description |
The val server process has started successfully. |
Action |
No action required. | |
1022 |
"ERROR : val has not successfully started." | |
|
Description |
The val server process could not be started. |
Action |
Related messages in the userlog will indicate the nature of the problem. You may need to take appropriate steps. For example, shut down the servers, clean up the IPC resources, and then reboot the servers. | |
1023 |
"INFO : val has shut down." | |
|
Description |
The val server process has been shut down. |
Action |
No action required. | |
1024 |
"WARN : callback for val doesn't exist" | |
|
Description |
The server failed to deliver the event to a subscriber because there was no callback object for subscription id val. |
Action |
Check the userlog for related messages indicating the nature of the problem. If this is unexpected behavior, check your implementation of the callback object for proper usage of the POA and/or BEAWrapper. | |
1025 |
"WARN : dropping subscription for val" | |
|
Description |
Since the server encountered an error, or can not find a callback for subscription id val, it will not be able to deliver further events to this subscriber. It is therefore dropping this subscription. |
Action |
No action required. | |
1040 |
"ERROR : syntax error. syntax = val [-s qspace]" | |
|
Description |
The syntax specified to start the val server process was incorrect. |
Action |
Reconfigure the Notification Service using the proper syntax, and reboot the failed server. | |
1041 |
"ERROR : transient only configuration" | |
|
Description |
Your configuration of the Notification Service can only support transient subscriptions. |
Action |
If you intend to support persistent subscriptions, reconfigure the Notification Service using a persistent configuration, and reboot the servers. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|