Has anyone encountered this problem before? The scenario is this:
The application we have is running LiveCycle ES2 v9.0 on IBM Websphere server and we are using LiveCycle Workbench 9.0 to create/deploy/undeploy processes.
The problem is after we deploy/undeploy an application a few times, we eventually end up with a workbench error of "Internal Error" or "Not serializable". This wouldn't be too much of a concern if we could delete the application, but we can't because the application is still deployed!
However, we can create a new minor version of that "stuck" application, and this new version can deployed and undeployed. However, eventually this application version will become corrupt like the previous version, and we won't be able to deploy/undeploy or delete...
Trying to undeploy and remove in AdminUI will fail as well - "Failed to undeploy <application name>, check the error log for details"
The snippet of the error log is as follows:
The error message from the server is as follow
[6/22/11 13:46:12:853 CDT] 000000b0 ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "doSupports" on bean "BeanId(LiveCycleES2#adobe-dscf.jar#EjbTransactionCMTAdapter, null)". Exception data: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
Caused by: com.adobe.idp.applicationmanager.application.ApplicationConfigurationNotFoundException: Application configuration with name: APPVS major version:2 minor version 1 does not exist.
... 114 more
The logfile from workbench is as follows:
LC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
Caused by: ALC-DSC-005-000: com.adobe.idp.dsc.DSCNotSerializableException: Not Serializable
Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
Caused by: com.ibm.websphere.csi.CSITransactionRolledbackException: Transaction marked rollbackonly
Any help/advice is greatly appreciated. Thanks!
I've been getting the same issue on JBOSS based system.
Read somewhere that Adobe does not recommend more than 50 resources per project.
Since keeping the number of resources in my projects below 50 i've incountered the error much less...
Thanks for the reply, odin836.
In case anyone encounters this down the road, we ended up reaching out to Adobe and, although they couldn't reproduce it, came back to us with a bunch of SQL's to clean up our applications in the LiveCycle db.
Since then, we've kept undeploying/deploying to a minimum and opt'd to delete and import instead - a bit of a hassle, but better than that error.