LiveCycle ES: NoSuchMethodError installing/uninstalling patches


If you are installing/uninstalling patches or service packs for LiveCycle ES you may encounter the following exception in the server log:

Caused by: javax.ejb.EJBException: Unexpected Error
java.lang.NoSuchMethodError: com.adobe.pof.omapi.POFQuery.addFilter(Ljava/lang/String;Ljava/lang/String;IJ)Lcom/adobe/pof/omapi/POFFilter;
    at com.adobe.idp.event.util.EventDBHelper.getNewAsynchEventIDs(
    at com.adobe.idp.event.notification.NotificationManagerImpl$2.doInTransaction(
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew(
    at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(
    at java.lang.reflect.Method.invoke(
    at org.jboss.invocation.Invocation.performCall(
    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(

This exception will usually occur following the EAR deployment.


When you install/uninstall patches for LiveCycle ES they will update files included in the EARs and also the DSC component files which are then deployed as services.  The versions of the EARs and components deployed must match, otherwise you will see this exception.  If the versions do not match, then the components may be referencing Java methods which were added/modified in the later patch, and therefore not available in the EARs or vice versa.

This exception will often occur directly after the updated EARs are deployed but the components have not yet been updated, as these are two separate steps in LCM.  Even after deploying the updated components the exception may still occur, as they are still loaded in the cache.


Ensure you have successfully completed deployment of the updated EARs and components.  If the error is still occurring, then restart your application server and perhaps even clean the application server temp files before restarting.  This should refresh all of the deployed services in the cache and the error should not occur.

reference: (182876692)

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