5:04 p.m.
I have already mentioned this issue previously here (see
http://n3.nabble.com/Mvel-and-multithreading-td50133.html)
Maybe I have described the problem not detailed enough.
We are using Drools version 5.0.1 and have a concrete problem with it in our production
environment. Our customer looks already interrogative at the developer team and have
"questions" about drools... please help! :)
Let us assume a multithreaded application, that tries to initialise & start several
processes using a StatefulKnowledgeSession in order to use in these processes rule flow.
The flow in all the processes is the same but every process instance must have an own
StatefulKnowledgeSession instance because of stateful session.
Actually the problem:
At the initializing phase occurs an org.mvel2.CompileException exception from time to time
at KnowledgeBuilder.add(...):
Exception in thread "Thread-60" [Error: incomplete statement: (possible use of
reserved keyword as identifier: )]
[Near : {... globals != empt ....}]
^
[Line: 0, Column: 0]
at
org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:153)
at org.mvel2.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:44)
at org.mvel2.MVEL.eval(MVEL.java:514)
at org.mvel2.templates.res.IfNode.eval(IfNode.java:61)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.TerminalNode.eval(TerminalNode.java:39)
at org.mvel2.templates.res.ForEachNode.eval(ForEachNode.java:116)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.TerminalNode.eval(TerminalNode.java:39)
at org.mvel2.templates.res.IfNode.eval(IfNode.java:64)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.ExpressionNode.eval(ExpressionNode.java:53)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:195)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:190)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:180)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:169)
at
org.drools.rule.builder.dialect.java.AbstractJavaRuleBuilder.generatTemplates(AbstractJavaRuleBuilder.java:126)
at
org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:128)
at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:86)
at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:1159)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:649)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:290)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:488)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25)
at com.myfirm.RuleFlowProcess.init(RuleFlowProcess.java:25)
at com.myfirm.RuleFlowProcess.clone(RuleFlowProcess.java:53)
at com.myfirm.ThreadTest$CloneThread.run(ThreadTest.java:35)
Caused by: java.lang.NullPointerException
at
org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:113)
... 27 more
Exception in thread "Thread-72" [Error: incomplete statement: (possible use of
reserved keyword as identifier: )]
[Near : {... declarations != empt ....}]
^
[Line: 0, Column: 0]
at
org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:153)
at org.mvel2.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:44)
at org.mvel2.MVEL.eval(MVEL.java:514)
at org.mvel2.templates.res.IfNode.eval(IfNode.java:61)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.ExpressionNode.eval(ExpressionNode.java:53)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.ExpressionNode.eval(ExpressionNode.java:53)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.TerminalNode.eval(TerminalNode.java:39)
at org.mvel2.templates.res.ForEachNode.eval(ForEachNode.java:116)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.TerminalNode.eval(TerminalNode.java:39)
at org.mvel2.templates.res.ForEachNode.eval(ForEachNode.java:116)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.ExpressionNode.eval(ExpressionNode.java:53)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.res.ExpressionNode.eval(ExpressionNode.java:53)
at org.mvel2.templates.res.TextNode.eval(TextNode.java:46)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:195)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:190)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:180)
at org.mvel2.templates.TemplateRuntime.execute(TemplateRuntime.java:169)
at
org.drools.rule.builder.dialect.java.AbstractJavaRuleBuilder.generatTemplates(AbstractJavaRuleBuilder.java:135)
at
org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(JavaConsequenceBuilder.java:128)
at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:86)
at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:1159)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:649)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:290)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:488)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25)
at com.myfirm.RuleFlowProcess.init(RuleFlowProcess.java:25)
at com.myfirm.RuleFlowProcess.clone(RuleFlowProcess.java:53)
at com.myfirm.ThreadTest$CloneThread.run(ThreadTest.java:35)
Caused by: java.lang.NullPointerException
at
org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:113)
... 33 more
To demonstrate this problem I have created a simple test maven project that reproduces
this error (s. attach):
I have a class that creates & inits stateful knowledge session in a init method
(RuleFlowProcess):
/**
* inits the rule flow
*/
public class RuleFlowProcess {
private StatefulKnowledgeSession ksession;
public void init() {
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();
kbuilder.add(ResourceFactory.newClassPathResource("threadSafeTest.rf"),
ResourceType.DRF);
kbuilder.add(ResourceFactory.newClassPathResource("testRules1.drl"),
ResourceType.DRL);
kbuilder.add(ResourceFactory.newClassPathResource("testRules2.drl"),
ResourceType.DRL);
kbuilder.add(ResourceFactory.newClassPathResource("testRules3.drl"),
ResourceType.DRL);
kbuilder.add(ResourceFactory.newClassPathResource("testRules4.drl"),
ResourceType.DRL);
KnowledgeBuilderErrors errors = kbuilder.getErrors();
if (errors.size() > 0) {
StringBuilder errorString = new StringBuilder();
for (KnowledgeBuilderError error : errors) {
errorString.append(error);
}
throw new RuntimeException(errorString.toString());
}
KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase();
kbase.addKnowledgePackages(kbuilder.getKnowledgePackages());
ksession = kbase.newStatefulKnowledgeSession();
}
...
}
I create & init concurrently in several (200) threads this RuleFlowProcess and some
threads crash with this exceptions while adding the resources.
I have run this project on two PCs:
core 2 duo @ 2.6 ghz, win xp prof sp3, sun jdk 1.6.0_17
Pentium Dual CPU E2160 @ 1.8GHz, XP prof SP3, sun jdk 1.6.0_16.
Could you please help us to clear this problem? Are we doing here something wrong?
If it should be an drools error, could you please create an issue for it?
Thanks!
Wbr,
Grigoriy Grigoriev
10:31 p.m.
On 15/12/2009 16:04, Grigoriev, Grigoriy wrote:
Maybe I have described the problem not detailed enough.
We are using Drools version 5.0.1 and have a concrete problem with it
in our production environment. Our customer looks already
interrogative at the developer team and have "questions" about
drools... please help! J
Let us assume a multithreaded application, that tries to initialise &
start several processes using a StatefulKnowledgeSession in order to
use in these processes rule flow. The flow in all the processes is the
same but every process instance must have an own
StatefulKnowledgeSession instance because of stateful session.
Can you open a jira and put your test case here. otherwise i'll forget
about it, when I review bugs.
Mark
12:38 a.m.
New subject: Drools 5.1.0.M1 - Process Task JPAWorkItemManager
Hi,
I am using Drools 5.1.0.M1. My question is there any reason why JPAWorkItemManager does
not call the workitemhandler when we abort a work item.
a) Step 1 - Obtain the stateful knowledge session - set the work item handler
b) Step 2 - Abort the work item. But this call does not call back the abortWorkItem
of the work item handler.
ksession.getWorkItemManager().abortWorkItem(workItemId);
I checked the JPAWorkItemManager and it does not call the handler to execute the
abortWorkItem method of the work item handler.
I do see that from
public void internalAbortWorkItem(long id) ---- there is a call for the work
item handler method but no call from abortWorkItem method
Any reason why?
Thanks
Vijay
2:41 a.m.
New subject: Drools 5.1.0.M1 - Process Task JPAWorkItemManager
After a work item has been created, the work item manager expects the
handler to either signal the completion of the work item, or the
abortion if it could not be executed normally. Note that, if the
handler decides to call the abortWorkItem method, the abort method of
the handler is not called again (as the handler just told the engine
that the work item could not be executed, so no need to call that again).
The abortWorkItem method is called when the work item should no longer
be executed, for example when the process it was executing in was
aborted. In that case, the abortWorkItem method of the handler will be
called, so he can also cancel the work item in the external system. For
example, if the work item is a user task on a task list, this will
usually remove the task from the task list again.
Hope this helps!
Kris
Quoting Vijay K Pandey <VPandey(a)mdes.ms.gov>:
Hi,
I am using Drools 5.1.0.M1. My question is there any reason why
JPAWorkItemManager does not call the workitemhandler when we abort a
work item.
a) Step 1 - Obtain the stateful knowledge session - set the
work item handler
b) Step 2 - Abort the work item. But this call does not call
back the abortWorkItem of the work item handler.
ksession.getWorkItemManager().abortWorkItem(workItemId);
I checked the JPAWorkItemManager and it does not call the handler to
execute the abortWorkItem method of the work item handler.
I do see that from
public void internalAbortWorkItem(long id) ---- there is
a call for the work item handler method but no call from
abortWorkItem method
Any reason why?
Thanks
Vijay
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
6:50 a.m.
New subject: Drools 5.1.0.M1 - Process Task JPAWorkItemManager
This is what our scenario is:
a) Sample Process A: --> Start -->Human Task 1 ---> Human Task 2 -->. End
When the above process is started it will wait at "Human Task 1". Let's says
after some time/days based on some external application data - Human Task 1 needs to be
skipped/aborted and then the process moves to Task 2. In that case if we simply call this
ksession.getWorkItemManager ().abortWorkItem (workItemId);
I was expecting the above call to also call the handler's abortWorkItem method so that
the external Task can also be skipped/aborted.
I understand that when we add a new Task 3 different types of events are registered for
the TaskEvent and if we complete the task (complete/failed/skipped) - the registered
handlers will get called back and will then internally call the
workitemamanger.abortWorkItem if it is failed/skipped and that will resolve the issue, but
the problem I am facing is after the server gets restarted all the added listeners are
lost and there won't be any callbacks.
May be I can manually call the skip of the Task associated with the work item but I
thought to have this call non intrusive.
Thanks
Vijay
-----Original Message-----
From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On
Behalf Of Kris Verlaenen
Sent: Tuesday, December 15, 2009 7:42 PM
To: Rules Users List; Vijay K Pandey
Cc: Rules Users List
Subject: Re: [rules-users] Drools 5.1.0.M1 - Process Task JPAWorkItemManager
After a work item has been created, the work item manager expects the
handler to either signal the completion of the work item, or the
abortion if it could not be executed normally. Note that, if the
handler decides to call the abortWorkItem method, the abort method of
the handler is not called again (as the handler just told the engine
that the work item could not be executed, so no need to call that again).
The abortWorkItem method is called when the work item should no longer
be executed, for example when the process it was executing in was
aborted. In that case, the abortWorkItem method of the handler will be
called, so he can also cancel the work item in the external system. For
example, if the work item is a user task on a task list, this will
usually remove the task from the task list again.
Hope this helps!
Kris
Quoting Vijay K Pandey <VPandey(a)mdes.ms.gov>:
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
Hi,
I am using Drools 5.1.0.M1. My question is there any reason why
JPAWorkItemManager does not call the workitemhandler when we abort a
work item.
a) Step 1 - Obtain the stateful knowledge session - set the
work item handler
b) Step 2 - Abort the work item. But this call does not call
back the abortWorkItem of the work item handler.
ksession.getWorkItemManager().abortWorkItem(workItemId);
I checked the JPAWorkItemManager and it does not call the handler to
execute the abortWorkItem method of the work item handler.
I do see that from
public void internalAbortWorkItem(long id) ---- there is
a call for the work item handler method but no call from
abortWorkItem method
Any reason why?
Thanks
Vijay
10:52 a.m.
Leaving the issue of thread safety aside, I wonder why it should be
necessary to
build the same KnowledgeBase 200 times? I'd say you are wasting a lot of
cycles.
It ought to be possible to derive many independent (and concurrent) sessions
from one kbase.
-W
2009/12/15 Grigoriev, Grigoriy <Grigoriy.Grigoriev(a)t-systems.ru>
I have already mentioned this issue previously here (see
http://n3.nabble.com/Mvel-and-multithreading-td50133.html)
Maybe I have described the problem not detailed enough.
We are using Drools version 5.0.1 and have a concrete problem with it in
our production environment. Our customer looks already interrogative at the
developer team and have „questions“ about drools… please help! J
Let us assume a multithreaded application, that tries to initialise & start
several processes using a StatefulKnowledgeSession in order to use in these
processes rule flow. The flow in all the processes is the same but every
process instance must have an own StatefulKnowledgeSession instance because
of stateful session.
Actually the problem:
At the initializing phase occurs an org.mvel2.CompileException exception
from time to time at KnowledgeBuilder.add(…):
Exception in thread "Thread-60" [Error: incomplete statement: (possible
use of reserved keyword as identifier: )]
[Near : {... globals != empt ....}]
^
[Line: 0, Column: 0]
at org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(*
MVELInterpretedRuntime.java:153*)
at org.mvel2.MVELInterpretedRuntime.parse(*
MVELInterpretedRuntime.java:44*)
at org.mvel2.MVEL.eval(*MVEL.java:514*)
at org.mvel2.templates.res.IfNode.eval(*IfNode.java:61*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.TerminalNode.eval(*TerminalNode.java:39*)
at org.mvel2.templates.res.ForEachNode.eval(*ForEachNode.java:116*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.TerminalNode.eval(*TerminalNode.java:39*)
at org.mvel2.templates.res.IfNode.eval(*IfNode.java:64*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.ExpressionNode.eval(*
ExpressionNode.java:53*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:195*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:190*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:180*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:169*)
at
org.drools.rule.builder.dialect.java.AbstractJavaRuleBuilder.generatTemplates(
*AbstractJavaRuleBuilder.java:126*)
at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(
*JavaConsequenceBuilder.java:128*)
at org.drools.rule.builder.RuleBuilder.build(*RuleBuilder.java:86*)
at org.drools.compiler.PackageBuilder.addRule(*
PackageBuilder.java:1159*)
at org.drools.compiler.PackageBuilder.addPackage(*
PackageBuilder.java:649*)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(*
PackageBuilder.java:290*)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(*
PackageBuilder.java:488*)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(*
KnowledgeBuilderImpl.java:25*)
at com.myfirm.RuleFlowProcess.init(*RuleFlowProcess.java:25*)
at com.myfirm.RuleFlowProcess.clone(*RuleFlowProcess.java:53*)
at com.myfirm.ThreadTest$CloneThread.run(*ThreadTest.java:35*)
Caused by: *java.lang.NullPointerException*
at org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(*
MVELInterpretedRuntime.java:113*)
... 27 more
Exception in thread "Thread-72" [Error: incomplete statement: (possible
use of reserved keyword as identifier: )]
[Near : {... declarations != empt ....}]
^
[Line: 0, Column: 0]
at org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(*
MVELInterpretedRuntime.java:153*)
at org.mvel2.MVELInterpretedRuntime.parse(*
MVELInterpretedRuntime.java:44*)
at org.mvel2.MVEL.eval(*MVEL.java:514*)
at org.mvel2.templates.res.IfNode.eval(*IfNode.java:61*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.ExpressionNode.eval(*
ExpressionNode.java:53*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.ExpressionNode.eval(*
ExpressionNode.java:53*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.TerminalNode.eval(*TerminalNode.java:39*)
at org.mvel2.templates.res.ForEachNode.eval(*ForEachNode.java:116*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.TerminalNode.eval(*TerminalNode.java:39*)
at org.mvel2.templates.res.ForEachNode.eval(*ForEachNode.java:116*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.ExpressionNode.eval(*
ExpressionNode.java:53*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.res.ExpressionNode.eval(*
ExpressionNode.java:53*)
at org.mvel2.templates.res.TextNode.eval(*TextNode.java:46*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:195*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:190*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:180*)
at org.mvel2.templates.TemplateRuntime.execute(*
TemplateRuntime.java:169*)
at
org.drools.rule.builder.dialect.java.AbstractJavaRuleBuilder.generatTemplates(
*AbstractJavaRuleBuilder.java:135*)
at org.drools.rule.builder.dialect.java.JavaConsequenceBuilder.build(
*JavaConsequenceBuilder.java:128*)
at org.drools.rule.builder.RuleBuilder.build(*RuleBuilder.java:86*)
at org.drools.compiler.PackageBuilder.addRule(*
PackageBuilder.java:1159*)
at org.drools.compiler.PackageBuilder.addPackage(*
PackageBuilder.java:649*)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(*
PackageBuilder.java:290*)
at org.drools.compiler.PackageBuilder.addKnowledgeResource(*
PackageBuilder.java:488*)
at org.drools.builder.impl.KnowledgeBuilderImpl.add(*
KnowledgeBuilderImpl.java:25*)
at com.myfirm.RuleFlowProcess.init(*RuleFlowProcess.java:25*)
at com.myfirm.RuleFlowProcess.clone(*RuleFlowProcess.java:53*)
at com.myfirm.ThreadTest$CloneThread.run(*ThreadTest.java:35*)
Caused by: *java.lang.NullPointerException*
at org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(*
MVELInterpretedRuntime.java:113*)
... 33 more
To demonstrate this problem I have created a simple test maven project that
reproduces this error (s. attach):
I have a class that creates & inits stateful knowledge session in a init
method (RuleFlowProcess):
/**
* *inits* the rule flow
*/
*public* *class* RuleFlowProcess {
*private* StatefulKnowledgeSession ksession;
*public* *void* init() {
KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.*
newKnowledgeBuilder*();
kbuilder.add(ResourceFactory.*newClassPathResource*(
"threadSafeTest.rf"), ResourceType.*DRF*);
kbuilder.add(ResourceFactory.*newClassPathResource*(
"testRules1.drl"), ResourceType.*DRL*);
kbuilder.add(ResourceFactory.*newClassPathResource*(
"testRules2.drl"), ResourceType.*DRL*);
kbuilder.add(ResourceFactory.*newClassPathResource*(
"testRules3.drl"), ResourceType.*DRL*);
kbuilder.add(ResourceFactory.*newClassPathResource*(
"testRules4.drl"), ResourceType.*DRL*);
KnowledgeBuilderErrors errors = kbuilder.getErrors();
*if* (errors.size() > 0) {
StringBuilder errorString = *new* StringBuilder();
*for* (KnowledgeBuilderError error : errors) {
errorString.append(error);
}
*throw* *new* RuntimeException(errorString.toString());
}
KnowledgeBase kbase = KnowledgeBaseFactory.*newKnowledgeBase*
();
kbase.addKnowledgePackages(kbuilder.getKnowledgePackages());
ksession = kbase.newStatefulKnowledgeSession();
}
…
}
I create & init concurrently in several (200) threads this RuleFlowProcess
and some threads crash with this exceptions while adding the resources.
I have run this project on two PCs:
core 2 duo @ 2.6 ghz, win xp prof sp3, sun jdk 1.6.0_17
Pentium Dual CPU E2160 @ 1.8GHz, XP prof SP3, sun jdk 1.6.0_16.
Could you please help us to clear this problem? Are we doing here something
wrong?
If it should be an drools error, could you please create an issue for it?
Thanks!
Wbr,
Grigoriy Grigoriev
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
5253
days inactive
5254
days old
5 comments
5 participants
participants (5)
-
Grigoriev, Grigoriy -
Kris Verlaenen -
Mark Proctor -
Vijay K Pandey -
Wolfgang Laun