Archive for June, 2009

LiveCycleES: NullPointerException trying to upgrade a LC7 process in Workbench

Issue

When trying to upgrade a LC7 process in Workbench, which is working fine under the LC7 compatibility layer you may receive an internal error in the upgrade report, with the following exception in the detail dialog:

java.lang.NullPointerException
at com.adobe.workflow.template.document.AbstractRouteTemplate.copyToAction(AbstractRouteTemplate.java:90)
at com.adobe.lcide.upgrade.lc8.dom.impl.ProcessRepositoryImpl.copyOutRoutes(Unknown Source)
at com.adobe.lcide.upgrade.lc8.dom.impl.ProcessRepositoryImpl.copyRouteInformationToBranch(Unknown Source)
at com.adobe.lcide.upgrade.lc8.dom.impl.ProcessRepositoryImpl.processBranch(Unknown Source)
at com.adobe.lcide.upgrade.lc8.dom.impl.ProcessRepositoryImpl.orchestrateProcess(Unknown Source)
at com.adobe.lcide.upgrade.lc8.app.UpgradeEngine.performUpgrade(Unknown Source)
at com.adobe.lcide.upgrade.lc8.pres.wizard.page.UpgradePageModel$UpgradeJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Troubleshooting

This will be related to a particular QPAC in the process which does not have the correct mapping file for the Upgrade Process Tool.  The report will show you on which QPAC the exception occurred, or you can remove each QPAC from the process one after the other, and re-test to isolate the problem QPAC.

Solution

Once you know what QPAC causes the issue, you should ensure you have the current upgrade mapping file for that QPAC loaded in Workbench.  If the QPAC is from another vendor, then contact that vendor for the latest mapping file, and load it into Workbench under Preferences -> Upgrade Process Tool.

reference: (180890412/2324824)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle Designer: Processing Instruction <?templateDesigner StyleID aped3?> duplicated many times

Issue

You may notice your XDP files are bloating in size when you are working with Designer ES 8.2.1.  A simple XDP file of 100kb could easily bloat up to 5MB.

Reason

The StyleId processing instruction “<?templateDesigner StyleID aped3?>” is being duplicated many times in the XDP source.

Solution

This issue is fixed in Designer 8.2.1 SP2, and in Designer 9.  You can delete these duplicate processing instructions in the XML Source for your existing XDP files.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: “ALC-WKS-005-029: A problem occurred in the Submit Service” error submitting a form in Workspace

Issue

 When you are trying to submit a form in Workspace with LiveCycle ES you may receive the following error in the Workspace UI:

Task 101 has failed to submit. (ALC-WKS-007-072)

and the following exception in the server log:

2009-06-24 11:51:12,968 WARN [com.adobe.workspace.tasks.com.adobe.workspace.tasks.DocumentSubmitServlet] 
ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.
flex.messaging.MessageException: 
ALC-WKS-005-029: A problem occurred in the Submit Service. Please review the submit orchestration for this process.
at com.adobe.workspace.AssemblerUtility.createMessageException(AssemblerUtility.java:384)
at com.adobe.workspace.tasks.DocumentSubmitServlet.doPost(DocumentSubmitServlet.java:230)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.adobe.workspace.events.RemoteEventClientLifeCycle.doFilter(RemoteEventClientLifeCycle.java:138)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)

Reason

 This is due to an incorrect configuration in the submit service settings.

Solution

 The submit service for the form variable should have the following configuration:

reference: (181013769/2365358)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle Workbench ES: OutOfMemoryError when working with many LC7 QPACs

Issue

 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.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)   
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)   
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.

Reason

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

Solution

 This issue has been fixed in Workbench ES 8.2.1.3 and later versions.  There is a patch available for both the server and workbench 8.2.1.2.  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:
-Dcom.adobe.workbench.lc7component.pageSize=3
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.

 reference: (180896059/2325722)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle Workbench ES: PATRuntimeException: Invalid variable type

Issue

After migrating Adobe LiveCycle 7 to LiveCycle ES, the properties dialog for some of the LiveCycle 7 components do not open in imported processes in Workbench.  This issue occurs particularly with components from other vendors.

In the server log file, you may find an exception similar to the following:

<Mar 18, 2009 5:38:47 PM CET> <Error> <com.adobe.workflow.AWS> <server> <LCServer1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<anonymous>> <BEA1-30E1940ABA8BD8AE228B> <> <1237394327753> <000000> <stalling action-instance: 803 with message:
com.adobe.workflow.pat.PATRuntimeException: Invalid variable type. Variable: com.adobe.workflow.template.document.DefaultVariableTemplate@5ebcf7d, Type: lc7form at com.avoka.workflow.qpac.userplus.UserPlusService.A(Unknown Source) at
com.avoka.workflow.qpac.userplus.UserPlusService.execute(Unknown Source) at
com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:551) at
com.adobe.workflow.engine.ProcessEngineBMTBean.executeAction(ProcessEngineBMTBean.java:1933) at
com.adobe.workflow.engine.ProcessEngineBMTBean.asyncExecuteActionCommand(ProcessEngineBMTBean.java:1878) at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncExecuteActionCom
...

Reason

Most QPACs from LC7 need to be updated to be able to handle the new “lc7form” variable type.  According to the documentation on the adobe site, this is a pre-requisite for using LC7 QPACs in LC ES.

On pg.4 of the doc at: http://help.adobe.com/en_US/livecycle/8.2/upgrade_changes.pdf

there is the following text:

Changes in variable types

Adobe LiveCycle Workflow 7.x supported a series of variable types that you can use in process definitions. The form variable type is renamed lc7form when you upgrade to LiveCycle ES. The upgrade willautomatically update your processes to use the new variable type name; therefore, in most cases, thechange is transparent. However, if you are using a custom component from a third-party or have created oneinternally and the QPAC makes an explicit reference to the form variable type, the QPAC must be updatedto recognize the lc7form variable type name instead. The new QPAC must then be deployed to the serverfrom Adobe LiveCycle Workbench ES.

Solution

For Adobe components, make sure you are using the latest version of the component available from the Workflow SDK.  For QPACs from other vendors, please contact these vendors and request an updated QPAC which is compatible with LiveCycle ES.

To deploy the updated component:

  1. Copy the component jar file to a local folder on the server
  2. Open Workbench
  3. Show View -> LiveCycle 7.x components
  4. Right click in the LiveCycle 7.x components view, and select “Deploy new component”
  5. Browse to the component jar file from step 1 above
  6. Set the appropriate deployment properties for the component
  7. Click OK

You may have to close and re-open the process map in Workbench for the changes to take affect.  You should now be able to open the properties dialog for the affected component activity.

reference: (180802977/2302710)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)