| Symptom | If, after installing the fix and restarting the server, a flow with
parallel activities (both implemented via compensation pairs) run together
and the flow database is hosted by Oracle, the following exception occured
and the flow fails with a system exception: [2/26/03 16:59:49:046 CET] 372bdb ExceptionUtil E CNTR0021E: Non-application exception occurred on bean "BeanId(BPEContainer_platane_server1#compensate_ejb.jar#Coordinator, 9ADC3C37-00F3-3000-E3F1-43F109985C7D)": Exception data: java.rmi.NoSuchObjectException: com.ibm.ws.ejbpersistence.utilpm.OptimisticUpdateFailedException: PMGR6025E: An attempted update under optimistic concurrency control failed because another application has changed the bean data in the datastore since this transaction read it. Either it changed a predicate field value or removed the bean itself. |
| Customer Impact | 1. Travel Booking Sample is an example of such a flow and hence fails
on Oracle 2. User macroflows that have parallel activities may encounter this problem on Oracle |
| Workaround (if any) | None |
PQ72173
| Symptom | After applying PQ71037 and executing bpeupgrade.jacl, the Business
Process Web Client stops working if security was enabled before the
execution of bpeupgrade.jacl. This is caused by the wsadmin command not
preserving the "AllAuthenticatedUsers" portion of the mapping from roles
to users.
NOTE: This defect is a WAS 5.0 base defect |
| Customer Impact | If security was enabled before the fixes were applied, the Web Client is unable to function after the fixes have been applied. |
| Workaround (if any) | Using the admin console, update the
BPEContainer_<nodename>_<servername> application via
Applications > Enterprise Applications > BPEContainer_<node>_<server> Additional Properies > Map security roles to users/groups Select "All Authenticated" for WebClientUser and JMSAPIUser Map your userid to BPESystemAdministrator Save your changes |
PQ72181 Note that this defect is NOT caused by the fix, but is a problem found when installing the fix
| Symptom | After installing PQ71037 and restarting the server, all Business Processes
fail.
NOTE: This defect is present in the 5.0 GA code and can also be triggered by configuring the flow container using the "INSTALL" button from the admin console's business process container page. |
| Customer Impact | After installing the fix and restarting the server, any flow will fail
with the following exception: [3/6/03 16:27:13:171 CST] 3e6bcd7c ConnectionFac I J2CA0107I: Component-managed authentication alias not specified for connection factory or datasource JMS$BPECF$JMSManagedConnection@1116999018. [3/6/03 16:27:13:280 CST] 3e6bcd7c Helpers W NMSV0605W: A Reference object looked up from the context "java:" with the name "comp/env/jms/BPECFC" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows: Reference Factory Class Name: com.ibm.ws.util.ResRefJndiLookupObjectFactory Reference Factory Class Location URLs: <null> Reference Class Name: java.lang.Object Type: ResRefJndiLookupInfo Content: com.ibm.ws.util.ResRefJndiLookupInfo@58dd8d6a ResRefJndiLookupInfo: Look up Name="jms/BPECFC";JndiLookupInfo: jndiName=<NULL>; providerURL=""; initialContextFactory="" |
| Workaround (if any) | Using the admin console, update the
BPEContainer_<nodename>_<servername>
application Applications > Enterprise Applications > BPEContainer_<node>_<server> Additional Properies > Mapping Resource References to Resources Select "Generic Process Choregrapher EJB" Update the JNDI name to "jms/BPECFC" Save your changes |
PQ72218
| Symptom | The DDL Script to upgrade the database schema for the fixes on DB2/zOS does not contain the definition for required tablespaces |
| Customer Impact | If DB2/zOS is used as the database by the flow container, invocation of the first compensation pair in a flow will result in an error message that a table space has not been found |
| Workaround (if any) | Update the createTablespaceDb2V6zOs.ddl to add the additional table
spaces and rerun the ddl: CREATE LOB TABLESPACE AUXTS40 IN @DBNAME@ USING STOGROUP @STG@ CREATE LOB TABLESPACE AUXTS42 IN @DBNAME@ USING STOGROUP @STG@ |