Equality semantics of logical assertions and stated assertions
by mikerod
I understand that logical insertions in Drools does not insert two facts that
are equal according to their #equals implementation (and associated
#hashCode logic).
I'm basing this off of my own investigation plus the (well written)
documentation @
http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html/....
However, normal/stated fact assertions only use identity-based equality
checks - by default.
It looks like this can be changed to value-based equality via
RuleBaseConfiguration.
I have found some related, old Jiras:
https://issues.jboss.org/browse/JBRULES-266
https://issues.jboss.org/browse/JBRULES-233
In both cases, Mark Proctor had a final remark, but I wasn't able to
understand what was really decided and why.
One specific comment @ https://issues.jboss.org/browse/JBRULES-266 is,
"logical assertions are always equality based. Stated facts can now use
identity and equality - using your configuration settings.
I have added another configuration setting to dictate how logical over-ride
works. Does it discard the original fact, or turn it into two stated fact
handles."
What is the reasoning behind only using the value-based equality for logical
assertions?
Why is it not configurable as stated fact assertions are?
Also, why is the default behavior of stated fact assertion to be
identity-based equality?
- I find the inconsistency between the default for normal assertions and the
(only option) for logical assertion to be a bit confusing/inconsistent.
I'm just looking for an understanding the motivation behind these design
decisions.
I have had a lot of performance issues using, primarily, logical assertions
due to the "no duplicate" checking being done.
Even the stated assertions do still come with a cost of creating the initial
FactHandle.
With deeply nested/complex domain objects, the #equals and #hashCode
implementations may be quite expensive when executed many times throughout
rule execution.
This is especially prominent in accumulators that may later accumulate these
objects into collections that then are also subject to this equals/hashCode
"penalty".
I have a related post a while back @
http://drools.46999.n3.nabble.com/Object-size-impact-on-session-insertion....
I do not believe it is typical to use complex domain model objects as the
keys to something like a HashMap.
One reason (there are more; especially for mutable objects) would be due to
the performance around having them be hashed and equality checked regularly
when the
map is accessed, modified, etc.
The creation of many FactHandle's has shown up in some of my profiling
performance problems due to this the constructor immediately hashing my
domain model objects.
I think the reason the fact handles use this information is for value-based
equality comparisons - such as the only method used by the Truth Maintenance
System logical assertions.
I would really appreciate more insight into the motivation for not allowing
#equals facts to be logically asserted separately into working memory -
especially since there is a price to pay for the behavior in my case.
--
View this message in context: http://drools.46999.n3.nabble.com/Equality-semantics-of-logical-assertion...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11 years, 6 months
Repositories in Kie-Drools
by Sumit Dhaniya
I want to use a repository hosted on cloud as repository in my kie ide.
I tried creating a new repo cloning an existing repo but after cloning kie
ide creates a new repo path at localhost and doesn't uses the cloud repo
path.
Can I achieve this or I'll have to find a way to sync two repositories one
linked to kie and another to cloud repo.
--
View this message in context: http://drools.46999.n3.nabble.com/Repositories-in-Kie-Drools-tp4030254.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
11 years, 6 months
Kie Spring integration
by Sumit Dhaniya
Hi,
I'm trying to inject KieBase objects declared in my
kmodule.xml file which is in a jar imported by using maven dependencies in
my project but it doesn't work. Below are few things I tried :-
1.) @KBase(name="defaultKieBase")
@KReleaseId(artifactId="com.demo", groupId="FirstDemo",
version="1.0")
private KieBase kbase;
2.)KieServices.Factory.get().newKieContainer(KieServices.Factory.get().newReleaseId("com.demo","FirstDemo","1.0"))
nothing works until I import drl files in my project and write own
kmodule.xml file. FirstDemo Project is imported correctly using maven I can
see it in my dependencies also.
Is there anything I'm doing wrong?
I'm using spring-tc server and trying this in spring project and I've
imported spring-kie and kie-ci and related dependencies in my project.
--
View this message in context: http://drools.46999.n3.nabble.com/Kie-Spring-integration-tp4030243.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
11 years, 6 months
Diesel montres courantes se présentent tout simplement parce que votre meilleure option dans la gestion de montres que vous pouvez acheter
by cheapwatches
Diesel annoncé catégorie des montres I-pod lecteur mp3, stéréo Main joueur de
poker (WMP-1V), ce fut le commencer avec le type il s'asseoir et regarder
rester conçu. Quand quelqu'un est une plongée importante dans le futur
potentiel, aider de nombreuses personnes à être manipulés par les
propriétaires chansons préférées en raison de sa propre s'asseoir et
regarder tout en étant get pour éclairer la période de temps. L'application
continua de courir Diesel Montre store <http://www.dieselmontre.com/>
montres à la suite d'être seul objectif principal réel pour vous aider
principal objectif multicouche, un style importante qui n'a effectivement
lieu et même voyager un peu rapidement. Mai '08 est une autre révolution
gigantesque conçu pour un moteur diesel à l'échelle mondiale dans la gestion
de montres devraient-ils déchargés que G-SHOCK Riseman, ce n'était que dans
le monde entier à commencer par 6 multi-bande le diesel des ondes qui
fonctionne sous montres à vendre restreintes s'asseoir et regarder de tous
les produits s'asseoir et regarder, moteur diesel contient fréquemment et
même systématiquement stimulé l'état de concept à leur fonctionnement
montres encore plus loin et plus si sont toujours la gestion à l'échelle
mondiale en ligne de montres de fonctionnement numérique, à laquelle
certaines personnes accueillent toujours une colossale partie de la
publicité. Grâce notion outre, les probabilités de concept de restauration
assez fréquemment, demain ne peuvent apparaître en effet remarquable dans un
moteur diesel, à travers un certain nombre de penser à tout ce qui les
possèdent alors une grande s'asseoir et regarder vraiment va acquérir. En
général individuel, ayant sur une montre-bracelet est vraiment aussi
rapide tout simplement parce que répondre et même la sélection de toutes
sortes de choses qui est bouclée dans la branche. En supposant que cela
pourrait effectivement éclairer un temps précieux, il est affligé sans avoir
un moment considération. Puis, dans l'individu qui pourrait être individuel
de ce qu'il ou elle les vêtements, à vrai dire, il est connu comme un devoir
de s'assurer qu'une personne fait la meilleure application. Obtenir un
emploi mieux peut utiliser le présentant sur le sit parfait et regarder pour
vous aider à aider à faire juste la bonne formule compte tenu de la diesel
autres parties alimenté montres courantes appartenant aux vêtements qu'ils
sont vraiment avoir sur. Le plus souvent, à moteur diesel montres courantes
se présentent tout simplement parce que votre meilleure option dans la
gestion de montres que vous pouvez acheter. Une chose très importante, une
fois l'achat s'asseoir et regarder Diesel Montre prix
<http://www.dieselmontre.com/> pour vous aider à être habillé en est
certainement l'occasion appartenant à l'asseoir et regarder faire tout le
travail. Toutefois, vous pourriez désirer la bonne façon attrayante
l'application se sent, en plus il est un être de s'assurer que vous serez en
appréciant un s'asseoir et regarder ce qui fonctionne totalement claire.
Diesel montres courantes sont remarquables pour sa propre possibilité
d'accomplir le bon nombre de prudent occasion de l'opération. Beaucoup de
ces montres courantes faire le travail tout à fait clairement pour une
personne qui pourrait être porté sur la variété d'options du fait que le
s'asseoir et regarder des cadeaux.
--
View this message in context: http://drools.46999.n3.nabble.com/Diesel-montres-courantes-se-presentent-...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11 years, 6 months
Pièces de moteur diesel apparaissent principalement parce que la meilleure option pour les pièces qui peuvent être achetés
by cheapwatches
Diesel a commencé modèle de montre-bracelet Mp3player, Bras Mp3 footballeur
(WMP-1V), qui avait été parmi les nombreuses premières sortes de la voir
généralement être construit. Pour une raison qui était initialement une
bonne hop dans un avenir proche, offrant aux consommateurs d'être contrôlées
par votre chanson à travers votre siège, mais encore être prêt à révéler à
la quantité de temps. Tout procuré morceaux avec apparaissant motif exclusif
qui sera nombreux motif, une bonne direction que semblait sont fournis avec
choix extrêmement Diesel <http://www.dieselmontre.com/> instantanément.
Août 08 aura été d'abord un autre pas en avant considérable destiné à moteur
diesel dans le monde entier pour les pièces dès qu'ils ont révélé une
Riseman G-SHOCK, qui avait eu des premiers 6 multibande diffusion des pièces
de moteur diesel internationales sur la vente exploités voir hors de tout
les marques de voir les, moteur diesel a obtenu en continu avec livrées
correctement la qualité des systèmes de leurs morceaux les plus profondes et
plus loin et ont tendance à être également parmi les nombreux meneurs
internationaux pour les morceaux en ligne, la place de ces également en
charge un grand système de la promouvoir. Systèmes et aussi des possibilités
de développement des systèmes utilisant régulièrement, votre avenir immédiat
ne semble vraiment être exaltante pour moteur diesel, en utilisant
d'innombrables curieux de savoir ce que précisément votre après voir
substantielle pourrait atteindre. Pour votre gars norme, étant vêtu d'une
montre-bracelet est aussi facile en raison principalement détendre avec le
choix d'une seule chose qui peut vraiment être attaché sur le triceps /
biceps. Si elle va révéler au point dans le temps, il est endommagé wthout
utilisant notion suivante. Pourtant, à votre type qui peut être choisi de
manière à ce qu'elle va porter, certes, il est souvent un devez être sûr
d'une particulière devrait obtenir tout idéal. Sa mise en place pourrait
idéal sont vendus entre être habillé dans le siège approprié qui gagnent le
meilleur appariement en utilisant les pyjamas des pièces de moteur diesel
dans la robe ils sont juste habillées po Très souvent, des pièces de moteur
diesel apparaissent principalement parce que le meilleure option pour les
pièces qui peuvent être achetés. Un Montre Diesel
<http://www.dieselmontre.com/> point tout moment très puissant à la
recherche d'un siège qui habillera en ressort que les moyens au sein de la
voir travailler essentiellement. Même si vous voulez la manière dont il
amende toute apparence, peut avoir pour être sûr que vous arrive d'être
l'achat d'un voir le fait que réussit merveilleusement bien. Pièces de
moteur diesel sont reconnus pour vos moyens de parvenir à la majorité
minutieux des moyens d'exécution. Ceux travail merveilleusement bien pour ce
type qui peut être excité à propos des nombreux morceaux attributs que votre
siège peut offrir.
--
View this message in context: http://drools.46999.n3.nabble.com/Pieces-de-moteur-diesel-apparaissent-pr...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11 years, 6 months
Workbench JAAS Authenticated , But NOT Authorized
by 706826
Hi,
I am configuring DB based JAAS Authentication for Kie-Drools-Workbench
6.1.0. Server log (Pasted Below) shows user is authenticated and roles are
assigned to the user. But KIE login form says “Login failed: Not Authorized
“.
I have also added roles in Organizational Unit, Repository and Projects
using kie-config-cli. But still getting the same error.
Kindly let me know what wrong am I doing.
Standalone.xml
<security-domain name="drools-guvnor" cache-type="default">
<authentication>
<login-module
code="org.jboss.security.auth.spi.DatabaseServerLoginModule"
flag="required">
<module-option name="dsJndiName"
value="java:jboss/datasources/jdbc/jbpmStagingRWDS"/>
<module-option name="principalsQuery"
value="select PASSWORD from principals where PRINCIPALID=?"/>
<module-option name="rolesQuery" value="select
ROLE,ROLEGROUP from roles WHERE principalid=?"/>
<module-option name="hashAlgorithm"
value="MD5"/>
<module-option name="hashEncoding"
value="base64"/>
<module-option name="hashCharset"
value="UTF-8"/>
<module-option name="password-stacking"
value="useFirstPass"/>
</login-module>
</authentication>
</security-domain>
Kie-drools-wb.War / WEB_INF/jboss-web.xml|
<security-domain>drools-guvnor</security-domain>
Server Logs
13:55:22,408 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) initialize
13:55:22,410 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Security domain: other
13:55:22,412 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Password hashing activated: algorithm = MD5,
encoding = base64, charset = UTF-8, callback = null, storeCallback = null
13:55:22,415 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) DatabaseServerLoginModule,
dsJndiName=java:jboss/datasources/jdbc/jbpmStagingRWDS
13:55:22,419 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) principalsQuery=select PASSWORD from principals
where PRINCIPALID=?
13:55:22,422 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) rolesQuery=select ROLE,ROLEGROUP from roles WHERE
principalid=?
13:55:22,424 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) suspendResume=true
13:55:22,426 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) login
13:55:22,428 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) suspendAnyTransaction
13:55:22,489 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Excuting query: select PASSWORD from principals
where PRINCIPALID=?, with username: iit
13:55:22,495 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Obtained user password
13:55:22,497 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) resumeAnyTransaction
13:55:22,499 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) User 'iit' authenticated, loginOk=true
13:55:22,501 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) commit, loginOk=true
13:55:22,503 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) getRoleSets using rolesQuery: select ROLE,ROLEGROUP
from roles WHERE principalid=?, username: iit
13:55:22,507 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) suspendAnyTransaction
13:55:22,509 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Excuting query: select ROLE,ROLEGROUP from roles
WHERE principalid=?, with username: iit
13:55:22,514 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Assign user to role admin
13:55:22,516 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Assign user to role analyst
13:55:22,518 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Assign user to role developer
13:55:22,521 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Assign user to role manager
13:55:22,523 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) Assign user to role user
13:55:22,525 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) resumeAnyTransaction
13:55:22,527 TRACE
[org.jboss.security.authentication.JBossCachedAuthenticationManager]
(http--127.0.0.1-8080-2) defaultLogin,
lc=javax.security.auth.login.LoginContext@3460a6,
subject=Subject(11883582).principals=org.jboss.security.SimplePrincipal@25145532(iit)org.jboss.security.SimpleGroup(a)12885648(CallerPrincip
al(members:iit))org.jboss.security.SimpleGroup@12885648(admingrp(members:admin))org.jboss.security.SimpleGroup@12885648(usergrp(members:user))org.jboss.security.SimpleGroup@12885648(analystgrp(members:analyst))org.jboss.security.SimpleGroup@12885648(developergrp(members:developer))org.jboss.security.SimpleGroup@12
885648(managergrp(members:manager))
13:55:22,538 TRACE
[org.jboss.security.authentication.JBossCachedAuthenticationManager]
(http--127.0.0.1-8080-2) updateCache,
inputSubject=Subject(11883582).principals=org.jboss.security.SimplePrincipal@25145532(iit)org.jboss.security.SimpleGroup@12885648(CallerPrincipal(members:iit))org.jboss.security.SimpleGroup
@12885648(admingrp(members:admin))org.jboss.security.SimpleGroup@12885648(usergrp(members:user))org.jboss.security.SimpleGroup@12885648(analystgrp(members:analyst))org.jboss.security.SimpleGroup@12885648(developergrp(members:developer))org.jboss.security.SimpleGroup@12885648(managergrp(members:manager)),
cacheSubj
ect=Subject(11399784).principals=org.jboss.security.SimplePrincipal@25145532(iit)org.jboss.security.SimpleGroup@12885648(CallerPrincipal(members:iit))org.jboss.security.SimpleGroup@12885648(admingrp(members:admin))org.jboss.security.SimpleGroup@12885648(usergrp(members:user))org.jboss.security.SimpleGroup@12885648
(analystgrp(members:analyst))org.jboss.security.SimpleGroup@12885648(developergrp(members:developer))org.jboss.security.SimpleGroup@12885648(managergrp(members:manager))
13:55:22,556 TRACE
[org.jboss.security.authentication.JBossCachedAuthenticationManager]
(http--127.0.0.1-8080-2) Inserted cache info:
org.jboss.security.authentication.JBossCachedAuthenticationManager$DomainInfo@5bd7b
13:55:22,560 TRACE
[org.jboss.security.authentication.JBossCachedAuthenticationManager]
(http--127.0.0.1-8080-2) End isValid, true
13:55:22,562 TRACE [org.jboss.security.SecurityRolesAssociation]
(http--127.0.0.1-8080-2) Setting threadlocal:null
13:55:22,576 TRACE [org.jboss.security.SecurityRolesAssociation]
(http--127.0.0.1-8080-2) Setting threadlocal:null
13:55:22,578 TRACE
[org.jboss.security.authentication.JBossCachedAuthenticationManager]
(http--127.0.0.1-8080-2) Flushing iit from cache
13:55:22,580 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule]
(http--127.0.0.1-8080-2) logout
13:55:22,841 TRACE [org.jboss.security.SecurityRolesAssociation]
(http--127.0.0.1-8080-3) Setting threadlocal:null
13:55:22,845 TRACE [org.jboss.security.SecurityRolesAssociation]
(http--127.0.0.1-8080-2) Setting threadlocal:null
13:55:22,845 TRACE [org.jboss.security.SecurityRolesAssociation]
(http--127.0.0.1-8080-1) Setting threadlocal:null
Config Tool
********************************************************
************* Welcome to Kie config CLI ****************
********************************************************
>>Please specify location of the parent folder of .niogit
D:\Servers\Drools-6-Deployment\Server-A-As-7\bin
>>Please enter command (type help to see available commands):
add-role-repo
>>Repository alias:netsolrepo
>>Security roles (comma separated
list):admin,analyst,business,user,developer
Result:
Role admin added successfully to repository netsolrepo
Role analyst added successfully to repository netsolrepo
Role business added successfully to repository netsolrepo
Role user added successfully to repository netsolrepo
Role developer added successfully to repository netsolrepo
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
add-role-org-unit
>>Organizational Unit name:netsol
>>Security roles (comma separated
list):admin,analyst,business,user,developer
Result:
Role admin added successfully to Organizational Unit netsol
Role analyst added successfully to Organizational Unit netsol
Role business added successfully to Organizational Unit netsol
Role user added successfully to Organizational Unit netsol
Role developer added successfully to Organizational Unit netsol
Regards,
Zahid Ahmed
--
View this message in context: http://drools.46999.n3.nabble.com/Workbench-JAAS-Authenticated-But-NOT-Au...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11 years, 6 months
Rules not picked when packaged inside the JAR
by ash316
I am working on DROOLS 6.0.1 application. I have my rule files (*.drl)
packaged inside a separate project which is included as a jar file as a
maven dependency. When I deploy my project, KIEModule is not able to find
the rules files (which are packaged inside the jar above). I am not getting
an error though but rules are not getting fired.If I manually place the
rules files under classpath say WEB-INF/rules/*.drl they are detected and
rules are executed.I was under impression that KIEmodules are auto
discovered from anywhere in classpath.Any pointers are appreciated. This is
general question hence I have not included the comprehensive code files.
Everything start working once I place the *.drl files in the classpath (take
them outside of jar).I have opened the JIRA issue @ Link
<https://issues.jboss.org/browse/DROOLS-466> Thanks
--
View this message in context: http://drools.46999.n3.nabble.com/Rules-not-picked-when-packaged-inside-t...
Sent from the Drools: User forum mailing list archive at Nabble.com.
11 years, 6 months
Memory leak or rule problem?
by James Breese
We’re running DROOLS 6.1.0-SNAPSHOT and are seeing unbounded memory growth for certain rules. I’ve put together an example that reproduces the problem using a rule based on (but not identical to) one that we are seeing memory leaks. I’m not sure if the leaks are caused by poorly written rules or by something else.
The attached example can be built and run using maven, i.e. “mvn install exec:exec” It’s running DROOLS in stream mode using a real-time clock and using EQUALITY equals behavior. The input to the rules are events that are identified by their eventId (a long value) and a state enumeration having 3 possible values: ACTIVE, INACTIVE and ACCEPTED. The rules are supposed to work like this:
1. If an event is received with a state of ACTIVE and no event having that eventId has been captured, then capture the event data in a new fact (CapturedEvent) and delete the event.
2. If an event is received with a state of INACTIVE and an event having the same eventId has previously been captured, then delete the CapturedEvent fact.
3. If, after 10 seconds the CapturedEvent fact is still there then set its state to ACCEPTED.
4. All other events facts are deleted.
Not a real useful example, but it does demonstrate either a memory leak or a poorly written set of rules.
After creating the KieSession in streams mode, the demo starts inserting event facts every 5ms. There are 1000 different eventIds - each iteration of events being inserted sends one event with each eventId. Initially the events state is set to ACTIVE. Periodically the events state is set to INACTIVE for one iteration, then back to ACTIVE. The intent is that 1000 different events will, 10 seconds after they’re first inserted, transition from ACTIVE to ACCEPTED. Then shortly after the INACTIVE events are sent and all 1000 CapturedEvent facts are deleted. The cycle then repeats until 500,000 events have been inserted into the session. Because all events are deleted by one of the rules, at the end of the run there should be 1000 facts of type CapturedEvent in the session since the final iteration of events all have a state of ACTIVE.
For example, the set of events look something like this:
Time ID State
0.000s 0 ACTIVE
0.005s 1 ACTIVE
0.010s 2 ACTIVE
…
4.995s 999 ACTIVE
5.000s 0 ACTIVE
5.005s 1 ACTIVE
…
9.995s 999 ACTIVE
10.000s 0 ACTIVE
10.005s 1 ACTIVE
…
14.995s 999 ACTIVE
15.000s 0 INACTIVE
15.005s 1 INACTIVE
15.010s 2 INACTIVE
…
19.995s 999 INACTIVE
20.000s 0 ACTIVE
and so on until a total of 500,000 events are inserted. Each iteration of 1000 events takes 5 seconds. So basically the first three iterations the events are ACTIVE then the fourth iteration the events are INACTIVE, then three more iterations of ACTIVE, etc.
What actually happens is that the rules actually work but only once for each ID. So, for example, the first insert of event ID 0 with state of ACTIVE matches the “capture active” rule as expected. The second insert of event ID 0 with state of ACTIVE matches the “delete events” rule. 10 seconds after the first event with ID 0 arrives, the “ensure active” rule matches. The third ACTIVE event also matches the “delete event” rule. When the fourth event with ID 0 and state INACTIVE is inserted that matches the “restart timer” rule which deletes the CapturedEvent fact. When the next event with ID 0 and state ACTIVE is inserted, I expected the “capture active” rule to fire because the CapturedEvent fact was deleted. But instead the “delete events” rule matches, and from this point on all events trigger the “delete events” rule.
After garbage collection, analysis of the heap dump shows there are 248,000 instances of org.drools.core.reteoo.RightTuple objects and the same number of org.drools.core.common.PhreakPropagationContext objects. Also, there are 124,000 instances of org.drools.core.common.EventFactHandle objects, even though the reported fact count is 0.
The demo project is attached.
11 years, 6 months
Drools 6.0 | Workbench Authentication | JAAS with DB
by Zahid Ahmed
Hi,
I am configuring DB based JAAS Authentication for Kie-Drools-Workbench 6.1.0. Server log shows user is authenticated and roles are assigned to the user. But KIE login form says "Login failed: Not Authorized ".
I have also added roles in Organizational Unit, Repository and Projects using kie-config-cli. But still getting the same error.
Kindly let me know what wrong am I doing.
Standalone.xml
<security-domain name="drools-guvnor" cache-type="default">
<authentication>
<login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
<module-option name="dsJndiName" value="java:jboss/datasources/jdbc/jbpmStagingRWDS"/>
<module-option name="principalsQuery" value="select PASSWORD from principals where PRINCIPALID=?"/>
<module-option name="rolesQuery" value="select ROLE,ROLEGROUP from roles WHERE principalid=?"/>
<module-option name="hashAlgorithm" value="MD5"/>
<module-option name="hashEncoding" value="base64"/>
<module-option name="hashCharset" value="UTF-8"/>
<module-option name="password-stacking" value="useFirstPass"/>
</login-module>
</authentication>
</security-domain>
Kie-drools-wb.War / WEB_INF/jboss-web.xml|
<security-domain>drools-guvnor</security-domain>
Server Logs
13:55:22,408 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) initialize
13:55:22,410 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Security domain: other
13:55:22,412 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Password hashing activated: algorithm = MD5, encoding = base64, charset = UTF-8, callback = null, storeCallback = null
13:55:22,415 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) DatabaseServerLoginModule, dsJndiName=java:jboss/datasources/jdbc/jbpmStagingRWDS
13:55:22,419 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) principalsQuery=select PASSWORD from principals where PRINCIPALID=?
13:55:22,422 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) rolesQuery=select ROLE,ROLEGROUP from roles WHERE principalid=?
13:55:22,424 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) suspendResume=true
13:55:22,426 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) login
13:55:22,428 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) suspendAnyTransaction
13:55:22,489 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Excuting query: select PASSWORD from principals where PRINCIPALID=?, with username: iit
13:55:22,495 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Obtained user password
13:55:22,497 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) resumeAnyTransaction
13:55:22,499 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) User 'iit' authenticated, loginOk=true
13:55:22,501 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) commit, loginOk=true
13:55:22,503 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) getRoleSets using rolesQuery: select ROLE,ROLEGROUP from roles WHERE principalid=?, username: iit
13:55:22,507 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) suspendAnyTransaction
13:55:22,509 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Excuting query: select ROLE,ROLEGROUP from roles WHERE principalid=?, with username: iit
13:55:22,514 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Assign user to role admin
13:55:22,516 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Assign user to role analyst
13:55:22,518 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Assign user to role developer
13:55:22,521 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Assign user to role manager
13:55:22,523 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) Assign user to role user
13:55:22,525 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) resumeAnyTransaction
13:55:22,527 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--127.0.0.1-8080-2) defaultLogin, lc=javax.security.auth.login.LoginContext@3460a6, subject=Subject(11883582).principals=org.jboss.security.SimplePrincipal@25145532(iit)org.jboss.security.SimpleGroup(a)12885648(CallerPrincip
al(members:iit))org.jboss.security.SimpleGroup@12885648(admingrp(members:admin))org.jboss.security.SimpleGroup@12885648(usergrp(members:user))org.jboss.security.SimpleGroup@12885648(analystgrp(members:analyst))org.jboss.security.SimpleGroup@12885648(developergrp(members:developer))org.jboss.security.SimpleGroup@12
885648(managergrp(members:manager))
13:55:22,538 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--127.0.0.1-8080-2) updateCache, inputSubject=Subject(11883582).principals=org.jboss.security.SimplePrincipal@25145532(iit)org.jboss.security.SimpleGroup@12885648(CallerPrincipal(members:iit))org.jboss.security.SimpleGroup
@12885648(admingrp(members:admin))org.jboss.security.SimpleGroup@12885648(usergrp(members:user))org.jboss.security.SimpleGroup@12885648(analystgrp(members:analyst))org.jboss.security.SimpleGroup@12885648(developergrp(members:developer))org.jboss.security.SimpleGroup@12885648(managergrp(members:manager)), cacheSubj
ect=Subject(11399784).principals=org.jboss.security.SimplePrincipal@25145532(iit)org.jboss.security.SimpleGroup@12885648(CallerPrincipal(members:iit))org.jboss.security.SimpleGroup@12885648(admingrp(members:admin))org.jboss.security.SimpleGroup@12885648(usergrp(members:user))org.jboss.security.SimpleGroup@12885648
(analystgrp(members:analyst))org.jboss.security.SimpleGroup@12885648(developergrp(members:developer))org.jboss.security.SimpleGroup@12885648(managergrp(members:manager))
13:55:22,556 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--127.0.0.1-8080-2) Inserted cache info: org.jboss.security.authentication.JBossCachedAuthenticationManager$DomainInfo@5bd7b
13:55:22,560 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--127.0.0.1-8080-2) End isValid, true
13:55:22,562 TRACE [org.jboss.security.SecurityRolesAssociation] (http--127.0.0.1-8080-2) Setting threadlocal:null
13:55:22,576 TRACE [org.jboss.security.SecurityRolesAssociation] (http--127.0.0.1-8080-2) Setting threadlocal:null
13:55:22,578 TRACE [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--127.0.0.1-8080-2) Flushing iit from cache
13:55:22,580 TRACE [org.jboss.security.auth.spi.DatabaseServerLoginModule] (http--127.0.0.1-8080-2) logout
13:55:22,841 TRACE [org.jboss.security.SecurityRolesAssociation] (http--127.0.0.1-8080-3) Setting threadlocal:null
13:55:22,845 TRACE [org.jboss.security.SecurityRolesAssociation] (http--127.0.0.1-8080-2) Setting threadlocal:null
13:55:22,845 TRACE [org.jboss.security.SecurityRolesAssociation] (http--127.0.0.1-8080-1) Setting threadlocal:null
Config Tool
********************************************************
************* Welcome to Kie config CLI ****************
********************************************************
>>Please specify location of the parent folder of .niogit
D:\Servers\Drools-6-Deployment\Server-A-As-7\bin
>>Please enter command (type help to see available commands):
add-role-repo
>>Repository alias:netsolrepo
>>Security roles (comma separated list):admin,analyst,business,user,developer
Result:
Role admin added successfully to repository netsolrepo
Role analyst added successfully to repository netsolrepo
Role business added successfully to repository netsolrepo
Role user added successfully to repository netsolrepo
Role developer added successfully to repository netsolrepo
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
add-role-org-unit
>>Organizational Unit name:netsol
>>Security roles (comma separated list):admin,analyst,business,user,developer
Result:
Role admin added successfully to Organizational Unit netsol
Role analyst added successfully to Organizational Unit netsol
Role business added successfully to Organizational Unit netsol
Role user added successfully to Organizational Unit netsol
Role developer added successfully to Organizational Unit netsol
Regards,
Zahid Ahmed
11 years, 6 months