topic Strange behavior Deploy and Start Process in Alfresco Archive

Strange behavior Deploy and Start Process

pedrog1 — Tue, 29 May 2012 17:19:44 GMT

I'm having a strange behavior in my app.When I reboot my application do I have to redeploy the process definitions? It doesn't make any sense for me, but I try to explain why.Imagine I've just deployed Activiti. I start my application and upload a process definitionpublic void deployProcess(string r

Re: Strange behavior Deploy and Start Process

trademak — Fri, 01 Jun 2012 09:13:55 GMT

Hi,

Based on the information you provided I've no idea. Can you post your Activiti Engine config as well?
Can you tell a bit more about your environment and how you've deployed the Activiti Engine?

Best regards,

Re: Strange behavior Deploy and Start Process

cweber — Fri, 01 Jun 2012 11:03:51 GMT

I'm not sure but it seems to me as if you are using an in memory version of the database.

Did you use the config script out of the user guide?

If you have

 <property name="jdbcUrl" value="jdbc:h2:mem:activiti;DB_CLOSE_DELAY=1000" />

change it to the database you use.
If you are using the standard activiti setup (5.9) that should work for you.

<property name="jdbcUrl" value="jdbc:h2:tcp://localhost/activiti" />

Re: Strange behavior Deploy and Start Process

pedrog1 — Fri, 01 Jun 2012 12:00:32 GMT

Thank you for your replies

In my app I'm using Spring with Hibernate

my persistence.xml


(…)
 <persistence-unit name="WorkflowPU_3" transaction-type="JTA">
  <provider>org.hibernate.ejb.HibernatePersistence</provider>
  <jta-data-source>java:/comp/env/jdbc/WorkflowDB_3</jta-data-source>
  <exclude-unlisted-classes>true</exclude-unlisted-classes>
  <properties>
   <property name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect" />
   <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.BTMTransactionManagerLookup" />
   <property name="jta.UserTransaction" value="java:comp/UserTransaction" />
   <property name="javax.persistence.transactionType" value="jta" />
   <property name="hibernate.current_session_context_class" value="jta" />
   <property name="hibernate.archive.autodetection" value="none" />
   <property name="hibernate.cache.use_second_level_cache" value="false" />
   <property name="hibernate.query.plan_cache_max_strong_references" value="1024" />
   <property name="hibernate.query.plan_cache_max_soft_references" value="4096" />
   <property name="hibernate.connection.isolation" value="2" />
   <property name="hibernate.connection.release_mode" value="after_statement" />
  </properties>
 </persistence-unit>

my applicationcontext.xml


(…)
 <!– create BTM transaction manager –>
 <bean id="BitronixTransactionManager" factory-method="getTransactionManager" class="bitronix.tm.TransactionManagerServices" destroy-method="shutdown" />
 <!– Spring JtaTransactionManager –>
 <bean id="transactionManager" class="org.springframework.transaction.jta.JtaTransactionManager">
  <property name="transactionManager" ref="BitronixTransactionManager" />
  <property name="userTransaction" ref="BitronixTransactionManager" />
 </bean>

 <bean id="entityManagerFactory3" depends-on="BitronixTransactionManager" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
  <property name="persistenceUnitName" value="WorkflowPU_3" />
 </bean>

 <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
  <property name="databaseSchemaUpdate" value="true" />
  <property name="transactionManager" ref="transactionManager" />
  <property name="dataSourceJndiName" value="java:/comp/env/jdbc/WorkflowDB_3" />
  <property name="jpaEntityManagerFactory" ref="entityManagerFactory3" />
  <property name="jpaHandleTransaction" value="true" />
  <property name="jpaCloseEntityManager" value="false" />
  <property name="jobExecutorActivate" value="false" />
  <property name="transactionsExternallyManaged" value="true" /> 
  <property name="history" value="full" /> 
 </bean>

 <bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean">
  <property name="processEngineConfiguration" ref="processEngineConfiguration" />
 </bean>

Hope this helps. Thanks

Re: Strange behavior Deploy and Start Process

pedrog1 — Fri, 01 Jun 2012 17:46:07 GMT

I believe I've solved the problem.

I started using the StrongUuidGenerator and so far so good.

For the ones who might having this problem:


<bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
  (…)
  <property name="idGenerator">
         <bean class="org.activiti.engine.impl.persistence.StrongUuidGenerator" />
       </property>
      <property name="idBlockSize" value="2000" />
(…)
 </bean>

Remember to include java-uuid-generator-3.1.2.jar in your classpath

Regards