WSCFG Messages 0-99
|
|
1
ERROR: Configuration initialize failed, memory allocation error
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while preparing to parse SALT configuration file.
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 and/or swap space on the machine.
2
ERROR: Configuration initialize failed, internal error
Description
An internal error was detected while preparing to parse the SALT configuration file.
Action
Contact BEA Customer Support.
14
ERROR: WSDL file generation failed. Memory allocation error.
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while the SALT WSDL file is being generated.
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 and/or swap space on the machine.
15
ERROR: WSDL file generation failed. Internal error.
Description
An internal error was detected while the SALT WSDL file is being generated.
Action
Contact BEA Customer Support.
16
ERROR: Output WSDL file (filename) error
Description
A file IO error was detected while tmwsdlgen is trying to output the SALT WSDL file.
Action
Make sure the correct WSDL file path is specified as the tmwsdlgen command line option. Make sure you have write permission to the output WSDL file path.
See Also
tmwsdlgen(1)
17
ERROR: WSDL generation failed. Web service definition does not exist.
Description
The specified Web Service Definition id does not exist when trying to download WSDL from an active GWWS server.
Action
Make sure the correct WSDF id is given using the following download URL format:
http(s)://
See Also
BEA SALT Administration Guide
18
ERROR: GWWS Configuration not initialized yet
Description
While GWWS attempts to load the BEA SALT configuration file, the GWWS initialization operation was not completed successfully.
Action
Make sure your GWWS is booted successfully. Try to shutdown and reboot GWWS to avoid such problem.
24
Cannot save Inbound WSDF file.
Description
While attempts to load the BEA SALT 1.1 configuration file, wsloadcf cannot save the inbound WSDF file converted from the SALT 1.1 configuration file.
Action
Try to delete some existing generated inbound WSDF files and SALTDEP files in the target directory.
See Also
wsloadcf(1)
25
Temp WSDF file conversion error.
Description
While attempts to convert the BEA SALT 1.1 configuration file, tmwsdlgen failed to save the temporary generated WSDF file.
Action
Check if the TEMP directory on your local machine has enough spaces. Free some space and retry. If the error persists, contact BEA Customer Support.
See Also
tmwsdlgen(1)
26
Generating WSDF file filename error.
Description
While attempts to convert the BEA SALT 1.1 configuration file, wsloadcf failed to save the generated inbound WSDF file.
Action
Check if the TEMP directory on your local machine has enough spaces. Free some space and retry. If the error persists, contact BEA Customer Support.
See Also
wsloadcf(1)
27
WSDF file filename generated.
Description
wsloadcf successfully converted the BEA SALT 1.1 configuration file into a SALT WSDF file, filename.
Action
No action required.
See Also
wsloadcf(1)
29
Generating SALTDEPLOY file filename error.
Description
While attempts to convert the BEA SALT 1.1 configuration file, wsloadcf failed to save the generated SALTDEPLOY file.
Action
Check if the TEMP directory on your local machine has enough spaces. Free some space and retry. If the error persists, contact BEA Customer Support.
See Also
wsloadcf(1)
30
SALTDEPLOY file filename generated.
Description
wsloadcf successfully converted the BEA SALT 1.1 configuration file into a SALTDEPLOY file, filename.
Action
No action required.
32
ERROR: GWWS <GWWS_instance_id> configuration context creation failed.
Description
GWWS encountered an error while attempting to load SALTCONFIG VTOC file and generate in memory configuration context.
Action
First, make sure the correct SALTCONFIG file is compiled using wsloadcf and the SALTCONFIG environment variable is set properly.
Then, make sure 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.
If the error persists, contact BEA Customer Support.
33
INFO: Get configuration for GWWS <GWWS_instance_id> succeeded
Description
GWWS loaded the SALTCONFIG file and generated in memory context successfully.
Action
No action required.
34
ERROR: Create configuration context failed.
Description
tmwsdlgen encountered an error while attempting to load WSDF file and generate in memory configuration context.
Action
Make sure 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. If the error persists, contact BEA Customer Support.
36
ERROR: SALTCONFIG environment variable not set.
Description
The SALTCONFIG environment variable is not set.
Action
Set and export the SALTCONFIG environment variable.
37
ERROR: SALTCONFIG environment variable must be an absolute pathname.
Description
The application specified a value for the SALTCONFIG environment variable that is a simple or relative pathname, not beginning with slash (/).
Action
Change the SALTCONFIG environment variable to be an absolute pathname and re-execute the program.
38
ERROR: SALTCONFIG file filename does not exist.
Description
The SALTCONFIG file, filename, does not exist.
Action
Check the SALTCONFIG environment variable. Then, check to see if the SALTCONFIG file has been generated. If not, use wsloadcf(1) to create the SALTCONFIG file.
See Also
wsloadcf(1)
39
ERROR: Cannot stat SALTCONFIG file filename, errno = errno_val.
Description
Cannot get the file status on the SALTCONFIG file, filename.
Action
Check the UNIX errno for reasons and take appropriate actions accordingly.
See Also
stats(2) in UNIX system reference manuals
40
ERROR: SALTOFFSET environment variable must be >= 0.
Description
The SALTOFFSET environment variable is less than 0.
Action
Specify a value for the SALTOFFSET environment variable that is greater than or equal to 0.
41
ERROR: Invalid table type.
Description
The calling process failed to open a configuration table in the SALTCONFIG file. An invalid table type was passed to the system routine responsible for opening configuration tables.
Action
Contact your BEA Technical Support.
42
ERROR: Cannot open section section_name of SALTCONFIG file: error code errno_val.
Description
The section_name of the SALTCONFIG file cannot be opened. The SALTCONFIG file might be corrupted.
Action
You can shut down the application and re-load the SALTCONFIG file using wsloadcf. If the error still occurs, contact BEA Technical Support.
See Also
wsloadcf(1)
43
ERROR: Cannot malloc space for SALTCONFIG file.
Description
Memory allocation failed for adding new sections in the SALTCONFIG file.
Action
Make sure 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.
44
ERROR: Close failed on vtoc table.
Description
The SALTCONFIG file in the VTOC table cannot be closed.
Action
Check the permissions and the existence of the SALTCONFIG file, or contact BEA Technical Support.
45
ERROR: gp_tblread on entry failed.
Description
Read an entry from the disk table failed. Possible causes: 1) the logical table file descriptor was corrupted, 2) the read page offset was set incorrectly by the system, or 3) the table itself got corrupted which caused read to fail.
Action
Check your disk tables such as VTOC for possible corruptions and/or damages. If this error still occurs, contact your BEA Technical Support.
46
ERROR: Write on file not opened: section_name.
Description
An error was detected when attempting to write to the SALTCONFIG file. The file associated with the named section section_name of the SALTCONFIG file was not opened prior to attempting the write.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Technical Support.
47
ERROR: Write failed on file: section_name.
Description
An error was detected when attempting to write to the SALTCONFIG file.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Technical Support.
51
Memory Alloc Error for new entry (section_name).
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while trying to create a new entry for section section_name of the SALTCONFIG file.
Action
Make sure 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.
53
Policy file (filename) cannot be applied to (msg_direction) message(s)
Description
The policy file, filename, contains WS-Policy assertions that are not supported to be applied to the msg_direction message(s) of the service.
Action
Make sure the WS-Policy assertions defined in the WS-Policy file are supported by BEA SALT and can be applied to the msg_direction message(s) of a service.
See Also
BEA SALT Administration Guide
54
Policy Reference number exceeds max_policy_ref_val. Ignored
Description
This warning indicates that the WS-Policy files referenced by a Web service object ( either a <Servicegroup>, or a <Service> ) exceeds the maximum allowed number max_policy_ref_val while parsing a WSDF file.
Action
Try to merge some WS-Policy assertions in one WS-Policy file.
55
Policy file (filename) cannot be applied to <Service> Level
Description
The policy file, filename, contains WS-Policy assertions that are not supported to be applied to the service.
Action
Make sure the WS-Policy assertions defined in the WS-Policy file are supported by BEA SALT and can be applied to the service level.
See Also
BEA SALT Administration Guide
56
Policy file (filename) cannot be applied to <Servicegroup> Level
Description
The policy file, filename, contains WS-Policy assertions that are not supported to be applied to the Servicegroup.
Action
Make sure the WS-Policy assertions defined in the WS-Policy file are supported by BEA SALT and can be applied to the Servicegroup level.
See Also
BEA SALT Administration Guide
57
Duplicate endpoint (endpoint_id)
Description
wsloadcf detects multiple endpoints defined with the same id endpoint_id while parsing a WSDF file.
Action
Correct the WSDF file to avoid duplicate endpoint id values.
See Also
BEA SALT Web Service Definition File Reference
58
Unsupported endpoint address (url_val)
Description
wsloadcf detects unsupported endpoint address URL value while parsing a WSDF file. BEA SALT only supports HTTP and HTTPS transport protocol, hence the endpoint address URL value must start with "http://" or "https://".
Action
Correct the WSDF file with valid endpoint address URL value.
See Also
BEA SALT Web Service Definition File Reference
59
Unknown WSDF (wsdf_name)
Description
wsloadcf detects undefined WSDF wsdf_name is referenced by a GWWS gateway instance while parsing the SALT deployment file.
Action
Make sure all necessary WSDF files are imported in the SALT deployment file. Make sure the wsdf_name value specified in the SALT deployment file is correct.
See Also
BEA SALT Deployment File Reference, BEA SALT Web Service Definition File Reference
60
Unknown binding (binding_id)
Description
wsloadcf detects undefined binding binding_id is referenced by a GWWS gateway instance while parsing the SALT deployment file.
Action
Make sure all necessary WSDF files are imported in the SALT deployment file. Make sure the binding_id value specified in the SALT deployment file is correct.
See Also
BEA SALT Deployment File Reference, BEA SALT Web Service Definition File Reference
61
Unknown endpoint (endpoint_id)
Description
wsloadcf detects undefined endpoint endpoint_id is referenced by a GWWS gateway instance while parsing the SALT deployment file.
Action
Make sure all necessary WSDF files are imported in the SALT deployment file. Make sure the endpoint_id value specified in the SALT deployment file is correct.
See Also
BEA SALT Deployment File Reference, BEA SALT Web Service Definition File Reference
67
Duplicate address between endpoint (endpoint_id1) and (endpoint_id2)
Description
wsloadcf detects the same address value is used by both endpoint endpoint_id1 and endpoint_id2 while parsing a SALT WSDF file.
Action
Correct the WSDF file to avoid duplicate endpoint address value.
68
Imported WSDF (wsdf_name) cannot be used for both inbound/outbound direction
Description
BEA SALT enforces each WSDF file must be used for only one direction, either inbound or outbound. wsloadcf detects the WSDF wsdf_name is used for both direction while parsing the SALT deployment file.
Action
Correct the SALT deployment file. Make sure a WSDF is only used for one direction, either inbound or outbound.
See Also
BEA SALT Deployment File Reference
76
Document/Encoded style is not supported
Description
wsloadcf detects the unsupported Document/Encoded style is set in the WSDF file.
Action
Modify the SOAP message encoding style to Document/Literal or RPC/Encoded in the WSDF file.
77
RPC/Literal style is not supported
Description
wsloadcf detects the unsupported RPC/Literal style is set in the WSDF file.
Action
Modify the SOAP message encoding style to Document/Literal or RPC/Encoded in the WSDF file.
79
Unsupported Policy Assertion <assertion>
Description
wsloadcf detects unsupported WS-Policy assertion assertion defined in the WS-Policy file.
Action
Remove the unsupported policy assertion from the WS-Policy file.
80
Policy Assertion <assertion> is not a top level assertion
Description
wsloadcf detects the Policy Assertion assertion defined as a top level assertion in the WS-Policy file. But BEA SALT does not support this assertion to be defined at top level.
Action
Modify your WS-Policy file according to BEA SALT WS-Policy rules.
See Also
BEA SALT Administration Guide
83
Nesting Policy Assertion <sub_assertion> is not supported for <assertion>
Description
BEA SALT supports a limited scope of nesting policy assertions defined in WS-SecurityPolicy 1.2 spec. wsloadcf detects unsupported nesting relationship while parsing a WS-SecurityPolicy 1.2 file.
Action
Modify your WS-Policy file according to BEA SALT WS-Policy rules.
See Also
BEA SALT Administration Guide
90
System memory allocation error
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while the SALT configuration file is being parsed.
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 and/or swap space on the machine.
91
[Line(line_num) Char(char_num)]:err_string
Description
An XML Schema validation warning is detected in the XML file at line line_num, character position char_num. The warn detail is specified in err_string.
Action
Refer to the corresponding XML Schema file to modify your XML file.
92
[Line(line_num) Char(char_num)]:err_string
Description
An XML Schema validation error is detected in the XML file at line line_num, character position char_num. The error detail is specified in err_string.
Action
Refer to the corresponding XML Schema file to modify your XML file.
93
[Line(line_num) Char(char_num)]:err_string
Description
An XML Schema validation fatal error is detected in the XML file at line line_num, character position char_num. The fatal error detail is specified in err_string.
Action
Refer to the corresponding XML Schema file to modify your XML file.
95
File "filename" is not a valid SALT WSDF file
Description
The specified file, filename, is not a valid BEA SALT WSDF file.
Action
Check that the specified file is a valid SALT WSDF file. Correct the file and re-execute the command.
See Also
BEA SALT Web Service Definition File Reference
96
File "filename" is not a valid SALT 1.1 configuration file
Description
The specified file, filename, is not a valid BEA SALT 1.1 configuration file.
Action
Check that the specified file is a valid SALT 1.1 configuration file.
97
File "filename" is not a valid SALT deployment file
Description
The specified file, filename, is not a valid BEA SALT deployment file.
Action
Check that the specified file is a valid SALT deployment file. Correct the file and re-execute the command.
 |
 |
 |