(21901521) DateFormat exceptions when using JDK 8.
If you are using JDK 8 update 60 or later, you may see DateFormat exceptions and other related exceptions. JDK 8u60 introduced a change that is incompatible with Joda-Time library versions used by Oracle Commerce and most supported application servers.
Workaround: The incompatibility has been fixed in Joda-Time version 2.8.1 and higher. You can download this library at:
https://github.com/JodaOrg/joda-time/releases
Add the JAR file to the CLASSPATH of your application server. Make sure it appears earlier in the CLASSPATH than any older version of the library.
(21379275) Duplicate message sinks or filters created in Patch Bay.
If an exception occurs while the Patch Bay MessagingManager component is starting up, the startup process is reinitiated. Message sinks and filters that have already been created are created again, resulting in duplicate copies. This can lead to components receiving the same message multiple times, or scenarios executing multiple times for the same scenario event.
Workaround: Resolve the startup errors to ensure that Patch Bay does not need to be reinitialized. Restart the affected server instances.
(18903573) When running against a DB2 database, the following exception occurs:
[jcc][t4][10401][12066][3.67.26] XA exception: XA_RBOTHER ERRORCODE=-4228,
SQLSTATE=null
Workaround: If you see this exception, do the following:
Use the db2jcc4.jar driver found in your installed version of DB2 instead of the db2jcc.jar driver.
Create a custom property, called
queryCloseImplicit, and set it to 2 for both publishing and production data sources. For instructions on creating this property, see http://www-01.ibm.com/support/docview.wss?uid=swg21429116.
(16176316) DB2 Schema contains column with incorrect column type, which may cause errors in the messaging system.
In DB2 environments, the dms_limbo_delay table contains the jms_destination column. This column uses an incorrect column type, which corresponds to the dmsLimboMessage.jmsDestination property and creates errors when viewing dmsLimboMessages. The database column type used by other databases is blob.
Workaround: Delete the row from the dms_limbo_delay table. Once the rows are deleted, dmsLimboMessage items can be listed in the Dynamo Server Admin.
(15922809) Using the runAssembler script to assemble a Web application with XML-encoded UTF-8 characters in its context root may cause application server deployment errors. The runAssembler script writes the actual UTF-8 characters in the web.xml and application.xml files for the Web application EAR file.
Workaround: Manually edit the web.xml and application.xml files. Replace any UTF-8 characters with the XML-encoded versions of those characters.
(14304845) Installing the Oracle Commerce Platform with Java 7 on a Windows operating system may prevent users from accessing the Dynamo Server Admin user interface. Attempting to log into /dyn/admin results in page compilation errors.
Workaround: Add the lib\tools.jar file from the JDK to the CLASSPATH of the Oracle Commerce Platform instance that is running the Dynamo Server Admin, and set the value of the /atg/dynamo/servlet/pagecompile/PageProcessor.javaCompilerClassName property as follows:
javaCompilerClassName=atg.servlet.pagecompile.SunJavaSourceCompiler
(14187240) Deploying large amounts of data while using an Oracle JRockit Java Virtual Machine (JVM) may consume excessive processing resources.
Workaround: Make sure your JVM and operating system are configured for maximum performance. See information about tuning the Oracle JRockit JVM at http://docs.oracle.com/cd/E15289_01/doc.40/e15060/bestpractices.htm.
(13559803) SQL repository caching causes repository queries that include property hints to fail.
If you are using SQL repository caching, Repository Query Language (RQL) queries that include property hints may produce an error rather than returning query results.
Workaround: Invalidate cached repository item data before executing queries.
(13312273) Japanese characters in e-mail subjects appear as numeric encoding.
Non-ASCII characters in the subject lines of e-mails you send through the Oracle Commerce Platform may appear as numbers in the recipient’s e-mail client.
Workaround: Set the sending system’s default locale to UTF-8 to ensure non-ASCII characters are encoded correctly.
(13297984) startSQLRepository and runAssembler scripts fail if DISPLAY variable is set to a remote machine.
If you run the startSQLRepository or runAssembler script on a UNIX-based system whose DISPLAY variable is set to a remote machine, the script will fail if the remote machine does not allow host connections.
Workaround: Configure the remote machine to allow host connections.
(13296892) Using the i-net MERLIA JDBC driver with Microsoft SQL Server databases prevents repository validation.
If you use the i-net MERLIA JDBC driver, your Oracle Commerce Platform application may not be able to validate its repository configuration.
Workaround: Use the Microsoft SQL Server JDBC Driver instead of the i-net MERLIA JDBC driver.
(13294120) Error connecting to Oracle 11g database from a 64-bit Linux system.
When connecting to an Oracle 11g database from a 64-bit Linux system, you may see connection errors. This is due to a bug in the Java API used by the Oracle drivers.
Workaround: For information about this bug and how to work around it, see:
http://bugs.sun.com/view_bug.do?bug_id=6521844(13272692) Out of memory exception running startSQLRepository script.
When running the startSQLRepository script, you might receive an exception of class java.lang.OutOfMemoryError.
Workaround: Edit the script and increase the memory allocation. Find the line that invokes the class atg.adapter.gsa.xml.TemplateParser. Immediately in front of the class name, add these arguments:
-Xmx512m -Xms512m
