WAS v8.5 > Troubleshoot > Troubleshooting Service integration > Problem solving for messaging engine data stores

Diagnose problems with data store exclusive access locks

Diagnose the causes of problems with data store exclusive access locks and examine possible causes to the problems. Each messaging engine establishes an exclusive lock on its data store. While the messaging engine is running, it maintains that lock to ensure the integrity of the data within the data store.

Compare your symptoms with those listed in the following table and examine the possible solutions:
Symptom Cause Solution
The messaging engine cannot start. The messaging engine writes error message CWSIS1519 The messaging engine cannot connect to the database that you specified in the data source that you configured to enable the messaging engine to access its data store.

  • Check that connectivity to the database is possible when using the defined data source.

The messaging engine fails to start and writes error messages CWSIS1535 and CWSIS1519 The identifiers in the SIBOWNER table do not match those of the messaging engine.

  • Check the data source that you configured for the messaging engine refers to the correct database.

  • If the MEUUID identifiers do not match, check that a previous messaging engine did not use the same tables. If the tables already exist, DROP the tables and CREATE them again for the new messaging engine.

  • If the INCUUID identifiers do not match, another instance of the same messaging engine is running and has acquired the lock. Check for other running instances of the messaging engine.

The messaging engine starts but then stops and writes error message CWSIS1519. The messaging engine has lost its lock on the data store.

  • Check that we have connectivity to the database through the data source that you specified. The messaging engine might have lost network connectivity and be unable to maintain a connection with the database.

  • If we can connect to the database, another instance of the messaging engine might have started and obtained a lock on the data store. Check for other running instances of the messaging engine.


Related concepts:

Data store exclusive access


Related


Tune the detection of database connection loss
Troubleshooting service integration technologies


+

Search Tips   |   Advanced Search