Posts tagged "NoClassDefFoundError"

LiveCycle ES2: LCMException[ALC-LCM-030-200]: Failed to deploy component

Issue

If you are installing and deploying patches for LiveCycle ES2 using the command line version of LiveCycle Configuration Manager (LCM) you may encounter an error similar to the following while deploying components:

com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Failed to deploy component
 /opt/adobe/adobe_livecycle_es2/deploy/adobe-usermanager-dsc.jar.
         at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:419)
         at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(DeployDSCs.java:151)
         at com.adobe.livecycle.lcm.headless.HeadlessLCMImpl.deployDSCFilesLFS(HeadlessLCMImpl.java:285)
         at com.adobe.livecycle.lcm.cli.DeployLCComponentsCLI.executeCommandLineImpl(DeployLCComponentsCLI.java:96)
         at com.adobe.livecycle.lcm.cli.LCMCLI.execute(LCMCLI.java:298)
         at com.adobe.livecycle.lcm.cli.LCMCLI.main(LCMCLI.java:344)

and the LC logs may contain the following exception messages:

Component: com.adobe.PDFServices version: 9.0.0.2.20120202.1.312922 
introduced a new service, it should not be patched

….

java.lang.NoClassDefFoundError: com/adobe/idp/um/api/PreferenceManager

Reason

This problem occurs if the order of operations in LCM is incorrect.  For example, if you run the deploy components step (DSCs), before configuring and deploying the new EARs.  This can occur when using the command line LCM as you call each operation separately.  It can also occur using the UI LCM if you run the tool twice in succession and select to deploy components in the 1st run before deploying the EARs in the 2nd run.

Solution

You should re-run the LCM steps ensuring to configure and deploy the EARs first, before deploying the components.

 

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

LiveCycle ES: ALC-TTN-011-031: Bootstrapping failed for platform component [DocumentServiceContainer] | clustered environments

Issue

 If you are attempting a clustered installation of LiveCycle ES, you may experience errors during the bootstrapping phase of LiveCycle Configuration Manager (LCM) with the following exception in the LCM log:

[5/25/11 8:09:12:768 EDT] 0000003f DSCBootstrapp E com.adobe.livecycle.bootstrap.bootstrappers.AbstractBoostrapper log ALC-TTN-011-031: 
Bootstrapping failed for platform component [DocumentServiceContainer]. The wrapped exception's message reads: See nested exception; nested exception is: 
java.lang.Exception: java.lang.NoClassDefFoundError: com.adobe.livecycle.cache.adapter.GemfireCacheAdapter (initialization failure)

[5/25/11 8:09:12:768 EDT] 0000003f DSCBootstrapp E com.adobe.livecycle.bootstrap.bootstrappers.AbstractBoostrapper log TRAS0014I: 
The following exception was logged com.adobe.livecycle.bootstrap.BootstrapException: ALC-TTN-011-031: 
Bootstrapping failed for platform component [DocumentServiceContainer]. The wrapped exception's message reads: See nested exception; nested exception is: 
java.lang.Exception: java.lang.NoClassDefFoundError: com.adobe.livecycle.cache.adapter.GemfireCacheAdapter (initialization failure)
 at com.adobe.livecycle.bootstrap.bootstrappers.DSCBootstrapper.bootstrap(DSCBootstrapper.java:73)
 at com.adobe.livecycle.bootstrap.framework.ManualBootstrapInvoker.invoke(ManualBootstrapInvoker.java:78)
 at com.adobe.livecycle.bootstrap.framework.BootstrapServlet.doGet(BootstrapServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)

LCM may also display error message dialogs such as the following:

Reason

In a clustered environment, the cluster caching must be configured correctly and working before the database initialization can complete successfully.

Solution

The cluster caching should be configured using one of the options below, depending on whether you are using UDP or TCP caching:
A) UDP caching uses the following Java argument to set a port number: -Dadobe.cache.multicast-port=<port number>
The multicast port must be unique to the LiveCycle ES cluster (that is, the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> on all nodes in the LiveCycle ES cluster.

B) TCP caching uses the following Java argument: -Dadobe.cache.cluster-locators=<IPaddress>[<port number>],<IPaddress><port number>]
Configure, as a comma-separated list, the locators for all nodes of the cluster. The value for <IPaddress> is the IP address of the computer running the locator, and the value for <portnumber> is any unused port between 1 and 65535 (the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> for all locators.

Troubleshooting

Here are some further troubleshooting tips for LCM errors related to the DB initialization step:

  • ensure the DB privileges for the DB user match what is specified in the installation documentation
  • ensure sure the user that is starting the application server has R/W access to the GDS and LC TEMP directories (Bootstrap will fail if the permissions are incorrect)
  • it may be necessary to drop the DB and re-create it if there was an error the first time
  • if using WebSphere, test the DB connection from the WAS admin console
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (1 vote cast)

LiveCycle: NoClassDefFoundError: com/adobe/workflow/datatype/form/FormDataTypeInstanceImpl

Issue

After performing an upgrade from LC7 to ES 8.2.1 and then trying to run a process in the LC7 compatibility layer, the process instance may stall at a User component with the following exception in the server log:

java.lang.NoClassDefFoundError: com/adobe/workflow/datatype/form/FormDataTypeInstanceImpl
at com.adobe.workflow.qpac.user.UserService.execute(UserService.java:221)
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.asyncExecuteActionCommand(adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.java:2153)
at com.adobe.workflow.engine.ProcessCommandControllerBean.doOnMessage(ProcessCommandControllerBean.java:138)
at com.adobe.workflow.engine.ProcessCommandControllerBean.onMessage(ProcessCommandControllerBean.java:99)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3953)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Reason

The version of the User QPAC deployed in LC ES is not the updated version compatible with LC ES. It cannot interpret the lc7form variable type which is used in the LC7 compatibility layer when importing LC7 processes into ES.

Solution

Deploy the updated User QPAC available from:
LIVEYCYLE_HOME\configurationManager\plugins\upgrade-plugin\collateral

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