[JBoss JIRA] (HAWKULARQE-81) Baseline #3
by viet nguyen (JIRA)
viet nguyen created HAWKULARQE-81:
-------------------------------------
Summary: Baseline #3
Key: HAWKULARQE-81
URL: https://issues.jboss.org/browse/HAWKULARQE-81
Project: Hawkular QE
Issue Type: Sub-task
Reporter: viet nguyen
Assignee: Michael Foley
* Run pyme on master to eliminate vpn slowness
* Fix query start-end window
* Update pyme endpoint to increase metrics to 30 (currently 2)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1502) Incorrect "local" namespace resolution
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1502?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-1502:
----------------------------------------
Second problem is {{DMNEvaluatorCompiler.compileDecisionTable}} was using wrong "baseline" node for local namespace resolution when calling {{resolveType}} for the InputClause
{code:java}
16:38:02.061 [main] ERROR o.k.d.core.compiler.DMNCompilerImpl.compile:80 - Error compiling model from source.
java.lang.NullPointerException: null
at org.kie.dmn.core.compiler.DMNEvaluatorCompiler.compileDecisionTable(DMNEvaluatorCompiler.java:254) ~[classes/:na]
at org.kie.dmn.core.compiler.DMNEvaluatorCompiler.compileExpression(DMNEvaluatorCompiler.java:75) ~[classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.processDrgElements(DMNCompilerImpl.java:207) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.compile(DMNCompilerImpl.java:93) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.compile(DMNCompilerImpl.java:77) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.compile(DMNCompilerImpl.java:66) [classes/:na]
at org.kie.dmn.core.assembler.DMNAssemblerService.addResource(DMNAssemblerService.java:55) [classes/:na]
{code}
> Incorrect "local" namespace resolution
> --------------------------------------
>
> Key: DROOLS-1502
> URL: https://issues.jboss.org/browse/DROOLS-1502
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
> The following example DMN model similar to an already existing in the code base is modified for "local" xmlns namespace definition:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <definitions id="definitions"
> name="definitions"
> namespace="https://www.drools.org/kie-dmn/definitions"
> xmlns="http://www.omg.org/spec/DMN/20151101/dmn.xsd"
> xmlns:kie="https://www.drools.org/kie-dmn"
> >
> <!--TEST: do not define feel namespace globally, e.g.: NO root element xmlns:feel="http://www.omg.org/spec/FEEL/20140401" -->
> <itemDefinition label="MyType" name="MyType">
> <typeRef xmlns:feel="http://www.omg.org/spec/FEEL/20140401">feel:string</typeRef>
> <allowedValues constraintsType="enumeration">
> <text>"a","b","c"</text>
> </allowedValues>
> </itemDefinition>
> <inputData id="_3d560678-a126-4654-a686-bc6d941fe40b" name="MyInput">
> <variable id="_053333df-1777-45f1-a6c7-56562fbdfdae" name="MyInput" typeRef="MyType"/>
> </inputData>
> <decision id="_497a5306-b2e8-4945-b8b5-82af2e2b99b5" name="MyDecision">
> <variable id="_514d6d8d-5329-44fa-af91-a7e7addbadd8" name="MyDecision" typeRef="MyType"/>
> <informationRequirement>
> <requiredInput href="#_3d560678-a126-4654-a686-bc6d941fe40b"/>
> </informationRequirement>
> <decisionTable hitPolicy="UNIQUE" id="_fff2b82e-2850-4826-adc9-4b1570d6fa91" outputLabel="MyDecision">
> <input id="_e0471736-9a71-40c7-b5ca-bf367c6a3af9" label="MyInput">
> <inputExpression typeRef="feel:string" xmlns:feel="http://www.omg.org/spec/FEEL/20140401">
> <text>MyInput</text>
> </inputExpression>
> </input>
> <output id="_01796218-0d50-4ebe-bd2b-b4509318e334"/>
> <rule id="_fd1835b6-5fe1-4fd9-a8e4-39b4f7083b24">
> <inputEntry expressionLanguage="http://www.omg.org/spec/FEEL/20140401" id="_1c8b24c7-e722-40d7-8661-f03d402688d2">
> <text>-</text>
> </inputEntry>
> <outputEntry id="_0b9d04fe-032b-4753-84dd-9838f6cdef53">
> <text>"Decision taken"</text>
> </outputEntry>
> </rule>
> </decisionTable>
> </decision>
> </definitions>
> {code}
> and it's throwing two distinct types of NPEs.. (follows)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1502) Incorrect "local" namespace resolution
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1502?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-1502:
----------------------------------------
First problem is {{DMNCompilerImpl.resolveTypeRef()}} which was not considering local namespace for the QName as resolved by the unmarshalling
{code:java}
16:28:24.122 [main] ERROR o.k.d.core.compiler.DMNCompilerImpl.compile:78 - Error compiling model from source.
java.lang.NullPointerException: null
at org.kie.dmn.core.compiler.DMNCompilerImpl.resolveTypeRef(DMNCompilerImpl.java:398) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.buildTypeDef(DMNCompilerImpl.java:290) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.processItemDefinitions(DMNCompilerImpl.java:100) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.compile(DMNCompilerImpl.java:90) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.compile(DMNCompilerImpl.java:75) [classes/:na]
at org.kie.dmn.core.compiler.DMNCompilerImpl.compile(DMNCompilerImpl.java:64) [classes/:na]
at org.kie.dmn.core.assembler.DMNAssemblerService.addResource(DMNAssemblerService.java:55) [classes/:na]
{code}
> Incorrect "local" namespace resolution
> --------------------------------------
>
> Key: DROOLS-1502
> URL: https://issues.jboss.org/browse/DROOLS-1502
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
> The following example DMN model similar to an already existing in the code base is modified for "local" xmlns namespace definition:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <definitions id="definitions"
> name="definitions"
> namespace="https://www.drools.org/kie-dmn/definitions"
> xmlns="http://www.omg.org/spec/DMN/20151101/dmn.xsd"
> xmlns:kie="https://www.drools.org/kie-dmn"
> >
> <!--TEST: do not define feel namespace globally, e.g.: NO root element xmlns:feel="http://www.omg.org/spec/FEEL/20140401" -->
> <itemDefinition label="MyType" name="MyType">
> <typeRef xmlns:feel="http://www.omg.org/spec/FEEL/20140401">feel:string</typeRef>
> <allowedValues constraintsType="enumeration">
> <text>"a","b","c"</text>
> </allowedValues>
> </itemDefinition>
> <inputData id="_3d560678-a126-4654-a686-bc6d941fe40b" name="MyInput">
> <variable id="_053333df-1777-45f1-a6c7-56562fbdfdae" name="MyInput" typeRef="MyType"/>
> </inputData>
> <decision id="_497a5306-b2e8-4945-b8b5-82af2e2b99b5" name="MyDecision">
> <variable id="_514d6d8d-5329-44fa-af91-a7e7addbadd8" name="MyDecision" typeRef="MyType"/>
> <informationRequirement>
> <requiredInput href="#_3d560678-a126-4654-a686-bc6d941fe40b"/>
> </informationRequirement>
> <decisionTable hitPolicy="UNIQUE" id="_fff2b82e-2850-4826-adc9-4b1570d6fa91" outputLabel="MyDecision">
> <input id="_e0471736-9a71-40c7-b5ca-bf367c6a3af9" label="MyInput">
> <inputExpression typeRef="feel:string" xmlns:feel="http://www.omg.org/spec/FEEL/20140401">
> <text>MyInput</text>
> </inputExpression>
> </input>
> <output id="_01796218-0d50-4ebe-bd2b-b4509318e334"/>
> <rule id="_fd1835b6-5fe1-4fd9-a8e4-39b4f7083b24">
> <inputEntry expressionLanguage="http://www.omg.org/spec/FEEL/20140401" id="_1c8b24c7-e722-40d7-8661-f03d402688d2">
> <text>-</text>
> </inputEntry>
> <outputEntry id="_0b9d04fe-032b-4753-84dd-9838f6cdef53">
> <text>"Decision taken"</text>
> </outputEntry>
> </rule>
> </decisionTable>
> </decision>
> </definitions>
> {code}
> and it's throwing two distinct types of NPEs.. (follows)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1502) Incorrect "local" namespace resolution
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-1502:
--------------------------------------
Summary: Incorrect "local" namespace resolution
Key: DROOLS-1502
URL: https://issues.jboss.org/browse/DROOLS-1502
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
The following example DMN model similar to an already existing in the code base is modified for "local" xmlns namespace definition:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<definitions id="definitions"
name="definitions"
namespace="https://www.drools.org/kie-dmn/definitions"
xmlns="http://www.omg.org/spec/DMN/20151101/dmn.xsd"
xmlns:kie="https://www.drools.org/kie-dmn"
>
<!--TEST: do not define feel namespace globally, e.g.: NO root element xmlns:feel="http://www.omg.org/spec/FEEL/20140401" -->
<itemDefinition label="MyType" name="MyType">
<typeRef xmlns:feel="http://www.omg.org/spec/FEEL/20140401">feel:string</typeRef>
<allowedValues constraintsType="enumeration">
<text>"a","b","c"</text>
</allowedValues>
</itemDefinition>
<inputData id="_3d560678-a126-4654-a686-bc6d941fe40b" name="MyInput">
<variable id="_053333df-1777-45f1-a6c7-56562fbdfdae" name="MyInput" typeRef="MyType"/>
</inputData>
<decision id="_497a5306-b2e8-4945-b8b5-82af2e2b99b5" name="MyDecision">
<variable id="_514d6d8d-5329-44fa-af91-a7e7addbadd8" name="MyDecision" typeRef="MyType"/>
<informationRequirement>
<requiredInput href="#_3d560678-a126-4654-a686-bc6d941fe40b"/>
</informationRequirement>
<decisionTable hitPolicy="UNIQUE" id="_fff2b82e-2850-4826-adc9-4b1570d6fa91" outputLabel="MyDecision">
<input id="_e0471736-9a71-40c7-b5ca-bf367c6a3af9" label="MyInput">
<inputExpression typeRef="feel:string" xmlns:feel="http://www.omg.org/spec/FEEL/20140401">
<text>MyInput</text>
</inputExpression>
</input>
<output id="_01796218-0d50-4ebe-bd2b-b4509318e334"/>
<rule id="_fd1835b6-5fe1-4fd9-a8e4-39b4f7083b24">
<inputEntry expressionLanguage="http://www.omg.org/spec/FEEL/20140401" id="_1c8b24c7-e722-40d7-8661-f03d402688d2">
<text>-</text>
</inputEntry>
<outputEntry id="_0b9d04fe-032b-4753-84dd-9838f6cdef53">
<text>"Decision taken"</text>
</outputEntry>
</rule>
</decisionTable>
</decision>
</definitions>
{code}
and it's throwing two distinct types of NPEs.. (follows)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1042) When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-1042?page=com.atlassian.jira.plugin.s... ]
Hynek Švábek updated ELY-1042:
------------------------------
Description:
When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
I expect consistent state, same aliases in memory and persisted on disk.
We must not add new aliases only to memory.
This problem is exported from issue https://issues.jboss.org/browse/JBEAP-6866
where is noted as secondary problem.
*HOW TO REPRODUCE*
{code}
/subsystem=elytron/credential-store=cs001:add(uri="cr-store://test/cs/credentialstore.jceks?create=true", credential-reference={clear-text=pass123}, relative-to="jboss.server.data.dir")
{code}
{code}
/subsystem=elytron/credential-store=cs001/alias=alias001:add(secret-value=secretvalue)
{code}
Now is credentialstore.jceks file persisted on disk here *JBOSS_HOME/standalone/data/cs*
Please remove write permission for folder "cs"
{code}
chmod g-w cs
chmod u-w cs
{code}
Try add another entry to credential store
/subsystem=elytron/credential-store=cs001/alias=alias002:add(secret-value=secretvalue)
{
"outcome" => "failed",
"failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09525: Unable to flush credential store to storage'",
"rolled-back" => true
}
And you get error message as above.
Now you list all aliases in credential store:
{code}
/subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
{
"outcome" => "success",
"result" => [
"alias001",
"alias002"
]
}
{code}
There is non persisted "alias002" too.
*Now we check aliases in persisted file**:*
{code}
reload
{code}
There isn't any alias "alias002" after reload.
{code}
/subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
{
"outcome" => "success",
"result" => ["alias001"]
}
{code}
was:
When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
I expect consistent state, same aliases in memory and persisted on disk.
We must not add new aliases only to memory.
This problem is exported from issue https://issues.jboss.org/browse/JBEAP-6866
where is noted as secondary problem.
*HOW TO REPRODUCE*
{code}
/subsystem=elytron/credential-store=cs001:add(uri="cr-store://test/cs/credentialstore.jceks?create=true", credential-reference={clear-text=pass123}, relative-to="jboss.server.data.dir")
{code}
{code}
/subsystem=elytron/credential-store=cs001/alias=alias001:add(secret-value=secretvalue)
{code}
Now is credentialstore.jceks file persisted on disk here *JBOSS_HOME/standalone/data/cs*
Please remove write permission for folder "cs"
{code}
chmod g-w cs
chmod u-w cs
{code}
Try add another entry to credential store
/subsystem=elytron/credential-store=cs001/alias=alias002:add(secret-value=secretvalue)
{
"outcome" => "failed",
"failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09525: Unable to flush credential store to storage'",
"rolled-back" => true
}
And you get error message as above.
Now you list all aliases in credential store:
{code}
/subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
{
"outcome" => "success",
"result" => [
"alias001",
"alias002"
]
}
{code}
There is non persisted "alias002" too.
*Now we check aliases in persisted file:*
{code}
reload
{code}
There isn't any alias "alias002" after reload.
{code}
/subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
{
"outcome" => "success",
"result" => ["alias001"]
}
{code}
> When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1042
> URL: https://issues.jboss.org/browse/ELY-1042
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Priority: Critical
>
> When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
> I expect consistent state, same aliases in memory and persisted on disk.
> We must not add new aliases only to memory.
> This problem is exported from issue https://issues.jboss.org/browse/JBEAP-6866
> where is noted as secondary problem.
> *HOW TO REPRODUCE*
> {code}
> /subsystem=elytron/credential-store=cs001:add(uri="cr-store://test/cs/credentialstore.jceks?create=true", credential-reference={clear-text=pass123}, relative-to="jboss.server.data.dir")
> {code}
> {code}
> /subsystem=elytron/credential-store=cs001/alias=alias001:add(secret-value=secretvalue)
> {code}
> Now is credentialstore.jceks file persisted on disk here *JBOSS_HOME/standalone/data/cs*
> Please remove write permission for folder "cs"
> {code}
> chmod g-w cs
> chmod u-w cs
> {code}
> Try add another entry to credential store
> /subsystem=elytron/credential-store=cs001/alias=alias002:add(secret-value=secretvalue)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09525: Unable to flush credential store to storage'",
> "rolled-back" => true
> }
> And you get error message as above.
> Now you list all aliases in credential store:
> {code}
> /subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
> {
> "outcome" => "success",
> "result" => [
> "alias001",
> "alias002"
> ]
> }
> {code}
> There is non persisted "alias002" too.
> *Now we check aliases in persisted file**:*
> {code}
> reload
> {code}
> There isn't any alias "alias002" after reload.
> {code}
> /subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
> {
> "outcome" => "success",
> "result" => ["alias001"]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1042) When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-1042:
---------------------------------
Summary: When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
Key: ELY-1042
URL: https://issues.jboss.org/browse/ELY-1042
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Priority: Critical
When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
I expect consistent state, same aliases in memory and persisted on disk.
We must not add new aliases only to memory.
This problem is exported from issue https://issues.jboss.org/browse/JBEAP-6866
where is noted as secondary problem.
*HOW TO REPRODUCE*
{code}
/subsystem=elytron/credential-store=cs001:add(uri="cr-store://test/cs/credentialstore.jceks?create=true", credential-reference={clear-text=pass123}, relative-to="jboss.server.data.dir")
{code}
{code}
/subsystem=elytron/credential-store=cs001/alias=alias001:add(secret-value=secretvalue)
{code}
Now is credentialstore.jceks file persisted on disk here *JBOSS_HOME/standalone/data/cs*
Please remove write permission for folder "cs"
{code}
chmod g-w cs
chmod u-w cs
{code}
Try add another entry to credential store
/subsystem=elytron/credential-store=cs001/alias=alias002:add(secret-value=secretvalue)
{
"outcome" => "failed",
"failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09525: Unable to flush credential store to storage'",
"rolled-back" => true
}
And you get error message as above.
Now you list all aliases in credential store:
{code}
/subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
{
"outcome" => "success",
"result" => [
"alias001",
"alias002"
]
}
{code}
There is non persisted "alias002" too.
*Now we check aliases in persisted file:*
{code}
reload
{code}
There isn't any alias "alias002" after reload.
{code}
/subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
{
"outcome" => "success",
"result" => ["alias001"]
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1042) When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-1042?page=com.atlassian.jira.plugin.s... ]
Hynek Švábek updated ELY-1042:
------------------------------
Component/s: Credential Store
> When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1042
> URL: https://issues.jboss.org/browse/ELY-1042
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Priority: Critical
>
> When failed credential store flush to file on the disk then we have inconsistency between credential store in memory and persisted file.
> I expect consistent state, same aliases in memory and persisted on disk.
> We must not add new aliases only to memory.
> This problem is exported from issue https://issues.jboss.org/browse/JBEAP-6866
> where is noted as secondary problem.
> *HOW TO REPRODUCE*
> {code}
> /subsystem=elytron/credential-store=cs001:add(uri="cr-store://test/cs/credentialstore.jceks?create=true", credential-reference={clear-text=pass123}, relative-to="jboss.server.data.dir")
> {code}
> {code}
> /subsystem=elytron/credential-store=cs001/alias=alias001:add(secret-value=secretvalue)
> {code}
> Now is credentialstore.jceks file persisted on disk here *JBOSS_HOME/standalone/data/cs*
> Please remove write permission for folder "cs"
> {code}
> chmod g-w cs
> chmod u-w cs
> {code}
> Try add another entry to credential store
> /subsystem=elytron/credential-store=cs001/alias=alias002:add(secret-value=secretvalue)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09525: Unable to flush credential store to storage'",
> "rolled-back" => true
> }
> And you get error message as above.
> Now you list all aliases in credential store:
> {code}
> /subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
> {
> "outcome" => "success",
> "result" => [
> "alias001",
> "alias002"
> ]
> }
> {code}
> There is non persisted "alias002" too.
> *Now we check aliases in persisted file:*
> {code}
> reload
> {code}
> There isn't any alias "alias002" after reload.
> {code}
> /subsystem=elytron/credential-store=cs001:read-children-names(child-type=alias)
> {
> "outcome" => "success",
> "result" => ["alias001"]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month