dispose sessions in PerProcessInstanceRuntimeManager
by Jeffrey Bride
Hi.
I'm doing a deep dive into the new jbpm6 PerProcessInstanceRuntimeManager functionality.
Impressive.
One minor observation is that it seems that both the engine.getKieSession().destroy(); and disposeRuntimeEngine(engine); function calls in the init() function are redundant.
Neither of these calls seem necessary.
Previous to these function calls, an instance of DisposeSessionTransactionSynchronization() was already registered .... which takes care of appropriately disposing the session after the JTA transaction has committed.
Subsequently, when either (or both) of these redundant calls to close the session prior to the transaction has committed, the following exception occurs:
java.lang.IllegalStateException: Illegal method call. This session was previously disposed.
at org.drools.core.reteoo.DisposedReteooWorkingMemory.getProcessRuntime(DisposedReteooWorkingMemory.java:262) [drools-core-6.1.0-SNAPSHOT.jar:6.1.0-SNAPSHOT]
at org.drools.core.impl.StatefulKnowledgeSessionImpl.getProcessRuntime(StatefulKnowledgeSessionImpl.java:868) [drools-core-6.1.0-SNAPSHOT.jar:6.1.0-SNAPSHOT]
at org.drools.persistence.SingleSessionCommandService$SynchronizationImpl.afterCompletion(SingleSessionCommandService.java:504) [drools-persistence-jpa-6.1.0-SNAPSHOT.jar:6.1.0-SNAPSHOT]
at org.drools.persistence.jta.JtaTransactionSynchronizationAdapter.afterCompletion(JtaTransactionSynchronizationAdapter.java:22) [drools-persistence-jpa-6.1.0-SNAPSHOT.jar:6.1.0-SNAPSHOT]
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:402)
I'm testing in an EAP6.1 environment using JTA transactions provided by the app server.
commenting out those apparently redundant function calls does not seem to cause any other negative side effects and the session is still closed by the DisposeSessionTransactionSynchronization instance.
jeff
--
Jeffrey Bride
Senior Principal Solution Architect
Global Partner Enablement
Red Hat (www.redhat.com)
cell: 303.523.7885
13 years, 1 month
jBPM user
by houshengkun＠gmail.com
Hi,
I want to ask a question. I am a J2EE developer from China. Recently, I need to develop a process designer. It will be used in the web pages to design a workflow(maybe the workflow contains a sub-process), but I have difficulties to develop my own process designer, so I want to do the secondary development based on jBPM. I dont know whether it can finish this work?
houshengkun(a)gmail.com
13 years, 1 month
JBPM Eclipse
by nag raj
Hi There,
I have downloaded JBPM from http://sourceforge.net/projects/jbpm/files/ link. But unfortunately the eclipse link in build.xml is broken can you update the build.xml please.
Between I can only use helios to work with JBPM 5.4 is it?
Thank you.
Regards
Raj
"The difficult I can do today. The impossible will take a little longer." (Billie Holiday)
13 years, 1 month
Re: [jbpm-dev] [rules-dev] IMPORTANT: droolsjbpm-parent is dead, long live kie-parent-metadata and kie-parent-with-dependencies
by Geoffrey De Smet
To show how it all fits together, here's a visual image.
Ignore the jboss-integration-platform-bom part - that's not there yet).
On 02-08-13 12:07, Geoffrey De Smet wrote:
> Hi guys,
>
> *Please read this, especially the bold parts.*
>
> We've created user-facing boms: drools-bom, jbpm-bom, optaplanner-bom,
> guvnor-bom and kie-bom.
> This way, users can do:
>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.drools</groupId>
> <artifactId>drools-bom</artifactId>
> <type>pom</type>
> <version>6.0.0.Final</version>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> ...
> <dependencies>
> <dependency>
> <groupId>org.drools</groupId>
> <artifactId>drools-compiler</artifactId><!-- No version needed
> :) -->
> <dependency>
> <dependency>
> <groupId>org.drools</groupId>
> <artifactId>drools-decisiontables</artifactId><!-- No version needed
> :) -->
> <dependency>
> </dependencies>
>
> *1) When you create a new module in any kie repository (for example
> jbpm-foo),
> instead of adding an entry in droolsjbpm-build-bootstrap,
> now add an entry in the appropriate bom file.
> *- The bom files are in the git repo droolsjbpm-build-bootstrap.
> - The new module's groupId determines its bom file:
> -- groupId org.kie => kie-bom
> -- groupId org.drools => drools-bom
> -- groupId org.optaplanner => optaplanner-bom
> -- groupId org.jbpm => jbpm-bom
> -- groupId org.guvnor => guvnor-bom
> - Normally you 'll add 2-3 entries: normal, classifier sources and
> classifier test-jar
> For example: modules in drools-bom:
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/droo...
>
> *2) When you add a new external dependency (for example
> richfaces-core) or update/delete an existing one,**
> **instead of changing droolsjbpm-build-bootstrap,**
> **now change the pom file **kie-parent-with-dependencies*
> - the bom files do not extend kie-parent-with-dependencies, but
> kie-parent-with-dependencies imports the bom files
> - kie-parent-with-dependencies is in a subdirectory of git repository
> droolsjbpm-build-bootstrap
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/kie-...
> - kie-parent-with-dependencies holds a properties list of all versions
> and the dependencyManagement section
> -- Note: the ongoing platform bom work will affect this, but I 'll
> explain that in a new mail when it's done.
> - All new repo's root poms should extend kie-parent-with-dependencies
> (NOT kie-parent-metadata)
> *- Reminder (long time standing rule): No poms except for
> kie-parent-with-dependencies should mention versions of dependencies*
> -- Some modules violate this and might run into issues during
> productization when their dependency versions don't align with the rest.
>
> *3) When you add/change/delete a build plugin or any other metadata
> (anything except dependencies),**
> ****instead of changing droolsjbpm-build-bootstrap,**
> ****now change the pom file **kie-parent-metadata*
> - the bom files do extends kie-parent-metadata.
> - kie-parent-with-dependencies extends kie-parent-metadata - so
> effectively everything extends kie-parent-metadata
> - kie-parent-metadata is in the root of git repository
> droolsjbpm-build-bootstrap
> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom.xml
>
> Questions, suggestions, feedback: let me know.
>
> The repo droolsjbpm-build-bootstrap's restructure is now finished -
> feel free to make changes there again.
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
13 years, 1 month
Fwd: [rules-dev] IMPORTANT: droolsjbpm-parent is dead, long live kie-parent-metadata and kie-parent-with-dependencies
by Mauricio Salatino
Hi guys,
*Please read this, especially the bold parts.*
We've created user-facing boms: drools-bom, jbpm-bom, optaplanner-bom,
guvnor-bom and kie-bom.
This way, users can do:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-bom</artifactId>
<type>pom</type>
<version>6.0.0.Final</version>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
...
<dependencies>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-compiler</artifactId><!-- No version needed :) -->
<dependency>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-decisiontables</artifactId><!-- No version needed
:) -->
<dependency>
</dependencies>
*1) When you create a new module in any kie repository (for example
jbpm-foo),
instead of adding an entry in droolsjbpm-build-bootstrap,
now add an entry in the appropriate bom file.
*- The bom files are in the git repo droolsjbpm-build-bootstrap.
- The new module's groupId determines its bom file:
-- groupId org.kie => kie-bom
-- groupId org.drools => drools-bom
-- groupId org.optaplanner => optaplanner-bom
-- groupId org.jbpm => jbpm-bom
-- groupId org.guvnor => guvnor-bom
- Normally you 'll add 2-3 entries: normal, classifier sources and
classifier test-jar
For example: modules in drools-bom:
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/droo...
*2) When you add a new external dependency (for example richfaces-core) or
update/delete an existing one,**
**instead of changing droolsjbpm-build-bootstrap,**
**now change the pom file **kie-parent-with-dependencies*
- the bom files do not extend kie-parent-with-dependencies, but
kie-parent-with-dependencies imports the bom files
- kie-parent-with-dependencies is in a subdirectory of git repository
droolsjbpm-build-bootstrap
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/kie-...
- kie-parent-with-dependencies holds a properties list of all versions and
the dependencyManagement section
-- Note: the ongoing platform bom work will affect this, but I 'll explain
that in a new mail when it's done.
- All new repo's root poms should extend kie-parent-with-dependencies (NOT
kie-parent-metadata)
*- Reminder (long time standing rule): No poms except for
kie-parent-with-dependencies should mention versions of dependencies*
-- Some modules violate this and might run into issues during
productization when their dependency versions don't align with the rest.
*3) When you add/change/delete a build plugin or any other metadata
(anything except dependencies),**
** **instead of changing droolsjbpm-build-bootstrap,**
** **now change the pom file **kie-parent-metadata*
- the bom files do extends kie-parent-metadata.
- kie-parent-with-dependencies extends kie-parent-metadata - so effectively
everything extends kie-parent-metadata
- kie-parent-metadata is in the root of git repository
droolsjbpm-build-bootstrap
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom.xml
Questions, suggestions, feedback: let me know.
The repo droolsjbpm-build-bootstrap's restructure is now finished - feel
free to make changes there again.
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
--
- MyJourney @ http://salaboy.com <http://salaboy.wordpress.com>
- Co-Founder @ http://www.jugargentina.org
- Co-Founder @ http://www.jbug.com.ar
- Salatino "Salaboy" Mauricio -
13 years, 1 month
