upgrade from 5.16.0 to 5.17.0 - processes no longer deployed

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

billdoor

Hello,

i recently attempted to upgrade a project from activiti 5.16.0 to 5.17.0.

running 5.16 my setup was as follows:

i had a custom class to create my processengine:

public class ProcessengineConfiguration implements ProcessEngineLookup {
    public ProcessEngine getProcessEngine() {
        CdiJtaProcessEngineConfiguration processEngineConfiguration = new CdiJtaProcessEngineConfiguration();
      
   processEngineConfiguration.setProcessEngineName("default");
   processEngineConfiguration.setDataSourceJndiName("java:/datasources/activitiDB");
   processEngineConfiguration.setTransactionManager(lookupTransactionManager());
   processEngineConfiguration.setDatabaseType("mssql");
   processEngineConfiguration.setTransactionsExternallyManaged(true);
   processEngineConfiguration.setJobExecutorActivate(true);
   processEngine = processEngineConfiguration.buildProcessEngine();   
   return processEngine;
   }
}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

and a

org.activiti.cdi.spi.ProcessEngineLookup‍

file, containing the fully qualified name of my Lookupclass above.


My Processes are stored in p_name.bpmn20.xml files on the classpath - the whole structre looks like this:

<blockcode>
main.ear/
    lib/activiti-[engine, cdi, spring, bpmn-model, bpmn-converter, process-validation, image-generator]-5.17.0.jar
    sub.war/
        WEB-INF/classes/p_name.bpmn20.xml
    sub.jar/
        /META-INF/services/org.activiti.cdi.spi.ProcessEngineLookup
        /com/package/ProcessengineConfiguration.class
</blockcode>
       
this worked just fine unter 5.16.0 - resulting in the following deployment log:
<blockcode>
2015-05-12 16:42:26,223 INFO  [org.jboss.resteasy.plugins.validation.AbstractValidatorContextResolver] (MSC service thread 1-1) Unable to find CDI supporting ValidatorFactory. Using default ValidatorFactory
2015-05-12 16:42:26,447 INFO  [org.activiti.cdi.impl.ActivitiExtension] (MSC service thread 1-1) Initializing activiti-cdi.
2015-05-12 16:42:26,504 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found

2015-05-12 16:42:27,391 INFO  [org.activiti.engine.impl.ProcessEngineImpl] (MSC service thread 1-1) ProcessEngine default created
2015-05-12 16:42:27,394 INFO  [org.activiti.engine.impl.jobexecutor.JobExecutor] (MSC service thread 1-1) Starting up the JobExecutor[org.activiti.engine.impl.jobexecutor.DefaultJobExecutor].
2015-05-12 16:42:27,398 INFO  [org.activiti.engine.impl.jobexecutor.AcquireJobsRunnable] (Thread-66) JobExecutor[org.activiti.engine.impl.jobexecutor.DefaultJobExecutor] starting to acquire jobs
2015-05-12 16:42:27,696 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-1) Deploying javax.ws.rs.core.Application: class com.company.activiti.rest.Resources.RootApplication
2015-05-12 16:42:27,781 INFO  [org.activiti.engine.impl.bpmn.deployer.BpmnDeployer] (pool-6-thread-1) Processing resource p_name.bpmn20.xml
2015-05-12 16:42:27,795 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /myapp
</blockcode>

main line i want to point out beeing:
2015-05-12 16:42:27,781 … Processing resource p_name.bpmn20.xml


Today i took the project, and replaced "5.16" with "5.17.0" in my buildfiles, where activiti was mentioned.

my logs now look like this:

<blockcode>
2015-05-18 15:05:35,160 INFO  [org.activiti.cdi.impl.ActivitiExtension] (MSC service thread 1-6) Initializing activiti-cdi.
2015-05-18 15:05:35,209 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found

2015-05-18 15:05:35,759 INFO  [org.activiti.engine.impl.ProcessEngineImpl] (MSC service thread 1-6) ProcessEngine default created
2015-05-18 15:05:35,762 INFO  [org.activiti.engine.impl.jobexecutor.JobExecutor] (MSC service thread 1-6) Starting up the JobExecutor[org.activiti.engine.impl.jobexecutor.DefaultJobExecutor].
2015-05-18 15:05:35,766 INFO  [org.activiti.engine.impl.jobexecutor.AcquireJobsRunnableImpl] (Thread-139) JobExecutor[org.activiti.engine.impl.jobexecutor.DefaultJobExecutor] starting to acquire jobs
2015-05-18 15:05:35,824 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-2) Deploying javax.ws.rs.core.Application: class com.company.activiti.rest.Resources.RootApplication
2015-05-18 15:05:35,846 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017534: Registered web context: /myapp
</blockcode>

Beeing identical, except for the part where activiti deploys the processdefinitions.


I went through my git logs and am sure i changes nothing that would affect this procedure. What changed in 5.17.0 that causes this to stop working?


Thanks in advance for your help!

jbarrez

Hmm no real idea im sorry. Nothin has changed in the CDI code from 5.16 -> 5.17