11:01 a.m.
Hi!
I am quite new to Drools and Drools Flow - please let me know if I am asking
something obvious here :)
I've implemented my custom WorkItemHandlers that are aware of the
KnowledgeSession. Now, I am trying to enable persistence to flows using
drools-persistence-jpa and drools-spring. Ideally, I wanted drools to start
and end transactions, but I wasn't able to achieve that (this is the
problem) and I have start/end transactions manually before
starting/aborting/signaling a process (i.e. running a process is a single
transaction -> if exception happens no state is persisted).
Problem: DroolsSpringTransactionManager has a flag localTransaction which is
set to true whenever a new transaction is started and transaction is
committed only if this flag is set to true. Now, if inside workItemHandler I
invoke a method on knowledgeSession, then my call is being delegated to
SingleSessionCommandService and it tries to start a transaction, but it sees
that there is a transaction already running and sets localTransaction flag
to false -> transaction never gets committed.
Am I doing something wrong here?
Thanks in advance!
Anton
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-persistence-spring-loca...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11:27 a.m.
Nobody uses Drools Flow with Spring?
According to svn Mark Proctor should be aware why/how this localTransaction
flag is used. Mark could you please comment?
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-persistence-spring-loca...
Sent from the Drools: User forum mailing list archive at Nabble.com.
4:17 a.m.
New subject: [Drools Flow 5.1] persistence + spring + localTransaction
hi,
i've put some notes on how to set it up in the below thread (have a look
on the last entries)
http://drools.46999.n3.nabble.com/Can-Drools-Flow-Persistence-Work-withou...
but be aware of the bug
http://drools.46999.n3.nabble.com/drools-flow-persistence-doesn-t-work-wi...
myslef, i gave up with drools flow+spring+jta. Because of the above
bug/missing code there is no way one could not risk leaving process in
inconsistent state when for instance using async tasks (e.g. JMS, user
task completed by Mina server commits database changes but if a crash
happens after db commit and before jms update you're going to have your
system in inconsistent state)
On 11/05/2011 17:27, anton.litvinenko wrote:
Nobody uses Drools Flow with Spring?
According to svn Mark Proctor should be aware why/how this localTransaction
flag is used. Mark could you please comment?
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-persistence-spring-loca...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Greg Stasica
PaceMetrics Ltd.
T +353 1 8849921
PaceMetrics Limited is registered in Ireland as a private company limited by shares,
Registration No. 298243, Registered office: PaceMetrics House, East Point Business
Park, Dublin 3. This e-mail may contain confidential, proprietary or privileged
information. If you are not the intended recipient (or have received this e-mail in error)
please destroy this e-mail and notify the sender immediately by telephoning +353 1
8184000. Any unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
2:16 p.m.
New subject: [Drools Flow 5.1] persistence + spring + localTransaction
Greg, were you able to achieve process persistence in other configurations?
(e.g. without spring?)
I don't use drools-spring bean factories to instantiate KnowledgeAgent and
KnoweldgeBase (instead i created alternative factories) + the following JPA
definition and spring context
persistence.xml:
<?xml version="1.0" encoding="UTF-8"
standalone="yes"?>
<persistence version="1.0"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd
http://java.sun.com/xml/ns/persistence/orm
http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
xmlns:orm="http://java.sun.com/xml/ns/persistence/orm"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/persistence">
<persistence-unit name="org.drools.persistence.jpa">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>org.drools.persistence.session.SessionInfo</class>
<class>org.drools.persistence.processinstance.ProcessInstanceInfo</class>
<class>org.drools.persistence.processinstance.ProcessInstanceEventInfo</class>
<class>org.drools.persistence.processinstance.WorkItemInfo</class>
<class>org.drools.persistence.processinstance.variabletypes.VariableInstanceInfo</class>
<class>org.drools.persistence.processinstance.variabletypes.SerializablePersistedVariable</class>
<class>org.drools.persistence.processinstance.variabletypes.JPAPersistedVariable</class>
<properties>
<property name="hibernate.dialect"
value="org.hibernate.dialect.PostgreSQLDialect"/>
<property name="hibernate.max_fetch_depth"
value="3"/>
<property name="hibernate.hbm2ddl.auto"
value="update"/>
<property name="hibernate.show_sql" value="true"/>
<property name="hibernate.connection.autocommit"
value="false"/>
</properties>
</persistence-unit>
</persistence>
ApplicationContext.xml:
<bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="dataSource" ref="dataSource"/>
<property name="loadTimeWeaver">
<bean
class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver"/>
</property>
</bean>
<jee:jndi-lookup id="dataSource"
jndi-name="jdbc/flowengine"/>
<bean id="transactionManager"
class="org.springframework.orm.jpa.JpaTransactionManager">
<constructor-arg type="javax.persistence.EntityManagerFactory"
ref="entityManagerFactory"/>
</bean>
<tx:annotation-driven transaction-manager="transactionManager"/>
This kinda works, but I have to start transaction manually before invoking
any method on Drools Flow. And of course if an exception happens during the
invocation then everything is rolled back (e.g. process with 3 steps and the
last step crashes then process state in database is not updated with 2 first
steps).
Is it possible to configure Drools Flow to start/commit transaction at
before/after process step?
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-persistence-spring-loca...
Sent from the Drools: User forum mailing list archive at Nabble.com.
4:43 a.m.
New subject: [Drools Flow 5.1] persistence + spring + localTransaction
hi,
sorry but i've never tried to use something else. My application uses
spring so there was no other option for me.
On 25/05/2011 20:16, anton.litvinenko wrote:
Greg, were you able to achieve process persistence in other
configurations?
(e.g. without spring?)
I don't use drools-spring bean factories to instantiate KnowledgeAgent and
KnoweldgeBase (instead i created alternative factories) + the following JPA
definition and spring context
persistence.xml:
<?xml version="1.0" encoding="UTF-8"
standalone="yes"?>
<persistence version="1.0"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd
http://java.sun.com/xml/ns/persistence/orm
http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
xmlns:orm="http://java.sun.com/xml/ns/persistence/orm"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/persistence">
<persistence-unit name="org.drools.persistence.jpa">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>org.drools.persistence.session.SessionInfo</class>
<class>org.drools.persistence.processinstance.ProcessInstanceInfo</class>
<class>org.drools.persistence.processinstance.ProcessInstanceEventInfo</class>
<class>org.drools.persistence.processinstance.WorkItemInfo</class>
<class>org.drools.persistence.processinstance.variabletypes.VariableInstanceInfo</class>
<class>org.drools.persistence.processinstance.variabletypes.SerializablePersistedVariable</class>
<class>org.drools.persistence.processinstance.variabletypes.JPAPersistedVariable</class>
<properties>
<property name="hibernate.dialect"
value="org.hibernate.dialect.PostgreSQLDialect"/>
<property name="hibernate.max_fetch_depth"
value="3"/>
<property name="hibernate.hbm2ddl.auto"
value="update"/>
<property name="hibernate.show_sql"
value="true"/>
<property name="hibernate.connection.autocommit"
value="false"/>
</properties>
</persistence-unit>
</persistence>
ApplicationContext.xml:
<bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="dataSource" ref="dataSource"/>
<property name="loadTimeWeaver">
<bean
class="org.springframework.instrument.classloading.InstrumentationLoadTimeWeaver"/>
</property>
</bean>
<jee:jndi-lookup id="dataSource"
jndi-name="jdbc/flowengine"/>
<bean id="transactionManager"
class="org.springframework.orm.jpa.JpaTransactionManager">
<constructor-arg type="javax.persistence.EntityManagerFactory"
ref="entityManagerFactory"/>
</bean>
<tx:annotation-driven transaction-manager="transactionManager"/>
This kinda works, but I have to start transaction manually before invoking
any method on Drools Flow. And of course if an exception happens during the
invocation then everything is rolled back (e.g. process with 3 steps and the
last step crashes then process state in database is not updated with 2 first
steps).
Is it possible to configure Drools Flow to start/commit transaction at
before/after process step?
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-Flow-5-1-persistence-spring-loca...
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
--
Greg Stasica
PaceMetrics Ltd.
T +353 1 8849921
PaceMetrics Limited is registered in Ireland as a private company limited by shares,
Registration No. 298243, Registered office: PaceMetrics House, East Point Business
Park, Dublin 3. This e-mail may contain confidential, proprietary or privileged
information. If you are not the intended recipient (or have received this e-mail in error)
please destroy this e-mail and notify the sender immediately by telephoning +353 1
8184000. Any unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
4728
days inactive
4757
days old
4 comments
2 participants
participants (2)
-
anton.litvinenko -
Greg Stasica