Adobe enterprise product blog | David McMahon

Issue

The exception below occurs when using a custom component (DSC) in LiveCycle ES 8.2.1 designed to extend the functionality provided by the services from Adobe. The component includes the TaskManager DSC JAR file.

####<09-Jul-2010 15:04:21 o'clock CEST> <Error> <com.adobe.workflow.AWS> <PI> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> 
<<anonymous>> <BEA1-2CB96822045F171B0B4D> <> <1278680661381> <000000> <stalling action-instance: 2101 with message: Cannot coerce object: 
com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo@33142fb of type: com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo to type: 
class com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo:

ALC-DSC-119-000: com.adobe.idp.dsc.util.InvalidCoercionException: Cannot coerce object: com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo@33142fb of type: 
com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo to type: class com.adobe.idp.taskmanager.dsc.userservice.UserServiceInfo
at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:1047)
at com.adobe.workflow.datatype.CoercionUtil.toType(CoercionUtil.java:168)
at com.adobe.workflow.engine.PEUtil.processMapping(PEUtil.java:968)
at com.adobe.workflow.engine.PEUtil.invokeAction(PEUtil.java:666)
at com.adobe.workflow.engine.SynchronousBranch.handleInvokeAction(SynchronousBranch.java:466)
at com.adobe.workflow.engine.SynchronousBranch.execute(SynchronousBranch.java:863)
at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBean.java:2773)
at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncInvokeProcessCommand(ProcessEngineBMTBean.java:704)
at com.adobe.workflow.engine.adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.asyncInvokeProcessCommand(adobe_ProcessEngineBMTEJB_e5zjcz_ELOImpl.java:1697)
at com.adobe.workflow.engine.ProcessCommandControllerBean.doOnMessage(ProcessCommandControllerBean.java:156)
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:4072)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:3962)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
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

This error occurs when you include the TaskManager DSC JAR in your component. The TaskManager DSC (that is, the service itself) is not meant for use as a library.

Solution

Remove the TaskManager JAR from your component and use the libraries provided with the SDK. Or, extract any required classes from the DSC JAR and include them in your component.

reference (181617740/2660587)