Troubleshooting

 

Use

If you think there may be problems with the enqueue service, you can test the individual layers. Then you can approach SAP support with a more precise problem description.

Known problems and their solutions are described in the section Known Problems.

Prerequisites

To identify and fix problems yourself, you should be familiar with the architecture of the enqueue service (see Architecture of the Locking Service).

The layers that can be tested are shown in the graphic below.

For more information about the architecture of the SAP Web AS for Java, see the Architecture Manual.

Procedure

Test the layers from top to bottom. Each layer creates a trace file.

Native Enqueue Library

With the program enqt you can test the native enqueue library. The program can be found in the directory usr/sap/sys/run. You have to enter the profile (for example, enqsrv.pf in the server directory).

If you enter enqt –help, you see which opcodes are possible and what they mean.

Examples

·        You can display all existing locks, by entering enqt pf=<profile> 20.

If this works, you can assume that the enqueue server process is running, and the profile and libraries are OK.

·        The opcode 8 (entry enqt pf=<profile> 8) generates statistics periodically.

·        Opcode displays the statistics.

Trace file

The relevant trace file is dev_eq_java and is located in the server directory. The other dev_* files may also be relevant. You can display the files in the Visual Administrator. Choose View Files ® Trace file of the native library of the enqueue server.

You can set the trace level in the enqsrv.pf profile file.

  

Note that enqt is a powerful program, with which you could also bring the enqueue service to a standstill. The other opcodes should only be used by SAP for testing.

Java Enqueue Library

You can test the Java enqueue using the EnquLocktableTest class. In the server directory call:

java -cp bin/kernel/jenqulib.jar com.sap.bc.krn.enqu.EnquLocktableTest <arguments>

If you delete <arguments>, the options that you can enter will be displayed.

The main test is started with the command:

java ‑cp bin/kernel/jenqulib.jar com.sap.bc.krn.enqu.EnquLocktableTest pf=cfg/kernel/enqt.pf ‑repeat_lock 1 ‑repeat_read 1

 If no error message appears, you can assume that the error is not in this layer.

If you enter

java ‑cp bin/kernel/jenqulib.jar com.sap.bc.krn.enqu.EnquLocktableTest pf=cfg/kernel/enqt.pf ‑version

a version check is carried out.

Trace File

The relevant trace file is dev_eq_java and is located in the server directory.

You can set the trace level in the enqt.pf profile file.

Locking Manager of the J2EE Engine - Interface ServerInternalLocking

As described in Architecture of the Locking Service, the locking manager is implemented by the interface ServerInternalLocking. This may only be called from the J2EE Engine, and not from a J2EE application.

You can access the locking manager in the following ways:

·        via the locking service in Visual Administrator

·        Via shell commands of the locking service, see Administration of the Locking Adapter Service Using the Console

·        Via the standalone program "locking editor" in the server directory

The locking service in Visual Administrator is the same as in the standalone program. The options you have for testing are described in Locking Service (section Features).

Trace File

Look in the server directory in the /log/managers/locking/*.log files for incorrect entries. You can then view the files in Visual Administrator.

You can change the trace level in LockingManager properties. Tracing must be activated for this component.

Application Locking Service

This is the service for creating and releasing locks and is available to J2EE applications. 

You can access the application locking service in the following ways:

·        Via the application locking service in Visual Administrator (see Application Locking Service)

·        Via shell commands of the application locking service, see Administration of the Application Locking Service Using the Console

Trace File

Look in the server directory in the /log/services/applocking/*.log files for incorrect entries. You can then view the files in Visual Administrator.

You can change the trace level in applocking.properties. Tracing must be activated for this component