GWWS Messages 0-99
|
|
|
1
ERROR: Internal memory allocation failed
Description
GWWS failed to get memory from the system.
Action
Check the system memory consumption. Make sure that there is enough RAM installed. If the problem persists, contact BEA Customer Support.
2
ERROR: GWWS message mutex initialization failed
Description
GWWS cannot initialize the message related thread mutex.
Action
Try to shutdown GWWS then reboot it. If the problem persists,contact BEA Customer Support.
3
ERROR: GWWS message conditional variable initialization failed
Description
GWWS cannot initialize the message related thread conditional variable.
Action
Try to shutdown GWWS then reboot it. If the problem persists,contact BEA Customer Support.
4
ERROR: GWWS message failed to destroy mutex
Description
GWWS cannot destroy the message related mutex during shutdown.This is an operating system error.
Action
You can ignore this message. If the problem persists, contact BEA 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
You can ignore this message. If the problem persists, contact BEA 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 then reboot it. If the problem persists,contact BEA 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 with request queue that unlikely happen.
Action
Try to shutdown GWWS then reboot it. If the problem persists,contact BEA Customer Support.
8
ERROR: Invalid GWWS command line argument option
Description
GWWS is given an invalid option in UBBCONFIG file. "-c" and "-i" are the only valid GWWS options.
Action
Give a valid CLOPT option for GWWS in UBBCONFIG.
See Also
GWWS
9
ERROR: Invalid GWWS CLOPT option, -c and -i must be given
Description
GWWS is given an invalid option in UBBCONFIG file. "-c" and "-i" are the only valid GWWS options.
Action
Give a valid CLOPT option for GWWS in UBBCONFIG.
See Also
GWWS
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 then reboot it. If the problem persists,contact BEA Customer Support.
11
ERROR: Invald Tuxedo typed buffer
Description
Tuxedo reports an invalid typed buffer from SOAP message.
Action
Contact BEA Customer Support.
12
ERROR: GWWS failed to call service name service
Description
GWWS failed to call Tuxedo application service.
Action
Check Tuxedo service status, make sure it is available and healthy.
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 get message from IPC queue
Description
GWWS cannot get messages from IPC queue. Usually, this is an operating system error.
Action
Try to shutdown GWWS then reboot it. If the problem persists,contact BEA Customer Support.
15
ERROR: GWWS cannot get 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 the problem persists, contact BEA Customer Support.
16
ERROR: GWWS cannot create reply queue
Description
GWWS failed to create the reply queue on start up
Action
Contact BEA Customer Support.
17
ERROR: Invalid GWWS CLOPT option
Description
GWWS is given an invalid option in UBBCONFIG file. "-c" and "-i" are the only valid GWWS options.
Action
Give a valid CLOPT option for GWWS in UBBCONFIG.
See Also
GWWS
18
ERROR: Cannot create GWWS context
Description
GWWS failed to create internal context.
Action
Contact BEA Customer Support.
19
INFO: GWWS started
Description
GWWS started normally.
Action
20
INFO: GWWS exiting system
Description
GWWS is exiting system
Action
21
ERROR: Tuxedo service returns TPFAIL
Description
Tuxedo application service returns TPFAIL status code explicitly.
Action
Check the service implementation.
22
ERROR: Tuxedo service encountered internal error
Description
Tuxedo application service returns TPESVCERR status code explicitly.
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 the problem persists,contact BEA Customer Support.
24
ERROR: Received invalid Tuxedo message
Description
GWWS received an invalid Tuxedo typed buffer.
Action
Check the implementation of Tuxedo application service.If the problem persists,contact BEA 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,security related settings are correct.
See Also
GWWS
29
ERROR: Storage Layer initialization failed
Description
GWWS failed to initialize the internal storage layer.
Action
Contact BEA Customer Support.
30
ERROR: Thread Pool initialization failed
Description
GWWS failed to initialize the internal thread pool.
Action
Contact BEA Customer Support.
31
ERROR: Cannot boot GWWS. MAXWSCLIENTS set to 0
Description
MAXWSCLIENTS must be set with a valid value in UBBCONFIG file on the system where GWWS is deployed. Each web service client is deemed a Tuxedo workstation client.
Action
Set MAXWSCLIENTS with a valid value in UBBCONFIG file on the system where GWWS is deployed.
See Also
BEA SALT Administration Guide
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 the problem persists, contact BEA 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
BEA SALT Administration Guide
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 or equal 12.
See Also
BEA SALT Administration Guide
35
ERROR: Cannot open TUXCONFIG file in authentication
Description
GWWS cannot find TUXCONFIG file to authenticate clients.
Action
Make sure TUXCONFIG file is accessible and valid.
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 WSRM policy file is specified in SALT configuration file.
Action
Contact BEA Customer support.
40
ERROR: Unable to read key
Description
GWWS cannot read TUXCONFIG file encryption key when SSL is set for GWWS.
Action
Contact BEA 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 BEA Customer support.
42
ERROR: Unable to decrypt password
Description
GWWS cannot decrypt password when SSL is set for GWWS.
Action
Contact BEA Customer support.
43
ERROR: Failed to advertise GWWS internal service
Description
GWWS cannot advertise the internal administration service.
Action
Contact BEA Customer support.
44
ERROR: Cannot find definition for instance instance id in configuration file
Description
GWWS cannot find the supplied instance ID in XML configuration file.
Action
Make sure the instance ID is consistent in UBBCONFIG file and XML configuration file.
45
ERROR: GWWS statistics data mutex initialization failed
Description
GWWS cannot initialize statistics data mutex.
Action
Try to shutdown GWWS then reboot it. If the problem persists,contact BEA Customer Support.
46
ERROR: GWWS statistics data mutex lock failed
Description
GWWS cannot lock statistics data mutex.
Action
Try to shutdown GWWS then reboot it. If the problem persists,contact BEA 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 in one Tuxedo domain.
Action
Make sure instance ID of GWWS is unique in one Tuxedo domain.
60
ERROR: Cannot generate a new UUID for wsa:MessageID
Description
GWWS failed to generate message ID with UUID format.
Action
Contact BEA Customer support.
61
ERROR: GWWS sequence table mutex initialization failed
Description
GWWS failed to initialize reliable message related sequence table mutex.
Action
Contact BEA Customer support.
62
ERROR: GWWS sequence table mutex destroy failed
Description
GWWS failed to destroy reliable message related sequence table mutex.
Action
Contact BEA Customer support.
63
ERROR: GWWS sequence mutex lock failed
Description
GWWS failed to lock sequence mutex
Action
Contact BEA Customer support.
64
ERROR: GWWS sequence mutex initialization failed
Description
GWWS cannot initialize reliable message related sequence mutex.
Action
Contact BEA Customer support.
65
ERROR: GWWS sequence mutex destroy failed
Description
GWWS failed to destroy sequence mutex.
Action
Contact BEA Customer support.
66
ERROR: Cannot initialize sequence
Description
GWWS failed to initialize sequence.
Action
Contact BEA Customer support.
67
ERROR: Cannot insert a new sequence to the table
Description
GWWS failed to insert a new reliable message sequence to the sequence table.
Action
Contact BEA 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 BEA 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 BEA Customer support.
70
ERROR: Unknown SOAP request
Description
GWWS failed to parse the SOAP request from client.
Action
First check the client SOAP message and make sure that the message format matches the GWWS WSDL file requirement. A frequent met reason for this problem is client uses an old WSDL then GWWS.
71
ERROR: WS-Addressing validation failed
Description
The WS-Addressing message from client is not valid. It may contain contents not conforming to WS-Addressing specification.
Action
First check SOAP message with WS-Addressing specification. Contact BEA Customer support if this problem continues happening.
72
ERROR: WS-ReliableMessaging validation failed
Description
The WS-ReliableMessaging message from client is not valid. It may contain contents not conforming to WS-Reliable Messaging specification.
Action
First check SOAP message with WS-ReliableMessaging specification. Contact BEA Customer support if this problem continues happening.
73
ERROR: Cannot create WSRM housekeeping thread
Description
GWWS failed to start reliable messaging housekeeping thread.
Action
Contact BEA Customer support.
74
INFO: GWWS instance ID started with reliable messaging feature
Description
GWWS started with reliable messaging support if a valid WSRM policy file is set in configuration file.
Action
 |
 |
 |