IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting the z/OS installation and configuration > IBM BPM configuration errors

Repeated SIB messages about acquiring and losing locks

This error can occur after correcting the DB2 Universal Driver configuration and restarting the server. The error messages are repeated continuously in the adjunct region.

ExtendedMessage: BBOO0222I: 
[CommonEventInfrastructure_Bus:mdnodea.mdsr01a-CommonEventInfrastructur e_Bus]
CWSIS1538I: The messaging engine, ME_UUID=68E9550CE7780888, 
INC_UUID=5f244052b02f04b4, 
is attempting to obtain an exclusive lock on the data store.
..
.. 
ExtendedMessage: BBOO0222I: 
[CommonEventInfrastructure_Bus:mdnodea.mdsr01a-CommonEventInfrastructur e_Bus] 
CWSIS1546I: The messaging engine, ME_UUID=68E9550CE7780888, 
INC_UUID=5f244052b02f04b4, 
has lost an existing lock or failed to gain an initial lock on the database

These error messages indicate that there is a problem accessing the data store. Check that the fixWPSvars.jacl had created (jdbc/MEdatasource) in the datasource. Check that the datasource has an JCA authentication alias associated with it. If there is no JCA authentication alias associated with the datasource the database access defaults to the user ID of the servant region and tries to find tables called MKASRU which do not exist.

This error can occur because the -sibauth option has not been coded when running fixWPSvars.jacl. You can fix this in a number of ways:

• Associate the JDBC datasources used by the SIBs with the JCA authentication alias called WPSDBAlias.

• Create a new JCA Authentication Alias and associate that with the JDBC. Re-run fixWPSvars.jacl using the -sibauth option to specify WPSDBAuth as the JCA authentication alias, or use the WebSphere administrative console to make the change, specifying WPSDBAlias as the alias name.

The following steps explain how to create a new JCA authentication alias to be used by the SIBs to access DB2:

1. Open the WebSphere administrative console and navigate to Security → Global security.

2. Click the link to J2C Authentication data under Additional Properties.

3. Click the New button.

4. Enter a name for the alias, and enter the user ID and the password for the alias.

5. Click OK.

6. Click Save.

The following steps explain how to associate the Service Integration Buses with the authentication alias that you have created:

1. Open the WebSphere administrative console and navigate to Service integration → Buses.

2. Click the first bus in the list.

3. On the next panel, click Messaging engines.

4. Click the hyperlink to the messaging engine.

5. Click the link to Data store under Additional Properties.
6. Expand the drop-down list box in the Authentication alias field and select the alias you created earlier.

7. Click OK and then save the change to the configuration.

8. Click the link at the top of the page to navigate back to the list of buses.

9. Select the next bus in the list and repeat the same procedure. Repeat for the remaining buses.

10. When all the buses have been updated to refer to a valid JCA authentication alias and stop and restart the server.

: IBM BPM configuration errors