Resolution:
When starting up the BC engine on a Linux system, the system may exhibit the following problems:

-  The engine may throw an RV-related exception and stop  
-  If it does start, errors may occur in BC or the BW private process related to data being missing from the payload.

This is because the RV jars files are not being loaded in the correct order in the classpath on Linux systems.

The classpath of the deployed BC engine includes the $RV_HOME/lib directory rather than the tibrvj.jar file specifically.   As a result, one of the other jars is picked up first and causes the issues described above.

To work around this issue, add the full path to the tibrvj.jar file into the PREPEND_TO_CLASSPATH variable when deploying BC to a Linux system.  This will force the jar files to be read in the correct order.

BC will not start (throws RV exception) or will not exchange information correctly with the private process on a Linux system.