WebSPhere: EJBConfigurationException: Using Commit Option A with a workload managed server

Problem(Abstract)
Installing the EJB 3.0 Feature Pack for WebSphere Application Server V6.1 might  result in the following exception when running an application that uses entity Container Managed Persistence Commit Option A in a clustered environment:

WSVR0068E: Attempt to start EnterpriseBean
..... failed with exception: com.ibm.ejs.container.EJBConfigurationException: Using Commit Option A with workload managed server is not supported.
 
Cause
Container Managed Persistence entity beans using "Commit Option A" are not supported in a clustered environment since it can have very severe consequences to data integrity. For more details, see EJB containers in the information center.However, in WebSphere Application Server Version 6.1 it is possible that no warnings or exceptions will be thrown if this unsupported configuration is attempted. Once the EJB 3.0 Feature Pack is installed, this unsupported behavior will be identified and an exception thrown.
 
Resolving the problem
It is highly recommended that "Commit Option A" not be used in a clustered environment. However, the exception that occurs once the EJB 3.0 Feature Pack is installed can be avoided by setting the property com.ibm.websphere.ejbcontainer.wlmAllowOptionAReadOnly to true:

Procedure
1. Open the administrative console.

2. Select Servers.

3. Select Servers > Application servers > server_name.

4. Under Server infrastructure, select Java and Process Management > Process  Definition.

5. Under Additional properties, select Java virtual machine > Custom properties > New.

6. In the Name entry field, type com.ibm.websphere.ejbcontainer.wlmAllowOptionAReadOnly.

7. In the Value entry field, type true.

8. Select OK.

from: https://www-304.ibm.com/support/docview.wss?uid=swg21419810