The figures (+300MB) you quote are frightening, and it would be *very*
interesting to learn what sort of rules causes this excessive amount
of heap usage. Could you post typical patterns - if they are
generated, there ought to be - and guestimates w.r,t, their relative
frequencies?
-W
On 3/30/10
WSHT saves a workItemID to the TASK table through the Mina client.
So what exactly should we copy from WSHT?
--
View this message in context:
http://n3.nabble.com/Drools-Flow-WORK-ITEM-ID-as-a-flow-variable-tp680939p687258.html
Sent from the Drools - User mailing list archive at Nabble.com.
___
I do not recommend that approach, I recommend to copy the same approach used
in the WSHT human task module. there is no need to clarify that Human Task
are only one of the possibilities for a wait state situation. But, WSHT
contains a good approach to achieve the same that you are looking for.. you
which component(s) should I look at?
I looked at "drools.process.workitem.wsht.*", but it is all Mina based, and
there is no answer to my question.
I wonder whether I should also persist it as a variable, and craft some
weird query to connect my business ID to the sessionID before I can reload
I have many entities that are related to the flow, and I am confident, I
should not make them aware of something as low level as the Drools Flow
"Process Instance ID".
The only approach I can think of so far is to have an aggregate root ID (
business ) persisted via Variable Persistence and craft
Long running process is not always a Human Task, that means the Task is not
always needed. Let's say we are waiting for the response from the external
system, and once response comes in, we would like to complete _this_ work
item.
Therefore we are looking to do this _without_ WS HT handler, and u
you can use the same approach used in the WSHT implementation.
Persist the work item Id related with the business activity that cause the
wait state.
In the Human task case, the work Item id is persisted in the node instance
(that is running) that causes the wait state
On Tue, Mar 30, 2010 at 4:4
hi again,
On 30 Mar 2010, at 18:32, Edson Tirelli wrote:
I am not sure I understand what you are doing when you say:
> Every X seconds I collect the available facts and call fireAllRules() +
dispose(), **always within the same session**.
(emphasis is mine)
i meant that i keep using the same
To be more precise, the specific directory "artifact" is giving a 404 even
though the rest of the build features appear to work. I also note that
recent builds have been failing.
jfl
--
View this message in context:
http://n3.nabble.com/Drools-Expert-5-OSGi-tp681546p686875.html
Sent from the D
yes, I understand they are persisted, but once you reload a session, you have
no knowledge of _which_ Processs Instance to use, and _which_ Work Item is
the one that caused the flow to wait.
Therefore I am looking for the way to save a workitem ID as a variablea,
using a Variable Persistence mech
ProcessInstanceID and WorkItemID are both persisted, and you can find the
information about them inside the Drools Flow tables.
On Tue, Mar 30, 2010 at 2:45 PM, tolitius wrote:
>
> well, we both know that there is no support from Red Hat.
>
> Red Hat does not support Drools Flow.
>
> so let me
the processInstanceId is very related with the business information that you
store about the business entity that you want to process.
If you are designing the solution, you must propose where do you want to
store it. I don't know your business entities so I cannot suggest where to
store that infor
Hi,
I'm a computer science student and am writing the related-work part for
my diploma thesis and would be interested in (scientific) papers or
information about refactoring or transformation possibilities which can
be done with drools / jboss rules. I have to admit that I never worked
with one
Hi,
I'm a computer science student and am writing the related-work part for
my diploma thesis and would be interested in (scientific) papers or
information about refactoring or transformation possibilities which can
be done with drools / jboss rules. I have to admit that I never worked
with one
ok, let me be more specific.
Wait state is reached (request is sent to an external system), the flow is
persisted, the thread that persisted the flow is gone.
Now, the response came back from the external system, and now would be a
good time to resume the flow (reload the session):
StatefulKnow
well, we both know that there is no support from Red Hat.
Red Hat does not support Drools Flow.
so let me try this again.. having a workitem, what would be the best
approach to persist a WorkItemID using VariablePersistence?
( In fact I think that it should be a framework concern to persist
Pro
Hi Edson,
Many thanks for taking the time to respond. I think I should be able to
develop something using
the controlled clock approach outlined below.
Thanks again, and keep up the great work!
Best Regards,
Paul
2010/3/30 Edson Tirelli
>
>Hi Paul,
>
>Unfortunately, the bottom lin
I am not sure I understand what you are doing when you say:
> Every X seconds I collect the available facts and call fireAllRules() +
dispose(), **always within the same session**.
(emphasis is mine)
Compilation indeed uses more memory, but you can compile once and reuse
the kbase. Also, if
Did you see how is that solved in the WHST module?
You can copy that if you want.
2010/3/30 tolitius
> Wait state is reached (request is sent to an external system), the flow is
> persisted, the thread that persisted the flow is gone.
>
> Now, the response came back from the external system, and
hudson.jboss.org is still down; are there mirrors elsewhere ?
Thanks,
Jean-François Lamy
On Sun, Mar 28, 2010 at 11:38 AM, Mark Proctor wrote:
> On 28/03/2010 16:05, jflamy wrote:
> > I want to manage Drools Expert rules with Drools Guvnor. My
> understanding is
> > that requires the use of Dro
You can store the processInstanceId in your http session, in some business
entity, depending on your situation there are myriad of ways of doing that.
On Tue, Mar 30, 2010 at 12:30 PM, tolitius wrote:
>
> StatefulKnowledgeSession ksession =
> JPAKnowledgeService.loadStatefulKnowledgeSession( ses
I've narrowed it down to a smaller example. The order of insertion seems to
trump the rule salience.
The following rule inserts 4 objects. Inserted as A4,A3,A2,A1 the rules
sequence is unexpected. Inserted A1,A3,A4,A2 they fire as expected.
rule "setup.two"
when
then
> // generates out of sal
Hi Anatoly,
Please remember that this is a free service, that the community gives to the
project users. Remember also that you can always get support for different
people from the community or from red hat.
If you have test cases running please feel free to share that projects with
us, and we will
Hi Paul,
Unfortunately, the bottom line is that there is no magic. Time windows
are always based on the concept of "current time" and to be able to join
different streams of events Drools took the decision of having a
session-scoped clock.
The major problem of a fact timestamp be in the
Wait state is reached (request is sent to an external system), the flow is
persisted, the thread that persisted the flow is gone.
Now, the response came back from the external system, and now would be a
good time to resume the flow (reload the session):
StatefulKnowledgeSession ksession =
JPAKn
Hey all
First of all, I am sorry if I haven't answered many of the e-mails lately
in the list (although I am glad that more and more users are stepping up and
helping others). The reason was we were really busy developing a major
improvement to the Drools algorithm during the last few months
StatefulKnowledgeSession ksession =
JPAKnowledgeService.loadStatefulKnowledgeSession( sessionId, kbase, null,
env );
Now, having a "ksession", how do I get to the right PROCESS_INSTANCE_ID, so
I can ksession.getProcessInstance()?
Thank you,
/Anatoly
--
View this message in context:
http://n3.
seems like this user list works as some others.. two days old post don't get
looked at
so let me try this again.. having a workitem, what would be the best
approach to persist a WorkItemID using VariablePersistence?
( In fact I think that it should be a framework concern to persist
ProcessInstan
Probably you have checked this, but just to make sure:
If you omit rule "a1": does fact A2 fire with rule "a2" at salience 65?
What does "...rules are like the following..." mean? I guess they are
not identical, that would be pointless. So, in which way do they differ?
-W
On Tue, Mar 30, 2010 a
We have 5 rules that are firing out of salience order for a particular set
of 4 objects. The rules have a branch on the RHS which sometimes retracts
the A object. There are reasons why the branch is not in the LHS not shown
in this sample.
The 5 rules are like the following. The salience values
hi all,
I'm quite new to the drools rule engine and i've been using it for a project
where i need to filter events and execute actions accordingly.
I'm currently running a DRL file and creating a stateful session from it, and
then running 2/3 facts every time. Every X seconds I collect the avai
Guided Rule validation fails in Guvnor (Internet Explorer only), when Guided
rule contains DSL components.
It looks as though the LHS of the DSL isn't being substituted with the RHS
when validating.
I can't find a JIRA for this, does anybody know whether it's fixed in 5.1
M1?
Thanks and Regards,
Hi All,
I am trying to change the persistence of the HumanTaskService from the in
memory database to Oracle and I am having the below errors if some one can
help. I have posted my persistence,xml and the Error that I am having.
Persistence.xml
---
http://java.sun.com/xml/ns/pers
Hi all,
In the documentation and other articles I reed about the Fault Node,
and how it acts as a bit of an End Node in Flow.
I've been searching on the net in general, and the mail-list archive
in particular for an example on how to use this, but without much
success.
In mostly interessted in t
34 matches
Mail list logo
