System Messages: GWWS Catalog 0-99
|
|
|
|
1 |
ERROR: Internal memory allocation failed. | |
|
|
Description |
GWWS failed to get memory from the system. |
|
Action |
Check system memory consumption. Make sure enough RAM is installed. If problem persists, contact Oracle Customer Support. | |
|
2 |
ERROR: GWWS message mutex initialization failed. | |
|
|
Description |
GWWS cannot initialize the message protection mutex. |
|
Action |
Try to shutdown GWWS and then reboot. If problem persists,contact Oracle Customer Support. | |
|
3 |
ERROR: GWWS message conditional variable initialization failed. | |
|
|
Description |
GWWS cannot initialize conditional variable for the message protection. |
|
Action |
Try to shutdown GWWS and then reboot. If problem persists, contact Oracle Customer Support. | |
|
4 |
ERROR: GWWS message failed to destroy mutex. | |
|
|
Description |
GWWS cannot destroy the message protection mutex during shutdown. This is an operating system error. |
|
Action |
Ignore this message. If problem persists, contact Oracle Customer Support. | |
|
5 |
ERROR: GWWS message failed to destroy conditional variable. | |
|
|
Description |
GWWS cannot destroy the message related conditional variable during shutdown. This is an operating system error. |
|
Action |
Ignore this message. If problem persists, contact Oracle Customer Support. | |
|
6 |
ERROR: GWWS message mutex lock failed. | |
|
|
Description |
GWWS cannot lock message protection mutex. This is an operating system error. |
|
Action |
Try to shutdown GWWS and then reboot. If problem persists, contact Oracle Customer Support. | |
|
7 |
ERROR: GWWS must have a separate reply queue. | |
|
|
Description |
GWWS maintains an independent reply queue separate from the request queue. REPLYQ=Y can be specified for GWWS in UBBCONFIG, or GWWS will create the reply queue. This error indicates the GWWS reply queue is same as the request queue. |
|
Action |
Try to shutdown GWWS and then reboot. If problem persists, contact Oracle Customer Support. | |
|
8 |
ERROR: Invalid GWWS command line argument 'option'. | |
|
|
Description |
Invalid GWWS option in UBBCONFIG file. "-i" is the only valid GWWS option. |
|
Action |
Give a valid CLOPT option for GWWS in UBBCONFIG. | |
|
See Also |
| |
|
9 |
ERROR: Invalid GWWS CLOPT option, -i must be used. | |
|
|
Description |
Invalid GWWS option in UBBCONFIG file. "-i" is the only valid GWWS option. |
|
Action |
Give a valid CLOPT option for GWWS in UBBCONFIG. | |
|
See Also |
| |
|
10 |
ERROR: GWWS cannot switch to client context. | |
|
|
Description |
GWWS cannot switch to client context when calling Tuxedo application service. |
|
Action |
Try to shutdown GWWS and then reboot. If problem persists, contact Oracle Customer Support. | |
|
11 |
ERROR: Invald Tuxedo typed buffer. | |
|
|
Description |
Tuxedo reports an invalid typed buffer from SOAP message. |
|
Action |
Contact Oracle Customer Support. | |
|
12 |
ERROR: GWWS failed to call service_name service. | |
|
|
Description |
GWWS failed to call Tuxedo application service. |
|
Action |
Check Tuxedo service status for availability. | |
|
13 |
ERROR: Tuxedo reports error error message. | |
|
|
Description |
Tuxedo reports error information. |
|
Action |
Take specific action to correct the error report according to the error message. | |
|
14 |
ERROR: GWWS failed to receive message from IPC queue. | |
|
|
Description |
GWWS cannot receive messages from IPC queue. Usually, this is an operating system error. |
|
Action |
Try to shutdown GWWS and reboot. If problem persists, contact Oracle Customer Support. | |
|
15 |
ERROR: GWWS cannot find machine parameters. | |
|
|
Description |
GWWS cannot to get machine information from TUXCONFIG file. |
|
Action |
Check TUXCONFIG for consistency and integrity, or regenerate it using tmloadcf. If problem persists, contact Oracle Customer Support. | |
|
16 |
ERROR: GWWS cannot create reply queue. | |
|
|
Description |
GWWS failed to create the reply queue on start up |
|
Action |
Contact Oracle Customer Support. | |
|
17 |
ERROR: Invalid GWWS CLOPT option. | |
|
|
Description |
Invalid GWWS option in UBBCONFIG file. "-i" is the only valid GWWS option. |
|
Action |
Give a valid CLOPT option for GWWS in UBBCONFIG. | |
|
See Also |
| |
|
18 |
ERROR: Cannot create GWWS context. | |
|
|
Description |
GWWS failed to create internal context. |
|
Action |
Contact Oracle Customer Support. | |
|
19 |
INFO: GWWS started. | |
|
|
Description |
GWWS started normally. |
|
Action |
None | |
|
20 |
INFO: GWWS exiting system. | |
|
|
Description |
GWWS is exiting system |
|
Action |
None | |
|
21 |
WARNING: Tuxedo service returns TPFAIL. | |
|
|
Description |
Tuxedo application service returns TPFAIL status code. |
|
Action |
Check the service implementation. | |
|
22 |
ERROR: Tuxedo service encountered internal error. | |
|
|
Description |
Tuxedo application service returns TPESVCERR status code. |
|
Action |
Check the service implementation and related Tuxedo configuration. | |
|
23 |
ERROR: System error occurred while receiving message. | |
|
|
Description |
GWWS encountered system error when receiving message from IPC queue. |
|
Action |
Check the IPC queue status using IPC related system commands. If problem persists, contact Oracle Customer Support. | |
|
24 |
ERROR: Received invalid Tuxedo message. | |
|
|
Description |
GWWS received an invalid Tuxedo typed buffer. |
|
Action |
Check the Tuxedo application service implementation. If problem persists, contact Oracle Customer Support. | |
|
28 |
ERROR: Network Layer initialization failed. | |
|
|
Description |
GWWS cannot start the network transport module. |
|
Action |
Check GWWS network configuration in the XML configuration file. Make sure the address, port, and security related settings are correct. | |
|
See Also |
| |
|
29 |
ERROR: Storage Layer initialization failed. | |
|
|
Description |
GWWS failed to initialize the internal storage layer. |
|
Action |
Contact Oracle Customer Support. | |
|
30 |
ERROR: Thread Pool initialization failed. | |
|
|
Description |
GWWS failed to initialize the internal thread pool. |
|
Action |
Contact Oracle Customer Support. | |
|
31 |
ERROR: Cannot boot GWWS. MAXWSCLIENTS must be larger than 0. | |
|
|
Description |
MAXWSCLIENTS must be set with a valid positive number in the UBBCONFIG file for the machines where GWWS servers are deployed. Each Web service client is deemed a Tuxedo workstation client. |
|
Action |
Set MAXWSCLIENTS with a valid value in UBBCONFIG file for the machines where GWWS servers are deployed. | |
|
See Also |
| |
|
32 |
ERROR: GWWS cannot get server parameters. | |
|
|
Description |
GWWS failed to get server parameter information from TUXCONFIG file. |
|
Action |
Check TUXCONFIG file for consistency and integrity, or regenerate it using tmloadcf. If problem persists, contact Oracle Customer Support. | |
|
33 |
ERROR: REPLYQ=Y must be set when using RESTART=Y for GWWS. | |
|
|
Description |
When RESTART=Y is set for GWWS in UBBCONFIG, REPLYQ=Y also must be set. |
|
Action |
Set REPLYQ=Y when RESTART=Y is set for GWWS. | |
|
See Also |
| |
|
34 |
ERROR: Instance ID is too long. | |
|
|
Description |
The GWWS instance ID is too long. |
|
Action |
Make sure the GWWS instance ID length is less than or equal to 12. | |
|
See Also |
| |
|
35 |
ERROR: Cannot open TUXCONFIG file when authenticating request. | |
|
|
Description |
GWWS cannot find TUXCONFIG file to authenticate clients. |
|
Action |
Check TUXCONFIG file availability and integrity. | |
|
36 |
ERROR: Cannot read RESOURCE contents from TUXCONFIG file. | |
|
|
Description |
GWWS cannot read RESOURCE contents from TUXCONFIG file. |
|
Action |
Check TUXCONFIG file for consistency and integrity, or regenerate it using tmloadcf. | |
|
37 |
ERROR: Application password does not match. | |
|
|
Description |
The application password passed from Web service clients through HTTP basic authentication does not match Tuxedo application password. |
|
Action |
Make sure clients send a correct application password when APP_AUTH is set in Tuxedo domain. | |
|
38 |
ERROR: tpcall(authsvc) failed, authsvc name . | |
|
|
Description |
GWWS cannot call AUTHSVC when USER_AUTH is set in Tuxedo domain. |
|
Action |
Make sure AUTHSVR is configured and runs correctly when USER_AUTH or above authentication is defined in Tuxedo domain. | |
|
39 |
ERROR: Failed to initialize reliable messaging module. | |
|
|
Description |
GWWS failed to initialize reliable messaging module when WS-RM policy file is specified in SALT configuration. |
|
Action |
Contact Oracle Customer support. | |
|
40 |
ERROR: Unable to read key. | |
|
|
Description |
GWWS cannot read TUXCONFIG file encryption key when SSL is set for GWWS. |
|
Action |
Contact Oracle Customer support. | |
|
41 |
ERROR: Unable to generate decryption schedule. | |
|
|
Description |
GWWS cannot generate needed decryption data structure when SSL is set for GWWS. |
|
Action |
Contact Oracle Customer support. | |
|
42 |
ERROR: Unable to decrypt password. | |
|
|
Description |
GWWS cannot decrypt password when SSL is set for GWWS. |
|
Action |
Contact Oracle Customer support. | |
|
43 |
ERROR: Failed to advertise GWWS internal service. | |
|
|
Description |
GWWS cannot advertise the internal administration service. |
|
Action |
Contact Oracle Customer support. | |
|
44 |
ERROR: Cannot find definition for instance instance_id in the configuration. | |
|
|
Description |
GWWS cannot find the supplied instance ID in SALT configuration. |
|
Action |
Make sure the instance ID is consistent in UBBCONFIG file and SALT deployment file. | |
|
45 |
ERROR: GWWS statistics data mutex initialization failed. | |
|
|
Description |
GWWS cannot initialize statistics data mutex. |
|
Action |
Try to shutdown GWWS and reboot. If problem persists, contact Oracle Customer Support. | |
|
46 |
ERROR: GWWS statistics data mutex lock failed. | |
|
|
Description |
GWWS cannot lock statistics data mutex. |
|
Action |
Try to shutdown GWWS and reboot. If problem persists, contact Oracle Customer Support. | |
|
47 |
ERROR: Failed to start GWWS instance 'instance ID'. Another instance already started. | |
|
|
Description |
GWWS failed to start because another GWWS is running using same instance ID. The GWWS instance ID must be unique within each Tuxedo domain. |
|
Action |
Make sure the GWWS instance ID is unique within one Tuxedo domain. | |
|
48 |
ERROR: Context Extension initialization failure. | |
|
|
Description |
GWWS failed to create extension for a message-processing context. |
|
Action |
System resource may be exhausted. Reboot the system. | |
|
49 |
ERROR: Server listening thread initialization failure. | |
|
|
Description |
GWWS failed to start the thread to listen on certain network address and port. |
|
Action |
Check if the network address is correct and the port is not occupied. | |
|
50 |
WARNING: Deprecated option opt_val in GWWS CLOPT. | |
|
|
Description |
GWWS is given a deprecated option in UBBCONFIG file. "-i" is the only valid GWWS option. |
|
Action |
Give a valid CLOPT option for GWWS in UBBCONFIG. | |
|
See Also |
| |
|
53 |
ERROR: GWWS failed to impersonate user 'user-name'. | |
|
|
Description |
If Tuxedo domain security attribute is configured to ACL or MANDATORY_ACL, GWWS impersonates the client's role to perform the Tuxedo service call. This error message is issued if the impersonate process failed. |
|
Action |
Contact Oracle Customer support. | |
|
54 |
ERROR: Failed to invoke service for access control violation. | |
|
|
Description |
If Tuxedo domain security attribute is configured to ACL or MANDATORY_ACL, ACL controls inbound web service calls. This error message is issued when a request violates the ACL. |
|
Action |
Contact system administrator to check if the client can access the service. | |
|
60 |
ERROR: Cannot generate a new UUID for wsa:MessageID. | |
|
|
Description |
GWWS failed to generate message ID with UUID format. |
|
Action |
Contact Oracle Customer support. | |
|
61 |
ERROR: GWWS sequence table mutex initialization failed. | |
|
|
Description |
GWWS failed to initialize reliable message related sequence table mutex. |
|
Action |
Contact Oracle Customer support. | |
|
62 |
ERROR: GWWS sequence table mutex destroy failed. | |
|
|
Description |
GWWS failed to destroy reliable message related sequence table mutex. |
|
Action |
Contact Oracle Customer support. | |
|
63 |
ERROR: GWWS sequence mutex lock failed. | |
|
|
Description |
GWWS failed to lock sequence mutex. |
|
Action |
Contact Oracle Customer support. | |
|
64 |
ERROR: GWWS sequence mutex initialization failed. | |
|
|
Description |
GWWS cannot initialize reliable message related sequence mutex. |
|
Action |
Contact Oracle Customer support. | |
|
65 |
ERROR: GWWS sequence mutex destroy failed. | |
|
|
Description |
GWWS failed to destroy sequence mutex. |
|
Action |
Contact Oracle Customer support. | |
|
66 |
ERROR: Cannot initialize sequence. | |
|
|
Description |
GWWS failed to initialize sequence. |
|
Action |
Contact Oracle Customer support. | |
|
67 |
ERROR: Cannot insert a new sequence in the table. | |
|
|
Description |
GWWS failed to insert a new reliable message sequence in the sequence table. |
|
Action |
Contact Oracle Customer support. | |
|
68 |
ERROR: Cannot compose CreateSequenceResponse message. | |
|
|
Description |
GWWS failed to compose CreateSequenceResponse message in response to CreateSequence message from source endpoint. |
|
Action |
Contact Oracle Customer support. | |
|
69 |
ERROR: Cannot compose SequenceAcknowledgement message. | |
|
|
Description |
GWWS failed to compose SequenceAcknowledgement message. This message is an ACK for application message in a reliable message sequence. |
|
Action |
Contact Oracle Customer support. | |
|
70 |
ERROR: Unknown SOAP request. | |
|
|
Description |
GWWS failed to parse the SOAP request from client. |
|
Action |
Check the client SOAP message and make sure that the message format matches the GWWS WSDL file requirement. A common cause for this problem is the client uses an outdated WSDL. | |
|
71 |
ERROR: WS-Addressing validation failed. | |
|
|
Description |
The WS-Addressing message from client is not valid. It may contain content not conforming to WS-Addressing specification. |
|
Action |
First check SOAP message with WS-Addressing specification. If problem persists, Contact Oracle Customer support. | |
|
72 |
ERROR: WS-ReliableMessaging validation failed. | |
|
|
Description |
The WS-ReliableMessaging message from client is not valid. It may contain content not conforming to WS-ReliableMessaging specification. |
|
Action |
First check SOAP message with WS-ReliableMessaging specification. If problem persists, Contact Oracle Customer support. | |
|
73 |
ERROR: Cannot create WS-ReliableMessaging housekeeping thread. | |
|
|
Description |
GWWS failed to start reliable messaging housekeeping thread. |
|
Action |
Contact Oracle Customer support. | |
|
74 |
INFO: GWWS instance ID started with reliable messaging feature. | |
|
|
Description |
GWWS started with reliable messaging support if a valid WS-RM policy file is set in configuration file. |
|
Action |
No action required. | |
|
75 |
ERROR: Plug-in Framework initialization failed. | |
|
|
Description |
GWWS failed to initialize all Plug-in interfaces. |
|
Action |
Contact Oracle Customer support. 77 | |
|
75 |
ERROR: Internal processing error | |
|
|
Description |
An internal error occurred when processing HTTP request. |
|
Action |
Contact Oracle Customer support. 78 | |
|
75 |
ERROR: Internal processing error | |
|
|
Description |
An internal error occurred when processing HTTP request. |
|
Action |
Contact Oracle Customer support. | |
 |
 |
 |