Exceptions and Error Messages

Process Engine has two different exception models, reflecting the C++ implementation of a server module and the Java™ implementation of the remaining modules (including also a server module). Additionally, the server C++ module has a number of interfaces contributing to Process-related errors.

The C++ server error are accessed using VWServerException.getTuple from Java to get a long value representing that error tuple. On the Java side, VWException.getKey returns a String version of the exception.

To get the C++ server errors, use the following as a coding model:

    Catch (VWServerException se)
        {
            if (se.getTuple == 123)
			    // do something
        }

To get the Java-side exceptions, use the following as a coding model:

    Catch (VWException e)
        {
            if (e.getKey().equals("filenet.api.server.CommandSessionError"))
			    // do something
        }

The Java exceptions (VWException) are logged in the jVWServern.exc file, where n is the number of the VWJ process. If server debugging is turned on in Process Task Manager and the VWJ trace is turned on from the vwtool application, the exceptions are also written to the FileNet elog file (default location is fnsw_loc\logs\elogs). You can view the elog file using the vl command. On Microsoft® Windows® platforms, you can also view the exceptions in the application log of Event Viewer.

For complete exception and error listings, see: