topic Re: activiti-osgi classloader issue in Alfresco Archive

activiti-osgi classloader issue

workflowuser2 — Tue, 17 Jul 2012 19:03:17 GMT

Hi,I have two bundles : activiti-osgi-karaf: configures and starts process engine (depends on activiti-osgi)activiti-osgi-process: contains process.bpmn20.xml, java delegates, process-request beanreference: activiti-in-action book. java delegates are binded into osgi container as serviceprocess-requ

Re: activiti-osgi classloader issue

frederikherema1 — Wed, 18 Jul 2012 06:15:55 GMT

Make sure your ProcessRequestBean implements Serializable. If it's a simple service-task, the process is not persisted and the POJO is still in memory (variable values are cached). Once you have an async, it's serialized to DB and when job-executor does the async work, it's de-serialized again when needed…

If you did implement Serializable, it's indeed an issue with classloading in the job-executor… Can you debug to see what's causing the " org.activiti.engine.ActivitiException: coudn't deserialize object in variable 'request'" in the first place?

Re: activiti-osgi classloader issue

workflowuser2 — Wed, 18 Jul 2012 17:56:27 GMT

Make sure your ProcessRequestBean implements Serializable. If it's a simple service-task, the process is not persisted and the POJO is still in memory (variable values are cached). Once you have an async, it's serialized to DB and when job-executor does the async work, it's de-serialized again when needed…

If you did implement Serializable, it's indeed an issue with classloading in the job-executor… Can you debug to see what's causing the " org.activiti.engine.ActivitiException: coudn't deserialize object in variable 'request'" in the first place?

frederikheremans

ProcessRequestBean does implements Serializable.
When I debugged, the issue appears to be de-serializing the ProcessRequestBean bytes from the db.

It appears to be classloader issue. ProcessRequestBean classloader, is perhaps, not available in the activiti-osgi-karaf bundle.

Do you think the following may help?
http://forums.activiti.org/en/viewtopic.php?f=4&t=1433&start=0

Re: activiti-osgi classloader issue

frederikherema1 — Thu, 19 Jul 2012 07:03:33 GMT

You should try that approach, indeed (setting the class loader).

Re: activiti-osgi classloader issue

workflowuser2 — Sat, 21 Jul 2012 04:43:25 GMT

Hi frederikheremans,

I further looked into this issue and it appears that it might be related to OSGi bundling of activiti-engine.
activiti engine need to allow importing client packages in addition to its own dependencies.

Since these packages/classes are not known during activiti-engine bundle/build time, the MANIFEST.MF file should contain something like below:
DynamicImport-Package: *

I looked at libraries similar to activiti and they use the same mechanism to allow loading client packages.

Let me know your thought and if you want me to test/work on this while I am working on other osgi issues.

activiti newbie

You should try that approach, indeed (setting the class loader).

Re: activiti-osgi classloader issue

frederikherema1 — Mon, 23 Jul 2012 06:40:53 GMT

Yes, this would be good to work on and test to allow cross-bundle imports, not know at build-time.

Re: activiti-osgi classloader issue

rahulkrs — Sun, 06 Oct 2013 20:42:18 GMT

Did you able to solve this problem? I also got in to a similar issue , when JobExecutor is trying to access the service task which is deployed in a different bundle. I am getting a class not found exception.