WSCFG Messages 200-299
|
|
209
Schema validate initialization error
Description
Xerces initialization failed before validating the XML document.
Action
This error was mostly due to the system memory allocation error. Please make sure sufficient memory can be used by the current process.
211
XML Exception(err_string)
Description
An attempt to parse the XML document failed, see err_string for further information. Xerces library throws an XML Exception.
Action
See Xerces reference for XML Exception.
212
DOM Exception(errcode:err_string)
Description
An attempt to parse the XML document failed, see errcode and err_string for further information. Xerces library throws a DOM Exception.
Action
See Xerces reference for DOM Exception.
219
Parameter schema ("param_schema_val") not recognized
Description
GWWS cannot find the XML Schema definition file according to the XML Schema namespace URI of the paramschema keyword value when loading a Tuxedo service definition from the Service Metadata Repository.
Action
Make sure the paramschema keyword value is correct and the directory pathname contains the corresponding XML Schema file is set in the XSDDIR environment variable.
See Also
BEA SALT Administration Guide
220
Buffer schema ("param_schema_val") not recognized
Description
GWWS cannot find the XML Schema definition file according to the XML Schema namespace URI of the *bufschema keyword value when loading a Tuxedo service definition from the Service Metadata Repository.
Action
Make sure the *bufschema keyword value is correct and the directory pathname contains the corresponding XML Schema file is set in the XSDDIR environment variable.
See Also
BEA SALT Administration Guide
221
ERROR: Memory Allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while GWWS is creating in memory configuration context at boot time.
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.
222
ERROR: Same advertised Tuxedo service [svc_name] is referenced more than once
Description
GWWS detects two outbound Tuxedo services are associated with the same Tuxedo service name.
Action
Advertising two outbound Tuxedo services with the same service name may result unexpected behavior. Customers need to manually update the tuxservice keyword value of the services to make sure multiple Tuxedo Metadata services are associated with different advertised Tuxedo service name.
223
ERROR: Could not open *OPERATION section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *OPERATION section.
Action
Try to recreate a new SALTCONFIG. If the SALTCONFIG is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by entering:
echo " " >$SALTCONFIG
If the error persists, check for disk-type error conditions that might cause problems writing to files.
Finally, contact BEA Technical Support.
See Also
wsloadcf(1)
224
ERROR: Could not open *WSDF section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *WSDF section.
Action
See message 223 above.
See Also
wsloadcf(1)
225
ERROR: Could not access No.seq_num *WSDF entry in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to access the SALTCONFIG file, GWWS got an error trying to access the specified No.seq_num *WSDF entry.
Action
See message 223 above.
See Also
wsloadcf(1)
226
ERROR: Could not allocate memory for No.seq_num *WSDF entry
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while GWWS is creating in memory configuration context for No.seq_num WSDF object.
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.
227
ERROR: Could not open *BINDING section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *BINDING section.
Action
See message 223 above.
See Also
wsloadcf(1)
228
ERROR: Could not access No.seq_num *BINDING entry in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to access the SALTCONFIG file, GWWS got an error trying to access the specified No.seq_num *BINDING entry.
Action
See message 223 above.
See Also
wsloadcf(1)
229
ERROR: Could not allocate memory for No.seq_num *BINDING entry
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while GWWS is creating in memory configuration context for No.seq_num BINDING object.
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.
230
ERROR: Could not open *ENDPOINT section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *ENDPOINT section.
Action
See message 223 above.
See Also
wsloadcf(1)
231
ERROR: Could not access No.seq_num *ENDPOINT entry in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to access the SALTCONFIG file, GWWS got an error trying to access the specified No.seq_num *ENDPOINT entry.
Action
See message 223 above.
See Also
wsloadcf(1)
234
ERROR: Could not open *GATEWAY section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *GATEWAY section.
Action
See message 223 above.
See Also
wsloadcf(1)
235
ERROR: Could not find Gateway gateway_id settings
Description
GWWS cannot find the Gateway gateway_id information from the SALTCONFIG file.
Action
Make sure the gateway instance id is correctly defined in both SALT deployment file and in the UBBCONFIG file.
236
ERROR: Could not allocate memory for GWWS information
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while GWWS is creating in memory configuration context for gateway information.
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.
237
ERROR: Could not open *RESOURCES section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *RESOURCES section.
Action
See message 223 above.
See Also
wsloadcf(1)
238
ERROR: Could not access *RESOURCES entry in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to access the SALTCONFIG file, GWWS got an error trying to access the *RESOURCES entry.
Action
See message 223 above.
See Also
wsloadcf(1)
240
ERROR: Could not open *POLICY section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *POLICY section.
Action
See message 223 above.
See Also
wsloadcf(1)
241
ERROR: Could not access No.seq_num *POLICY entry in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to access the SALTCONFIG file, GWWS got an error trying to access the specified No.seq_num *POLICY entry.
Action
See message 223 above.
See Also
wsloadcf(1)
242
ERROR: Could not allocate memory for No.seq_num *POLICY entry
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while GWWS is creating in memory configuration context for No.seq_num POLICY object.
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.
243
ERROR: Could not allocate memory for policy reference
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while GWWS is creating in memory configuration context for policy reference index.
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.
244
ERROR: Could not open *PLUGIN section in SALTCONFIG
Description
The SALTCONFIG file is a binary file in the BEA TUXEDO VTOC format. Each object of the SALTDEPLOY file and WSDF files (GWWS, WSBinding, Endpoint, etc.) is stored as a separate table in the SALTCONFIG file.
While trying to open the SALTCONFIG file, GWWS got an error trying to open the *PLUGIN section.
Action
See message 223 above.
See Also
wsloadcf(1)
245
ERROR: Could not allocate memory for *PLUGIN entry
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while GWWS is creating in memory configuration context for PLUGIN object.
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.
 |
 |
 |