WLS 10.0: Deployment Descriptor Configuration When Using Named Sequence Tables For Primary Key Generation.

(Doc ID 1087752.1)

Last updated on FEBRUARY 22, 2017

Applies to:

Oracle Weblogic Server - Version: 10.0 and later   [Release: and later ]
Information in this document applies to any platform.
***Checked for relevance on 06-10-2011***

Goal

You might have occasional concurrency problems for a specific Entity Bean in a multiple-server environment.  You will notice the error, [EJB:011103]Automatic Key Generation Error... apparently due to a Transaction Timeout (apparent DB lock contention).
After this error, you will notice a partial DB update and the data is corrupted.  The Entity Bean uses automatic key generation via a Named Sequence Table.
You will not explicitly be setting <transaction-isolation><isolation-level> as TransactionSerializable for this Entity Bean.  Does this option needs to be explicitly be set, or does WebLogic implicitly set it when the 'NAMED_SEQUENCE_TABLE' for automatic key generation type is used?
What is the optimal <automatic-key-generation><key-cache-size> when the table in question requires inserts from both a WebLogic-based EJB application, and a non-WebLogic standalone Java application? i.e. can both applications use the Sequence table to learn the next available key?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms