Release Notes for Oracle TopLink
12c (12.2.1.2.0)
E79112-01
October 2016
This document details issues associated with Oracle TopLink. It includes the following topics:
Section 5, "Managed Servers on Sybase with JCA Oracle Database Service"
Section 6, "Logging Configuration with EclipseLink Using Container Managed JPA"
The following features/enhancements are new in this release:
Bean Validation support in MOXy
http://aseng-wiki.us.oracle.com/asengwiki/display/ASDevWLS/MOXy+Bean+Validation+-+One+Pager#MOXyBeanValidation-OnePager-4.1.3.SchemaGensupport
JSON-P support in MOXy
https://wiki.eclipse.org/EclipseLink/DesignDocs/405161
JPA-RS Enhancements
http://review.us.oracle.com/review2/Review.html#reviewId=229982;documentId=690823;scope=document;status=open,fixed
http://aseng-wiki.us.oracle.com/asengwiki/download/attachments/168919160/Addition%20to%20JPA%20RESTful%20Services.pdf?version=1&modificationDate=1411030318000&api=v2
eclipselink.multitenant.strategy property for multi-tenancy
EclipseLink specific property (eclipselink.multitenant.strategy) has been introduced to support environments which are handling multitenancy transparently themselves. The value of this property can be either 'external' (any multitenancy requirements are expected to be handled externally (by application) and ignored by TopLink), or the fully qualified name of a class implementing org.eclipse.persistence.descriptors.MultitenantPolicy interface.
Usage of this option requires no @Multitenant entities defined, EntityManagerFactory is shared across tenants, its shared cache is disabled and no Entity defines its own schema.
The TopLink Grid feature in Oracle TopLink 12.2.1 is deprecated.
This section contains information on the following issues:
Section 3.1, "ERROR PARSING VALIDATION.XML - JAVA.UTIL.CONCURRENT.EXECUTIONEXCEPTION"
Section 3.3, "Cannot set EclipseLink log level in WLS System MBean Browser"
Section 3.4, "UnitOfWork.release() not Supported with External Transaction Control"
Section 3.5, "Returning Policy for UPDATE with Optimistic Locking"
Under some configurations, users may encounter a warning log message in the log file such as the one below. The log message is harmless and indicates TopLink's search for the validation.xml file (defined in the JSR 303 Bean Validation specification). TopLink is only able to read the validation.xml from the filesystem, not from archives of any kind.
[WARNING] [] [org.eclipse.persistence.jaxb.BeanValidationHelper] [tid: [STANDBY].ExecuteThread: '35' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: 8ee5cff5-3f55-4f1b-a389-4328958b1ee9-0000003d,0] [APP: webcenter] [partition-name: DOMAIN] [tenant-name: GLOBAL] Error parsing validation.xml[[ java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: URI scheme is not "file"
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
);
}
}
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.
Warning:
Adding this configuration property is potentially dangerous, as configuring this particular setting throughpersistence.xml affects ALL applications running on the serverWhen 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 that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=accid=info or visit http://www.oracle.com/pls/topic/lookup?ctx=accid=trs if you are hearing impaired.
Oracle Fusion Middleware, 12c (12.2.1.2.0) TopLink Release Notes
E79112-01
Copyright © 2014, 2016 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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.