(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 Oracle ATG Web Commerce 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 a atg/dynamo/servlet/pagecompile/PageProcessor.properties file to the configuration path for the server running the Dynamo Server Admin. Configure the javaCompilerClassName property as shown below.


(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.

(13775672) Heavy user load degrades application performance when using Oracle JRockit.
If you use the Oracle JRockit JVM and you are not using an Oracle Exalogic server, you may experience longer response times and degraded site throughput during periods of peak user activity. For example, this may occur when processor utilization exceeds 50 percent and Java starts garbage collection. Under this heavy load, Oracle JRockit converts contended Java thin locks to fat locks which may degrade performance. This problem is not known to occur when using Oracle Exalogic servers.

Workaround: Set the Oracle JRockit -XX:ThinLockConvertToFatThreshold configuration option to 100000000 (100 million). Do not use this workaround if you are using an Oracle Exalogic server.

Important: Changing the ThinLockConvertToFatThreshold setting can be very useful in some cases; in others it can cause a significant increase in CPU usage and have a corresponding negative effect on performance. Use this setting with extreme caution.

(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 ATG Web Commerce 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.

(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.

(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.

(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

(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:


(13312273) Japanese characters in e-mail subjects appear as numeric encoding.
Non-ASCII characters in the subject lines of e-mails you send through Oracle ATG Web Commerce 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.

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices