nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

ACT_RU_TASK table cleaned after new Activiti war file deploy !

gi00vani_kun

Hello,

I have a strange problem :
- on my local environment (oracle 11g xe) when ever I deploy a new WAR file all the previous task created are being erased from the database (ACT_RU_TASK) table
- on my development environment it's pretty much the same the super admin (kermit) comes and complete the tasks (some one invalidates the tasks ) upon deploying a new WAR file.

Is there a setting somewhere that does this ? I need to stop this from happening

Find more posts tagged with

Comments

jbarrez

What is your setting for the databaseSchemaUpdate? Does it recreate the schema on each deploy?

> the super admin (kermit) comes and complete the tasks (some one invalidates the tasks ) upon deploying a new WAR file

That sounds very strange. Can you describe exactly what you see, this is kinda vague.

gi00vani_kun

Hi,
Thank you for answering !
here is what I have in org.activiti.explorer.conf.ActivitiEngineConfiguration

<code>
@Bean(name = { "processEngineConfiguration" })
    public ProcessEngineConfigurationImpl processEngineConfiguration() {
        SpringProcessEngineConfiguration processEngineConfiguration = new SpringProcessEngineConfiguration();
        processEngineConfiguration.setDataSource(dataSource());
//        processEngineConfiguration.setDatabaseSchemaUpdate(environment
//                .getProperty("engine.schema.update", "false"));

        processEngineConfiguration
                .setTransactionManager(annotationDrivenTransactionManager());
        processEngineConfiguration.setJobExecutorActivate(Boolean
                .valueOf(
                        environment.getProperty("engine.activate.jobexecutor",
                                "false")).booleanValue());

        processEngineConfiguration.setHistory(environment.getProperty(
                "engine.history.level", "full"));

        List<AbstractFormType> formTypes = new ArrayList<AbstractFormType>();
        formTypes.add(new UserFormType());
        formTypes.add(new ProcessDefinitionFormType());
        formTypes.add(new MonthFormType());

        formTypes.add(new GridFormType());

        processEngineConfiguration.setCustomFormTypes(formTypes);
        return processEngineConfiguration;
    }
</code>

I've tried just now both versions
1)
<code>//        processEngineConfiguration.setDatabaseSchemaUpdate(environment
//                .getProperty("engine.schema.update", "false"));
</code>

2)
<code>       processEngineConfiguration.setDatabaseSchemaUpdate(environment
                  .getProperty("engine.schema.update", "false"));
</code>

I can also see that in Processengineconfiguration the default is :
<code>protected String databaseShemaUpdate ="false"; </code>

For the development server I'm not working on that server right now if I'll hit the problem again I'll let you know !

trademak

databaseSchemaUpdate set to true or false should never delete any data from the database.
Only create-drop would do this.

Best regards,

gi00vani_kun

Indeed databaseSchemaUpdate set to true or false does not delete data from the database.

I've fixed the issue by upgrading activiti from 5.16.4 to 5.17

Cheers