[JBoss JIRA] (DROOLS-3090) KieScanner does not work as expected
by Ales Dolecek (Jira)
[ https://issues.jboss.org/browse/DROOLS-3090?page=com.atlassian.jira.plugi... ]
Ales Dolecek commented on DROOLS-3090:
--------------------------------------
I have same problem. Everything works when I test it. It replaces released rules and works fine. But after few days when it really matters it does not work. The system is running 24/7 and during day processes about 1500 sessions per hour, usually submitted in small "chunks".
We check for changes every 5 minutes.
*I think that it breaks when the check/change occurs during processing*, but can't prove it as it depends on synchronization which is out of my control. The issue happens rarely - but that is maily because the system might be dunning weeks without actual update of the rules. And then when the change is made and it turns out that it is not applied it is impossible to trace back lifetime of the system.
We get new sessions like this:
{code}
KieSession session = kbase.newKieSession();
try {
RulesListener listener = new RulesListener(LOG);
session.addEventListener((AgendaEventListener) listener);
session.addEventListener((RuleRuntimeEventListener) listener);
session.setGlobal("backend", backend);
for (Object fact : facts)
session.insert(fact);
session.fireAllRules();
session.insert(Stage.META_DATA);
session.fireAllRules();
session.insert(Stage.FULL_TEXT);
session.fireAllRules();
for (Object fact : session.getObjects()) {
if (fact instanceof UserData) {
UserData kvp = (UserData) fact;
@Nullable String value = kvp.getValue();
if (value != null)
result.put(kvp.getKey(), value);
}
}
@Nullable String rule = listener.getDemandTypeRule();
if (rule != null)
result.put("AM_RuleName", rule);
} finally {
session.dispose();
}
{code}
eg. we keep the kbase "forever" - but that should be OK.
We had similiar problem back in version 5.5 (DROOLS-215) and I hoped that this whole new aproach will help.
Is there any description how this whole Scanner thing is actually implemented? I suppose you must use hierarchical classloader?
---
I'll try to implement wrapped arounf kbase, that will create brand new kbase after seeing event UPDATING from ScannerListener.
> KieScanner does not work as expected
> ------------------------------------
>
> Key: DROOLS-3090
> URL: https://issues.jboss.org/browse/DROOLS-3090
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.8.0.Final
> Reporter: Ales Dolecek
> Assignee: Mario Fusco
> Priority: Major
> Attachments: kmodule.xml, spring.xml
>
>
> We have published nee version of rules:
> {noformat}
> 2018-10-09 10:44:58,785 INFO [Timer-2][] ScannerListener Knowledge base scanner SCANNING
> 2018-10-09 10:44:59,019 INFO [Timer-2][] ScannerListener Knowledge base scanner UPDATING
> 2018-10-09 10:45:00,236 INFO [Timer-2][] KieRepositoryImpl KieModule was added: ZipKieModule[releaseId=cz.dimensiondata.o2:offline-rules:0.0.20,file=F:\GCTI8\assign_manager_2\repository\cz\dimensiondata\o2\offline-rules\0.0.20\offline-rules-0.0.20.jar]
> 2018-10-09 10:45:00,345 INFO [Timer-2][] KieScanner The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20}
> 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING
> 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING
> {noformat}
> As you can see the jar got downloaded to local M2 repository and replace. Yet drools still uses old rules.
> We have 3 artefacts:
> offline-facts - with classes inserted into operation memory
> offline-rules - with rules in 1 DRL file and 2 XLSX file
> offline-server - with the application code
> offline-server depend on offline-facs (so it can create new insances)
> offline-rules depend on offline-facts as well, but with provided scope (so the one on classpath is used)
> I have found that Maven has its own caching mechanism so even if new version is published it wont check remote repository more ften than once a day. This can be solved by setting update policy to always.
> {code}
> <repositories>
> <repository>
> <id>public</id>
> <name>Public Repositories</name>
> <url>https://example.org/nexus/content/groups/public/</url>
> <releases>
> <updatePolicy>always</updatePolicy>
> </releases>
> <snapshots>
> <updatePolicy>always</updatePolicy>
> </snapshots>
> </repository>
> </repositories>
> {code}
> Everything seems configred correctly. Fragments of spring configuration are added.
> I'm bit confused what the message:
> {code}
> The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20}
> {code}
> actually means.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10336) MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFLY-10336?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda commented on WFLY-10336:
------------------------------------------
OK, please prepare the PR.
> MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10336
> URL: https://issues.jboss.org/browse/WFLY-10336
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite, Web Services
> Environment: {noformat}
> Java(TM) SE Runtime Environment (build 8.0.5.11 - pxa6480sr5fp11-20180326_01(SR5 FP11))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180309_380776 (JIT enabled, AOT enabled)
> OpenJ9 - 49fcaf39
> OMR - 5cbbadf
> IBM - 4453dac)
> JCL - 20180319_01 based on Oracle jdk8u161-b12
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Jan Blizňák
> Priority: Major
>
> There are test failures running the WildFly Test Suite: Integration - WS on IBM jdk.
> {noformat}
> wildfly/testsuite/integration/ws] $ mvn clean install
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] EJBSignTestCase.signedRequest:86 » SOAPFault MustUnderstand headers: [{http://...
> [ERROR] SignTestCase.signedRequest:88 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:90 » SOAPFault
> [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:102 » SOAPFault
> [ERROR] EJBSignEncryptTestCase.encryptedAndSignedRequest:88 » SOAPFault MustUnderstand...
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:91 » SOAPFault
> [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:103 » SOAPFault
> [ERROR] SignEncryptTestCase.encryptedAndSignedRequest:90 » SOAPFault MustUnderstand he...
> [ERROR] WSTrustTestCase.test:318 » SOAPFault MustUnderstand headers: [{http://docs.oas...
> [ERROR] WSTrustTestCase.testActAs:441 » SOAPFault MustUnderstand headers: [{http://doc...
> [ERROR] WSTrustTestCase.testBearer:541 » SOAPFault MustUnderstand headers: [{http://do...
> [ERROR] WSTrustTestCase.testHolderOfKey:491 » SOAPFault MustUnderstand headers: [{http...
> [ERROR] WSTrustTestCase.testNoClientCallback:383 » SOAPFault MustUnderstand headers: [...
> [ERROR] WSTrustTestCase.testNoSignatureUsername:414 » SOAPFault MustUnderstand headers...
> [ERROR] WSTrustTestCase.testOnBehalfOf:468 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testPicketLink:518 » SOAPFault MustUnderstand headers: [{http:...
> [ERROR] WSTrustTestCase.testUsingEPR:350 » SOAPFault MustUnderstand headers: [{http://...
> [INFO]
> [ERROR] Tests run: 119, Failures: 0, Errors: 17, Skipped: 0
> {noformat}
> *Caused by*
> {noformat}
> Caused by: org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:87)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:53)
> at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:42)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:70)
> at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:35)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:827)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1695)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1572)
> at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1373)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:673)
> at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:533)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:442)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:343)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139)
> ... 129 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3067:
-------------------------------------
[~dadossan] I changed slightly the acceptance test due to precondition (all nodes near to [0,0]), however I didn't find any serious issue, just one point to discuss below. So really good job!
If the algorithm is used for [^a3.dmn] , then the text annotations are placed at the total top, even over the most important decision, is it intentional? I got output like this:
!Screenshot from 2018-10-10 08-22-25.png|thumbnail!
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-10-10 08-22-25.png, a3.dmn, auto.png, manual.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening (/)
> # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
> # Tree, top node in the middle of the screen, some branches to all sides (/)
> # Graph with big crossing of edges, similar to complete graph (/)
> # Large (but sparse) graph, not all nodes visible without scrolling (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3067:
--------------------------------
Attachment: Screenshot from 2018-10-10 08-22-25.png
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-10-10 08-22-25.png, a3.dmn, auto.png, manual.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening (/)
> # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
> # Tree, top node in the middle of the screen, some branches to all sides (/)
> # Graph with big crossing of edges, similar to complete graph (/)
> # Large (but sparse) graph, not all nodes visible without scrolling (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3067:
--------------------------------
Attachment: a3.dmn
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, a3.dmn, auto.png, manual.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening (/)
> # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
> # Tree, top node in the middle of the screen, some branches to all sides (/)
> # Graph with big crossing of edges, similar to complete graph (/)
> # Large (but sparse) graph, not all nodes visible without scrolling (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3067:
--------------------------------
Description:
Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
h2. Acceptance tests
# -User is prompted if he wants or not to apply autolayout feature- discussed in comments
# Positioning is automatically stored after model opening (/)
# Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
# Tree, top node in the middle of the screen, some branches to all sides (/)
# Graph with big crossing of edges, similar to complete graph (/)
# Large (but sparse) graph, not all nodes visible without scrolling (/)
was:
Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
h2. Acceptance tests
# -User is prompted if he wants or not to apply autolayout feature- discussed in comments
# Positioning is automatically stored after model opening (/)
# Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
# Tree, top node in the middle of the screen, some branches to all sides (/)
# Graph with big crossing of edges, similar to complete graph (/)
# Large (but sparse) graph, not all nodes visible without scrolling
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, auto.png, manual.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening (/)
> # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
> # Tree, top node in the middle of the screen, some branches to all sides (/)
> # Graph with big crossing of edges, similar to complete graph (/)
> # Large (but sparse) graph, not all nodes visible without scrolling (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3067) [DMN Designer] Automatic Layout Feature Workbench Integration
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3067?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3067:
--------------------------------
Description:
Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
h2. Acceptance tests
# -User is prompted if he wants or not to apply autolayout feature- discussed in comments
# Positioning is automatically stored after model opening (/)
# Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
# Tree, top node in the middle of the screen, some branches to all sides (/)
# Graph with big crossing of edges, similar to complete graph (/)
# Large (but sparse) graph, not all nodes visible without scrolling
was:
Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
h2. Acceptance tests
# -User is prompted if he wants or not to apply autolayout feature- discussed in comments
# Positioning is automatically stored after model opening
# Simple graph, no branches, starting node on left, ending node on right
# Simple graph, no branches, starting node on top, ending node on bottom
# Tree, top node in the middle of the screen, some branches to all sides
# Graph with big crossing of edges, similar to complete graph
# Large (but sparse) graph, not all nodes visible without scrolling
> [DMN Designer] Automatic Layout Feature Workbench Integration
> -------------------------------------------------------------
>
> Key: DROOLS-3067
> URL: https://issues.jboss.org/browse/DROOLS-3067
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, auto.png, manual.png
>
>
> Integrate the Automatic Layout feature into workbench, so during opening an imported DMN model its nodes are positioned automatically with this feature.
> h2. Acceptance tests
> # -User is prompted if he wants or not to apply autolayout feature- discussed in comments
> # Positioning is automatically stored after model opening (/)
> # Simple graph, no branches, starting node -> node -> ...... node -> ending node (/)
> # Tree, top node in the middle of the screen, some branches to all sides (/)
> # Graph with big crossing of edges, similar to complete graph (/)
> # Large (but sparse) graph, not all nodes visible without scrolling
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months