Activiti within OSGi: Classloader issues after bundle update

bpaas — Fri, 04 May 2012 12:06:24 GMT

Hi everyone,We are building a process-driven web application based on OSGi. We were hoping to make use of OSGi's hot deployment capabilities to update different parts of our system independently without having to restart the server.Unfortunately, that's when we run into problems. Once we update bund

Re: Activiti within OSGi: Classloader issues after bundle update

bpaas — Mon, 07 May 2012 13:10:38 GMT

I will try to be a little more specific with what is going on based on my understanding. Upon the initial server startup, we build a first engine instance using processEngineConfiguration.buildProcessEngine(). Everything is working fine subsequently until we update the bundle. Despite calling ProcessEngines.destroy() beforehand, we receive the above mentioned error. It seems to originate from attempted casts from objects loaded by the first bundle to objects loaded by the second bundle - failing because of different classloaders.

Thus, I would like to ask for a hint on how to destroy all objects/close all sessions by Activiti so that everything will be loaded by the new classloader again. I called ProcessEngines.init() for example and it told me that "ProcessEngines" were already initialized - despite ProcessEngines.destroy()?!

Thanks!

topic Re: Activiti within OSGi: Classloader issues after bundle update in Alfresco Archive

Activiti within OSGi: Classloader issues after bundle update

Re: Activiti within OSGi: Classloader issues after bundle update