If you are using the CQ5.5 authoring environment to add links to DAM assets through the rich-text editor dialog by drag-and-drop, then you may notice that some of these links will be marked invalid after clicking OK on the dialog.
A invalid link appears like the “banking” text below, whereas a valid link appears like the “investors” text.
You may also see errors similar to the following in the error.log:
*ERROR* [0:0:0:0:0:0:0:1  GET /libs/wcm/core/content/pageinfo.json HTTP/1.1] com.day.cq.wcm.core.impl.servlets.PageInfoServlet Request path does not resolve to a resource: /content/dam/geometrixx/documents/GeoSphere_D%20a%20tasheet.pdf
The links are marked invalid when the assets in DAM contain spaces, or other characters such as !%$üäö, in the file-name (e.g. GeoSphere_D a tasheet.pdf). Such file-names are being parsed by a URL encoder and the characters get converted by a URL encoder at the wrong place.
You can workaround this issue by creating the link with the in-place editor, and also creating the link manually using the link button in the rte dialog, and selecting the document through the browse function. Only drag&drop directly onto the text in the rte dialog is not working.
This is a product issue with the rich-text widget and has been fixed in later product versions.
If you wish to resolve this issue in CQ5.5 you should contact support through Daycare and request hotfix “cq-5.5.0-hotfix-2390-1.zip”. This hotfix has dependencies on other components, so the support team can advise you on installation order and requirements.
If you are installing Workflow 7.2.2 onto a DB2 database you may encounter the following error during the bootstrapping process:
“A system temporary table space with sufficient page size does not exist”
This is due to the “CREATE TEMPORARY TABLESPACE” command having failed when you created the LiveCycle Database.
This can occur when the DB creation script is invalid, due to missing line breaks, or spaces. Please consult the appropriate LC installation documentation for your version. The script for LC7 is as follows:
CREATE TEMPORARY TABLESPACE ADOBE_TEMP_8K IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING (‘C:\DB2\ADOBE_TEMP’) EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;
CREATE REGULAR TABLESPACE ADOBE_DATA_8K IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING (FILE’C:\DB2\ADOBE_DATA’1000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL BP8K;
When opening Workbench after migrating from LC7, or after manually deploying many LC7 QPACs in the LC7.x components view, you may receive the following error:
Caused by: java.lang.OutOfMemoryError: Java heap space ; nested exception is:
java.lang.OutOfMemoryError: Java heap space
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationConte xt.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
This may be accompanied with internal errors in Workbench, or other memory warnings and messages.
The OutOfMemoryError occurs as the server is loading all of the LC7 component configurations at the same time and sending all of this information to the Workbench client. It cannot handle this amount of data at one time, and so, throws the memory errors. The server may also be hitting some memory limitations depending on the heap size and platform (i.e. weblogic uses a lot more RAM than JBoss).
This issue has been fixed in Workbench ES 184.108.40.206 and later versions. There is a patch available for both the server and workbench 220.127.116.11. You should contact Adobe support if you require this patch.
The patch will expose a new parameter in the workbench.ini file to control the pageSize for the communication between the LiveCycle server and Workbench. You can check this parameter in <Workbench_Home>/Workbench/workbench.ini. The parameter should be set to 3 to resolve the OOM situation:
After making any such changes to the configuration of Workbench you may need to start Workbench cleaning out the temp files. You can do this by starting Workbench from the command line from the directory listed above using the -clean console command line switch.
You should also try increasing the JVM heap size for both the server and Workbench, and run Workbench on a separate machine to the LiveCycle server, if you are not already doing so.