System Messages: GWWS Catalog 1300-1399
|
|
|
|
1301 |
ERROR: Failed to initialize branch for transaction txid | |
|
|
Description |
Unable to initialize a branch object for transaction txid. |
|
Action |
Contact your Oracle support. | |
|
1302 |
ERROR: Transaction manager can not process transaction branch | |
|
|
Description |
The Transaction manager can not processing an event for a branch that does not belong to any transaction. |
|
Action |
Contact your Oracle support. | |
|
1303 |
ERROR: Transaction manager received none tranactional event(evt_id). | |
|
|
Description |
The Transaction manager received an event but no transaction information associates with it. |
|
Action |
Contact your Oracle support. | |
|
1304 |
ERROR: Failed to allocate transaction for transaction id txid | |
|
|
Description |
Transaction manager failed to allocate a transaction object for tranaction txid |
|
Action |
Check whether your MaxTran is enough to handle all the concurrent transactional requests. | |
|
1305 |
ERROR: Failed to initialzie transaction for transaction id txid | |
|
|
Description |
Transaction manager failed to initialize a transaction object for transaction id txid. |
|
Action |
Contact your Oracle support. | |
|
1306 |
ERROR: Failed to allocate branch for transaction id txid | |
|
|
Description |
Transaction manager failed to allocate a branch object for transaction with id txid. |
|
Action |
Contact your Oracle support. | |
|
1307 |
ERROR: Failed to link branch for transaction txid | |
|
|
Description |
Transaction manager was unable to find the transaction object for branch object with transaction id txid. |
|
Action |
Contact your Oracle support. | |
|
1308 |
ERROR: Failed to find transaction (txid) for event (evt_id) | |
|
|
Description |
Transaction manager failed to find transaction object for event evt_id with transaction id txid. |
|
Action |
Contact your Oracle support. | |
|
1309 |
ERROR: Failed to find transaction (txid) for event (evt_id) | |
|
|
Description |
Transaction manager failed to find transaction object for event evt_id with transaction id txid. |
|
Action |
Contact your Oracle support. | |
|
1310 |
ERROR: Transaction manager received UNKNOWN event. | |
|
|
Description |
Transaction manager received an |
|
Action |
Contact your Oracle support. | |
|
1311 |
ERROR: Transaction manager mutex initialization failed. | |
|
|
Description |
Transaction manager failed to initialize mutex. |
|
Action |
Contact your Oracle support. | |
|
1312 |
ERROR: Transaction manager lookup initialization failed. | |
|
|
Description |
Transaction manager failed to initialize necessary data for quick transaction object lookup operation. |
|
Action |
Contact your Oracle support. | |
|
1313 |
ERROR: GWWS transaction table super block malloc failure. | |
|
|
Description |
Transaction manager encountered memory allocation error while trying to allocate a super block. |
|
Action |
Add more memory to the syatem. | |
|
1314 |
ERROR: GWWS transaction table malloc failure. | |
|
|
Description |
Transaction manager encountered memory allocation error while trying to allocate transaction table. |
|
Action |
Add more memory to the syatem. | |
|
1315 |
ERROR: GWWS transaction table super block malloc failure. | |
|
|
Description |
Transaction manager failed to malloc more super block during transaction table expansion. |
|
Action |
Add more memory to the system. | |
|
1316 |
ERROR: TX manager transaction table malloc failed. | |
|
|
Description |
Transaction manager encountered memory allocation error while trying to expand transaction table. |
|
Action |
Add more memory to the syatem. | |
|
1317 |
ERROR: Failed to get the TX manager master lock. | |
|
|
Description |
The operation failed because it failed to acquire transaction manager's master lock. |
|
Action |
Contact your Oracle support. | |
|
1318 |
ERROR: Failed to get the TX manager master lock. | |
|
|
Description |
The operation failed because it failed to acquire transaction manager's master lock. |
|
Action |
Contact your Oracle support. | |
|
1319 |
ERROR: Failed to lock transaction access lock. | |
|
|
Description |
The operation failed because it failed to acquire transaction manager's access lock. |
|
Action |
Contact your Oracle support. | |
|
1320 |
ERROR: Transaction table branch super block malloc failure. | |
|
|
Description |
Transaction manager encountered memory allocation error while trying to allocate a super block for branch objects. |
|
Action |
Add more memory to the syatem. | |
|
1321 |
ERROR: Transaction branch table malloc failure. | |
|
|
Description |
Transaction manager encountered memory allocation error while trying to expand branch object table. |
|
Action |
Add more memory to the syatem. | |
|
1322 |
ERROR: Transaction branch table super block malloc failure. | |
|
|
Description |
Transaction manager encountered memory allocation error while trying to expand super block for branch objects. |
|
Action |
Contact your Oracle support. | |
|
1323 |
ERROR: TX manager trnasaction table malloc failed. | |
|
|
Description |
Transaction manager encountered memory allocation error while trying to allocate transacton table. |
|
Action |
Add more memory to the syatem. | |
|
1324 |
ERROR: Failed to get TX manager master lock. | |
|
|
Description |
The operation failed because it failed to acquire Transaction manager's master lock. |
|
Action |
Contact your Oracle support. | |
|
1325 |
ERROR: Failed to get the TX tree node lock. | |
|
|
Description |
Unable to acquire the transaction manager access lock to access transaction tree node. |
|
Action |
Contact your Oracle support. | |
|
1326 |
ERROR: Failed to get the TX manager master lock. | |
|
|
Description |
Unable to acquire the transaction manager master lock. |
|
Action |
Contact your Oracle support. | |
|
1327 |
ERROR: Failed to get the transaction access lock. | |
|
|
Description |
Unable to acquire the transaction manager access lock. |
|
Action |
Contact your Oracle support. | |
|
1328 |
ERROR: Transaction manager received NULL request. | |
|
|
Description |
Transaction manager received a |
|
Action |
Contact your Oracle support. | |
|
1329 |
ERROR: Transaction manager received UNKNOWN event. | |
|
|
Description |
Transaction manager received |
|
Action |
Contact your Oracle support. | |
|
1330 |
WARNING: Normal branch state transition error, state(st) event(evt). | |
|
|
Description |
Transaction branch state transition error, it received an event evt at state st. |
|
Action |
Contact your Oracle support. | |
|
1331 |
ERROR: Normal branch state transition error, state(st) event(evt). | |
|
|
Description |
Normal transacton branch state transition error, it received an event evt at state st. |
|
Action |
Contact your Oracle support. | |
|
1332 |
ERROR: Invalid input object pointer! | |
|
|
Description |
The input state object pointer is not valid. |
|
Action |
Contact your Oracle support. | |
|
1333 |
ERROR: Invalid input object initial state! | |
|
|
Description |
The input state object state is not a valid state. |
|
Action |
Contact your Oracle support. | |
|
1334 |
ERROR: Invalid input object type! | |
|
|
Description |
The input object is not a state capable object. |
|
Action |
Contact your Oracle support. | |
|
1335 |
ERROR: Event evt is not allowed for state st! | |
|
|
Description |
The event evt is not allowed for state st. |
|
Action |
Contact your Oracle support. | |
|
1336 |
ERROR: Invalid object event test metric with value v for state st! | |
|
|
Description |
The tested event return a value v that is not valid for object at current state st. |
|
Action |
Contact your Oracle support. | |
|
1337 |
WARNING: Inbound transaction state transaction error, state(st event(e). | |
|
|
Description |
The inbound transaction encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1338 |
ERROR: Inbound transaction state transition error, state(st) event(e). | |
|
|
Description |
The inbound transaction encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1339 |
WARNING: Outbound transaction state transition error, state(st) event(e). | |
|
|
Description |
The outbound transaction encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1340 |
ERROR: Outbound transaction state transition error, state(st) event(e). | |
|
|
Description |
The outbound transaction encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1341 |
ERROR: Outbound transaction state transition error, state(st) event(e). | |
|
|
Description |
The outbound transaction encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1342 |
ERROR: Recovery transaction state transition error, state(st) event(e). | |
|
|
Description |
The recovery transaction encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1343 |
WARNING: Recovery branch state transition error, state(st) event(e). | |
|
|
Description |
The recovery transaction branch object encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1344 |
ERROR: Recovery branch state transition error, state(st) event(e). | |
|
|
Description |
The recovery transaction branch object encountered state transition error, the current state is st and the input event is e. |
|
Action |
Contact your Oracle support. | |
|
1345 |
ERROR: Failed to advertise the request TMS service | |
|
|
Description |
GWWS failed to advertise the TMS service to the Tuxedo application domain. |
|
Action |
Check your TUXCONFIG to see whether you have enough resource configured. | |
|
1347 |
ERROR: Invalid input trace object pointer! | |
|
|
Description |
The input tracing object is |
|
Action |
Contact your Oracle support. | |
|
1348 |
ERROR: Invalid input trace object pointer! | |
|
|
Description |
The input tracing object is |
|
Action |
Contact your Oracle support. | |
|
1349 |
ERROR: Input event e out of range!(max) | |
|
|
Description |
The input event e is out of range. |
|
Action |
Contact your Oracle support. | |
|
1350 |
ERROR: Invalid input trace object pointer! | |
|
|
Description |
The input tracing object is |
|
Action |
Contact your Oracle support. | |
|
1351 |
ERROR: invalid input trace object pointer! | |
|
|
Description |
The input tracing object is |
|
Action |
Contact your Oracle support. | |
|
1352 |
ERROR: Invalid input event identifier(evt! | |
|
|
Description |
The input event identifier is out of legally supported range. |
|
Action |
Contact your Oracle support. | |
|
1353 |
The message was invalid for the current state of the activity. | |
|
|
Description |
The soap fault message. |
|
Action |
No action required. | |
|
1354 |
ERROR: The Web Service gateway is not configured to support WS-TX transactions. | |
|
|
Description |
GWWS is not configured to handle WS-TX transaction. |
|
Action |
Change your GWWS deployment configuration file to add transaction support. | |
|
1355 |
ERROR: Cannot propagate WS-COOR context. Make sure WS-Addressing is configred for this service. | |
|
|
Description |
Cannot propagate WS-COOR context. Make sure WS-Addressing is configured for this service. |
|
Action |
Contact your Oracle support. | |
|
1356 |
ERROR: This service definition defines a MUST FLOW ATAsertion but no transaction has been started. | |
|
|
Description |
The service request is not transactional but a MUST FLOW ATAsertion is configured in the service definition. |
|
Action |
Either remove MUST FLOW ATAsertion or start a transaction. | |
|
1357 |
ERROR: This call is transactional, but the service definition does not specify an ATAssertion element. | |
|
|
Description |
This service request is transactional but the service definition does not specify an ATAsesertion element. |
|
Action |
Correct the service definition by adding ATAsertion element. | |
|
1358 |
ERROR: Memory allocation for output buffer failed. | |
|
|
Description |
Memory allocation failed for output buffer. |
|
Action |
Add more memory to the system. | |
|
1359 |
ERROR: Memory allocation for output buffer failed. | |
|
|
Description |
Memory allocation failed for output buffer. |
|
Action |
Add more memory to the system. | |
|
1360 |
ERROR: no ReferenceParameters in this Prepare message header. | |
|
|
Description |
No ReferenceParamter in this ws-at:Prepare message header. |
|
Action |
Contact your Oracle support or your remote transaction participant provider. | |
|
1361 |
ERROR: Failed to establish WS-COOR registration service connection. | |
|
|
Description |
Failed to establish WS-COOR registration service connection. |
|
Action |
Contact your Oracle support. | |
|
1362 |
ERROR: Failed to establish WS-COOR registration service connection. | |
|
|
Description |
GWWS failed to establish WS-COOR registration service connection. |
|
Action |
Contact your Oracle support. | |
|
1363 |
ERROR: Maximum WS transaction limit reached(max), transaction creation failed. | |
|
|
Description |
The configured MaxTran limit reached so Transaction manager failed to create the transaction. |
|
Action |
Increase configured MaxTran in the deployment configuration file. | |
|
1364 |
WARN: Configured MaxTran (max) greater than allowed number of Tuxedo transaction(tmax, set to Tuxedo limit. | |
|
|
Description |
The configured MaxTran in deployment configuration file exceeded the Tuxedo transaction limit so use Tuxedo maximum transaction value. |
|
Action |
Do nothing or correct either Tuxedo maximum transaction or GWWS MaxTran. | |
|
1365 |
WARN: Configured MaxTran (max) greater than maximum number of outstanding transaction supported by GWWS(1600), set to GWWS limit. | |
|
|
Description |
The configured MaxTran is greater than maximum GWWS can support so use GWWS limit. |
|
Action |
Do nothing or correct either Tuxedo maximum transaction or GWWS MaxTran. | |
|
1366 |
ERROR: TUXCONFIG environment variable not set. | |
|
|
Description |
It is required to set TUXCONFIG environment variable before running |
|
Action |
Set the correct TUXCONFIG environment variable. | |
|
1367 |
ERROR: TUXCONFIG environment variable must be an absolute pathname. | |
|
|
Description |
The TUXCONFIG environment value be a absolute path. |
|
Action |
Change to use absolute pathname for your envirnoment. | |
|
1368 |
ERROR: Error in reading TUXCONFIG file. | |
|
|
Description |
GWWS encountered an error while reading TUXCONFIG. |
|
Action |
Contact your Oracle support. | |
|
1369 |
ERROR: UID in TUXCONFIG does not match your effective user ID. | |
|
|
Description |
The UID configured in TUXCONFIG does not match your effective user ID. |
|
Action |
Modify your TUXCONFIG file. | |
|
1370 |
WARN: Could not find transaction in transaction table. | |
|
|
Description |
Unable to find a transaction in the transaction table. |
|
Action |
Contact your Oracle support. | |
|
1371 |
WARN: Failed to find transaction(ctx) | |
|
|
Description |
Failed to find a transaction with coordinator context ctx. |
|
Action |
Contact your Oracle support. | |
|
1372 |
ERROR: The Web Service gateway cannot create more WS-TX transaction. | |
|
|
Description |
GWWS can not create more WS-TX transaction. |
|
Action |
Increase you number of transaction configured. | |
|
1373 |
ERROR: The Web Service gateway cannot start any more WS-TX transaction | |
|
|
Description |
GWWS can not create more WS-TX transaction. |
|
Action |
Increase you number of transaction configured. | |
|
1374 |
WARN: Failed to decode transaction record, record is skipped. | |
|
|
Description |
GWWS failed to decode a transaction log record during recovery, the record is skipped. |
|
Action |
Contact your Oracle support. | |
|
1375 |
ERROR: Failed to create transaction log. | |
|
|
Description |
Transaction manager failed to create transaction log. |
|
Action |
Contact your Oracle support. | |
|
1376 |
ERROR: Failed to process transaction log. | |
|
|
Description |
GWWS encountered error during transaction recovery. |
|
Action |
Contact your Oracle support. | |
|
1377 |
ERROR: Failed to open transaction log. | |
|
|
Description |
Transaction manager failed to open a transaction log. |
|
Action |
Check whether the transaction log is configured correctly in the deployment configuration file. | |
|
1378 |
WARN: Unknown transaction structure id(v) found in transaction log file. | |
|
|
Description |
An unknown transaction structure id of value v is found in transaction log file. The log page encountered this problem will be skipped. |
|
Action |
Contact your Oracle support. | |
|
1379 |
WARN: Unknown branch structure id(v) found in transaction log file. | |
|
|
Description |
An unknown transaction structure id of value v is found in the branch object in thetransaction log file. The log page encountered this problem will be skipped. |
|
Action |
Contact your Oracle support. | |
|
1380 |
WARN: Received ws-at:Committed without transaction id, ignoring it | |
|
|
Description |
A ws-at:Committed message is received without proper transaction id associated with the message so ignore it. |
|
Action |
Contact remote participant application service provider. | |
|
1381 |
ERROR: GWWS wstx mutex initilization failed | |
|
|
Description |
Failed to initialize WSTX mutex. |
|
Action |
Contact your Oracle support. | |
|
1382 |
ERROR: GWWS wstx mutex destroy failed. | |
|
|
Description |
Failed to destroy WSTX access mutex. |
|
Action |
Contact your oracle support. | |
|
1383 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WSTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1384 |
ERROR: no more space in wstxTable | |
|
|
Description |
The GWWS encountered WS-TX related internal problem. |
|
Action |
Contact your Oracle support. | |
|
1385 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1386 |
WARN: No transaction ID present in this message | |
|
|
Description |
A WS-AT message is received without transaction ID. |
|
Action |
Contact your remote service application provider. | |
|
1387 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1388 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Informational message, no action required. | |
|
1389 |
ERROR: could not find transacton in wstxTable for wake up... | |
|
|
Description |
Receive a WS-AT message but could not find the transaction in the internal table. |
|
Action |
Contact your Oracle support. | |
|
1390 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1391 |
ERROR: on return from TFSM for event OUTBOUND WsPrepared | |
|
|
Description |
TFSM returned error after processing outbound ws-at:Prepared message. |
|
Action |
Contact your Oracle support. | |
|
1392 |
ERROR: on return from TFSM for event OUTBOUND WsAborted | |
|
|
Description |
TFSM returned error after processing outbound ws-at:Aborted message. |
|
Action |
Contact your Oracle support. | |
|
1393 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1394 |
ERROR: wsat/Prepare handling - lookup up TX node to get GTRID | |
|
|
Description |
GWWS encountered a problem when handling a ws-at:Prepare message lookup operation. |
|
Action |
Contact your Oracle support. | |
|
1395 |
ERROR: wsat/Rollback handling - lookup up TX node to get GTRID | |
|
|
Description |
GWWS encountered a problem when handling a ws-at:Rollback message lookup operation. |
|
Action |
Contact your Oracle support. | |
|
1396 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
|
1397 |
ERROR: could not find transaction in wstxTable | |
|
|
Description |
GWWS WSTX encountered problem and could not find transaction in the internal table. |
|
Action |
Contact your Oracle support. | |
|
1398 |
ERROR: no ReferenceParameters in this RegisterResponse header... | |
|
|
Description |
Received a ws-at:RegisterResponse message without ReferenceParameters element. |
|
Action |
Contact your remote participant application provider. | |
|
1399 |
ERROR: GWWS wstx mutex lock failed | |
|
|
Description |
Failed to acquire WXTX access lock. |
|
Action |
Contact your Oracle support. | |
 |
 |
 |