System Messages: GWWS Catalog 1400-1499
|
|
|
|
1400 |
ERROR: No more state in wstxTable | |
|
|
Description |
GWWS WSTX internal table full. |
|
Action |
Contact your Oracle support. | |
|
1401 |
ERROR: on return from TFSM for event WsRegistered | |
|
|
Description |
GWWS TFSM returned error for event WsRegistered. |
|
Action |
Contact your Oracle support. | |
|
1402 |
ERROR: Memory allocation failed, (m,l) | |
|
|
Description |
GWWS memory allocation failed in module m at line l |
|
Action |
Add more memory to the system. | |
|
1403 |
ERROR: Memory allocation failed, (m,l) | |
|
|
Description |
GWWS memory allocation failed in module m at line l |
|
Action |
Add more memory to the system. | |
|
1404 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1405 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1406 |
WARN: No addressing and enlistment id information, unable to send | |
|
|
Description |
Unable to send WSTX message because it failed to find addressing and enlistment id information for the request. |
|
Action |
Contact your Oracle support. | |
|
1407 |
ERROR: Memory allocation failed, (m,l) | |
|
|
Description |
GWWS memory allocation failed in module m at line l |
|
Action |
Add more memory to the system. | |
|
1408 |
ERROR: Memory allocation failed, (m,l) | |
|
|
Description |
GWWS memory allocation failed in module m at line l |
|
Action |
Add more memory to the system. | |
|
1409 |
ERROR: Memory allocation failed, (m,l) | |
|
|
Description |
GWWS memory allocation failed in module m at line l |
|
Action |
Add more memory to the system. | |
|
1410 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1411 |
WARN: Failed to establish registration service connection | |
|
|
Description |
GWWS failed to establish registration service connection |
|
Action |
Correct the problem in the deployment configuration file. | |
|
1412 |
WARN: Transaction manager system lock initialization failed. | |
|
|
Description |
Transaction manager failed to initialize global transaction access lock. |
|
Action |
Contact your Oracle support. | |
|
1413 |
INFO: GWWS_TLOG_OFFSET is set to n blocks | |
|
|
Description |
GWWS transaction log offset is set to n number of blocks. |
|
Action |
Informational, no action required. | |
|
1414 |
INFO: GWWS_TLOG_OFFSET is set to n blocks | |
|
|
Description |
GWWS transaction log offset is set to n number of blocks. |
|
Action |
Informational, no action required. | |
|
1415 |
ERROR: allocating SCO object | |
|
|
Description |
Memeory allocation failure encountered while allocating SCO object. |
|
Action |
Add more memory to the system. | |
|
1416 |
ERROR: setting up SCO object | |
|
|
Description |
Encountered error while setting up SCO object. |
|
Action |
Contact your Oracle support. | |
|
1417 |
ERROR: allocating SCO object | |
|
|
Description |
Memeory allocation failure encountered while allocating SCO object. |
|
Action |
Add more memory to the system. | |
|
1418 |
ERROR: setting up SCO object | |
|
|
Description |
Encountered error while setting up SCO object. |
|
Action |
Contact your Oracle support. | |
|
1419 |
WARN: Received ws-at:Aborted without transaction id, ignoring it | |
|
|
Description |
The received ws-at:Aborted message is ignored because there is no transaction id. |
|
Action |
Contact your remote application provider support. | |
|
1420 |
Transaction error: Probelm setting up WS-TX context | |
|
|
Description |
Failed setting up internal WS-TX context. |
|
Action |
Contact your Oracle support. | |
|
1421 |
ERROR: Unable to create new listening connection for id | |
|
|
Description |
Unable to create listening connection for instance id. |
|
Action |
Contact your Oracle support. | |
|
1422 |
Created SSL listening connection for id | |
|
|
Description |
Created a SSL listening connection for instance id id |
|
Action |
Informational, no action required. | |
|
1423 |
Created listening connection for id | |
|
|
Description |
Created a listening connection for instance id |
|
Action |
Informational, no action required. | |
|
1324 |
ERROR: could not initialize wsat endpoint | |
|
|
Description |
Failed to initialize a WS-AT endpoint. |
|
Action |
Correct the error in the deployment configuration file. | |
|
1425 |
ERROR: Internal memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1455 |
ERROR: could not initialize REST http endpoint | |
|
|
Description |
Unable to allocate memory to initialize REST http endpoint. |
|
Action |
Add more memory to the system. | |
|
1456 |
ERROR: Unable to create new listening connection for ep | |
|
|
Description |
Failed to create listening connection for endpoint ep defined in the configuration.. |
|
Action |
Check the address/port is correct or is being used by another program. If so, correct the address/port accordingly. | |
|
1457 |
Create REST listening connection for ep | |
|
|
Description |
The REST listening connection for endpoint ep is created. |
|
Action |
Informational message, no action is required. | |
|
1458 |
ERROR: could not initialize REST https endpoint | |
|
|
Description |
Unable to allocate memory to initialize REST https endpoint. |
|
Action |
Add more memory to the system. | |
|
1459 |
ERROR: Unable to create new listening connection for ep | |
|
|
Description |
Failed to create listening connection for endpoint ep defined in the configuration.. |
|
Action |
Check the address/port is correct or is being used by another program. If so, correct the address/port accordingly. | |
|
1460 |
Create REST listening connection for ep | |
|
|
Description |
The REST listening connection for endpoint ep is created. |
|
Action |
Informational message, no action is required. | |
|
1461 |
ERROR: Error in converting payload between encoding enc1 and enc2 | |
|
|
Description |
Failed to convert from encoding enc1 to encoding enc2. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of failure and correct it. If problem persist contact Oracle Customer Support. | |
|
1462 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1463 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1464 |
ERROR: Internal memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1465 |
ERROR: Converting payload between encoding enc1 and enc2 | |
|
|
Description |
Failed to convert payload from encoding enc1 to encoding enc2. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of failure and correct it accordingly. If problem persist contat Oracle Customer Support. | |
|
1466 |
ERROR: Converting payload between encoding enc1 and enc2 | |
|
|
Description |
Failed to convert payload from encoding enc1 to encoding enc2. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of failure and correct it accordingly. If problem persist contat Oracle Customer Support. | |
|
1467 |
ERROR: Failed to parse buffer | |
|
|
Description |
Failed to parse buffer. |
|
Action |
Check input REST message to determine which element does not follow the rule. | |
|
1468 |
ERROR: Input is empty | |
|
|
Description |
Empty REST message in the payload. |
|
Action |
Check the application a correct the issue. | |
|
1469 |
ERROR: Failed to parse buffer | |
|
|
Description |
Failed to parse buffer. |
|
Action |
Check input REST message to determine which element does not follow the rule. | |
|
1470 |
ERROR: Failed to get the encoding style for TUXEDO MBSTRING buffer, detail | |
|
|
Description |
Unable to get the encoding style information for TUXEDO buffer; the error information is in detail. |
|
Action |
Check whether or not the MBSTRING returned by TUXEDO includes the encoding style. | |
|
1471 |
ERROR: Converting payload between encoding enc1 and enc2 | |
|
|
Description |
Failed to convert payload from encoding enc1 to encoding enc2. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of failure and correct it. If problem persist contact Oracle Customer Support. | |
|
1472 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1473 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1474 |
ERROR: Input is empty | |
|
|
Description |
Input MBSTRING buffer is empty. |
|
Action |
Check the application error. | |
|
1475 |
ERROR: Converting payload between encoding enc1 and enc2 | |
|
|
Description |
Failed to convert payload from encoding enc1 to encoding enc2. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of failure and correct it. If problem persist contact Oracle Customer Support. | |
|
1476 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1477 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1478 |
ERROR: Failed to set the encoding style for TUXEDO buffer, detail | |
|
|
Description |
Failed to set the encoding style for TUXEDO MBSTRING buffer, the detailed error information is in detail. |
|
Action |
Correct the problem indicated in the message especially check whether the mssage uses "UTF-8" encoding style. | |
|
1479 |
ERROR: Failed to set the encoding style for TUXEDO buffer, detail | |
|
|
Description |
Failed to set the encoding style for TUXEDO MBSTRING buffer, the detailed error information is in detail. |
|
Action |
Correct the problem indicated in the message especially check whether the mssage uses "UTF-8" encoding style. | |
|
1480 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1481 |
ERROR: DataMapping Error: Input data is empty | |
|
|
Description |
The convertion of the MBSTRING field yield empty data. |
|
Action |
Check whether the application data is correctly presented. | |
|
1482 |
ERROR: failed to convert between encoding enc1 and enc2 | |
|
|
Description |
Failed to convert MBSTRING field from encoding enc1 to enc2. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of failure and correct it. | |
|
1483 |
ERROR: DataMapping Error: Input data is empty | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of failure and correct it. | |
|
1484 |
ERROR: Cannot unpack MBSTRING data | |
|
|
Description |
Failed to unpack MBSTRING data. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of the failure and correct it. | |
|
1485 |
ERROR: Adding MBSTRING field to Tuxedo buffer: str | |
|
|
Description |
Failed to add MBSTRING field to a Tuxedo FML/FML32 buffer. kk[ACTION] Check prior error message in the TUXEDO USERLOG to determine the true cause of the failure and correct. |
|
1486 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1487 |
ERROR: Fail to convert from encoding enc1 to enc2 | |
|
|
Description |
Failed to convert MBSTRING field from encoding enc1 to encoding enc2. |
|
Action |
Check prior error message in the TUXEDO USERLOG to determine the true cause of the failure and correct. | |
|
1488 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1489 |
ERROR: Memory allocation failed | |
|
|
Description |
Failed to allocate memory. |
|
Action |
Add more memory to the system. | |
|
1490 |
ERROR: could not find method for service: svc | |
|
|
Description |
Failed to find REST service method svc. |
|
Action |
If this it not an error then check the SALT configuration for missing or mis-spelled REST service and correct it. | |
|
1491 |
ERROR: Request-URI Too Long, maximum is max | |
|
|
Description |
The request URI is longer than maximum allowed size max. |
|
Action |
Correct the problem. | |
|
1492 |
ERROR: Converting Tuxedo buffer to XML | |
|
|
Description |
Failed to Tuxedo buffer to XML document. |
|
Action |
Checking the prior error message in Tuxedo USERLOG for true cause of the failure and correct it. If the problem can not be resolved contact Oracle Customer Support. | |
|
1493 |
ERROR: Invalid content for field: fld while converting to XML: rc | |
|
|
Description |
Invalid content for field fld while converting FML/FML32 buffer type to XML document; the error return code is rc. |
|
Action |
Check the FML/FML32 buffer for data that can not be mapped properly. | |
|
1494 |
ERROR: Data mapping error for field fldname: rc | |
|
|
Description |
Failed to map XML data to FML/FML32 field fldname; the error return code is rc. |
|
Action |
Check the XML document for data field that can not be properly mapped to field in FML/FML32 buffer. | |
|
1495 |
Invalid type for field fldname when processing boolean value | |
|
|
Description |
Invalid JSON boolean data type to convert to FML/FML32 field fldname. |
|
Action |
Correct the application to use valid JSON data type for field fldname. | |
|
1496 |
Invalid type for field fldname when processing boolean value | |
|
|
Description |
Invalid JSON boolean data type to convert to FML/FML32 field fldname. |
|
Action |
Correct the application to use valid JSON data type for field fldname. | |
|
1497 |
Failed to convert query string from encoding enc1 to enc2 | |
|
|
Description |
Failed to converty a REST query string from encoding enc1 to enc2. |
|
Action |
Check the previous error message in Tuxedo USERLOG for cause of the failure and correct the problem accordingly. | |
|
1498 |
ERROR: unknown data mapping. | |
|
|
Description |
Lack of mapping information to transform input REST data to structured Tuxedo buffer type. |
|
Action |
Make sure the structured Tuxedo buffer type configuration information is properly setup. These information includes VIEW directory, VIEW definition files, FML field table directory and FML field definition files. | |
|
1499 |
ERROR: unknown data mapping. | |
|
|
Description |
Lack of mapping information to transform input REST data to structured Tuxedo buffer type. |
|
Action |
Make sure the structured Tuxedo buffer type configuration information is properly setup. These information includes VIEW directory, VIEW definition files, FML field table directory and FML field definition files. | |
 |
 |
 |