Release Notes for Oracle TopLink
12c (12.1.3)
E54496-01
June 2014
This chapter describes issues associated with Oracle TopLink. It includes the following topics:
Section 4, "Managed Servers on Sybase with JCA Oracle Database Service"
Section 5, "Logging Configuration with EclipseLink Using Container Managed JPA"
This section contains information on the following issues:
Section 1.1, "Exalogic TuningAgent Profiler is not Set"
Section 1.2, "Cannot set EclipseLink log level in WLS System MBean Browser"
Section 1.3, "UnitOfWork.release() not Supported with External Transaction Control"
Section 1.4, "Returning Policy for UPDATE with Optimistic Locking"
Section 1.6, "Unit of Work does not add Deleted Objects to Change Set"
When using the TopLink Exalogic automated tuner, the oracle.toplink.exalogic.tuning.TuningAgent profiler is not enabled. The TuningAgent profiler has been disabled due to issues with stuck threads.
Use Oracle Enterprise Manager to set the EclipseLink log level; do not use the WLS System MBean Browser to complete this action.
A unit of work synchronized with a Java Transaction API (JTA) will throw an exception if it is released. If the current transaction requires its changes to not be persisted, the JTA transaction must be rolled back.
When in a container-demarcated transaction, call setRollbackOnly() on the EJB/session context:
@Stateless
public class MySessionBean
{ @Resource
SessionContext sc;
public void someMethod()
{
...
sc.setRollbackOnly();
}
}
When in a bean-demarcated transaction then you call rollback() on the UserTransaction obtained from the EJB/session context:
@Stateless
@TransactionManagement(TransactionManagementType.BEAN)
public class MySessionBean implements SomeInterface
{
@Resource
SessionContext sc;
public void someMethod()
{
sc.getUserTransaction().begin();
...
sc.getUserTransaction().rollback();
}
}
The returning policy, which allows values modified during INSERT and UPDATE to be returned and populated in cached objects, does not work in conjunction with numeric version optimistic locking for UPDATE. The value returned for all UPDATE operations is 1 and does not provide meaningful locking protection.
Do not use a returning policy for UPDATE in conjunction with numeric optimistic locking.
The use of returning policy for INSERT when using optimistic locking works correctly.
TopLink assumes that date and time information returned from the server will use Timestamp. If the JDBC driver returns a String for the current date, TopLink will throw an exception. This is the case when using a DB2 JDBC driver.
To work around this issue, consider using a driver that returns Timestamp (such as COM.ibm.db2.jdbc.app.DB2Driver) or change the policy to use local time instead of server time.
Another option is to use a query re-director on the ValueReadQuery used by the platform:
ValueReadQuery vrq = new ValueReadQuery(
"SELECT to_char(sysdate, 'YYYY-MM-DD HH:MM:SS.SSSSS') FROM DUAL"
);
vrq.setRedirector(new TSQueryRedirector());
...
class TSQueryRedirector implements QueryRedirector
{
public Object invokeQuery(DatabaseQuery query, Record arguments, Session session)
{
String value = (String)session.executeQuery(query);
return ConversionManager.getDefaultManager().convertObject(
value, java.sql.Timestamp.class
);
}
}
When accessing the change set of a Unit of Work to determine what has changed, objects that are pending deletion (such as uow.deleteObject( ) and uow.deleteAllObjects( )) will not be returned from the result set.
The objects pending deletion are only available through the Unit of Work getDeletedObjects call.
This section contains information on the following:
To fully support Oracle Spatial and Oracle XDB mapping capabilities (in both standalone Oracle WebLogic Server and the Oracle JDeveloper integrated WebLogic Server), you must use the toplink-spatial-template.jar and toplink-xdb-template.jar to extend the WebLogic Server domain to support Oracle Spatial and XDB, respectively.
To extend your WebLogic Server domain:
Download the toplink-spatial-template.jar (to support Oracle Spatial) and toplink-xdb-template.jar (to support Oracle XDB) files from:
Use Table 1, "To Support Oracle Spatial" or Table 2, "To Support Oracle XDB" to determine which files to copy.
Table 1 To Support Oracle Spatial
| Copy this file | From...Foot 1 | To...Foot 2 |
|---|---|---|
|
sdoapi.jar |
|
|
Footnote 1 These are the default locations. Your actual location may vary depending on your specific environment, installed options, and version.
Footnote 2 When using Oracle JDeveloper integrated WebLogic Server, the <WEBLOGIC_HOME> is located within the <JDEVELOPER_HOME> directory.
| Copy this file | From...Foot 1 | To...Foot 2 |
|---|---|---|
|
xdb.jar |
|
|
|
xml.jar |
|
|
|
xmlparserv2.jar |
|
|
|
orai18n-mapping.jarFoot 3 |
|
|
Footnote 1 These are the default locations. Your actual location may vary depending on your specific environment, installed options, and version.
Footnote 2 When using Oracle JDeveloper integrated WebLogic Server, the <WEBLOGIC_HOME> is located within the <JDEVELOPER_HOME> directory.
Footnote 3 Use orai18n-mapping.jar for Oracle Database 11.2 and higher.
Note:
Although the actual JAR file may be named differently in your From directory, the file must be named as shown, when copied to the To directory.
Launch the Config Wizard (<WEBLOGIC_HOME>/common/bin/config.sh (or .bat).
Select Extend an existing WebLogic domain.
Browse and select your WebLogic Server domain.
When using JDeveloper with integrated WebLogic Server, the typical WebLogic Server domain location may be similar to:
In Windows environments: %APPDATA%\JDeveloper\systemXX.XX.XX.XX\DefaultDomain
where XX.XX.XX.XX is the unique number of the product build.
For Windows platforms, you must enable the Show hidden files and folders folder option.
In non-Windows environments, the default location is under the current user's default home directory: <$Home>/DefaultDomain
Refer to the Oracle JDeveloper documentation for details.
Select Extend my domain using an existing extension template.
Browse and select the required template JAR (toplink-spatial-template.jar for Oracle Spatial, toplink-xdb-template.jar for Oracle XDB).
Complete the remaining pages of the wizard.
By default, EclipseLink interprets zero as null for primitive types that cannot be null (such as int and long) causing zero to be an invalid value for primary keys. You can modify this setting by using the allow-zero-id property in the persistence.xml file. Valid values are:
true – EclipseLink interprets zero values as zero. This permits primary keys to use a value of zero.
false (default) – EclipseLink interprets zero as null.
Refer the EclipseLink User's Guide at http://wiki.eclipse.org/EclipseLink/UserGuide for more information.
When using a JCA service with the Oracle Database adapter in a cluster to perform database operations on a Sybase database, the managed nodes in the cluster process the messages and may attempt to perform duplicate operations.
Because supported versions of Sybase do not support Oracle TopLink record locking, Sybase allows the duplicate operation attempts.
By default, EclipseLink users in container managed JPA will use the Oracle WebLogic Server logging options to report all log messages generated by EclipseLink. Refer to "Configuring WebLogic Logging Services" in Oracle® Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.
To use the EclipseLink native logging configuration, add the following property to your persistence.xml file:
<property name="eclipselink.logging.logger" value="DefaultLogger"/>
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Fusion Middleware, 12c (12.1.3) TopLink Release Notes
E54496-01
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.